Last time we discussed how you organise your technology stack. This month’s discussion point is around testing your applications.
How do you organise your tests. Do you separate your unit tests, integration tests and UI tests into separate projects? Do you do anything specific to keep track of your tests? What naming conventions do you use? Do you run them before a check in or is that what the build server is for?
If you are not testing, then how would you like to test your apps if given the opportunity?
I apologise, it has been a while since the last Developer Blog Banter. I was too busy getting my applications ready for the launch of Windows Phone 7.
As usual, comment on this post when you join the Developer Blog Banter and I’ll add your response below
Participants
- David Burela – testing applicaitons
- Liam Mclennan – testing, huh! what is it good for?
- Tarn Barford – How do you test your applications?
- Eric Ridgeway – I can haz tests?
- Peter Gfader – How do you test your applications?
[…] is my response to the 2nd Developer Blog Banter. The question asked […]
[…] So our friend David Burela is back at it again with Developer Blog Banter #2: How do you test your applications? […]
[…] October 2010 kicked off the 2nd Developer Blog Banter https://davidburela.wordpress.com/2010/10/13/developer-blog-banter-2-how-do-you-test-your-application… […]
[…] Previous banters asked developers to “What their current technology stacks look like” and “How do you test applications”. More information about the blog banter can be found at […]
Here are a couple databases compatible with Windows Phone 7 and Windows Phone 8:
http://www.kellermansoftware.com/p-43-ninja-net-database-pro.aspx