StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><em>Update: Added section 'Automated testing for iOS4'</em></p> <p>As a professional tester my suggestion is that you should have a healthy mix of automated and manual testing. The Examples below are in .net but it should be easy to find a tool for whatever technique you are using.</p> <p><strong>AUTOMATED TESTING</strong></p> <ul> <li><p><strong>Unit Testing</strong><br> Use NUnit to test your classes, functions and interaction between them.<br> <a href="http://www.nunit.org/index.php" rel="noreferrer">http://www.nunit.org/index.php</a></p></li> <li><p><strong>Automated Functional Testing</strong><br> If it's possible you should automate a lot of the functional testing. Some frame works have functional testing built into them. Otherwise you have to use a tool for it. If you are developing web sites/applications you might want to look at Selenium.<br> <a href="http://www.peterkrantz.com/2005/selenium-for-aspnet/" rel="noreferrer">http://www.peterkrantz.com/2005/selenium-for-aspnet/</a></p></li> <li><p><strong>Continuous Integration</strong><br> Use CI to make sure all your automated tests run every time someone in your team makes a commit to the project.<br> <a href="http://martinfowler.com/articles/continuousIntegration.html" rel="noreferrer">http://martinfowler.com/articles/continuousIntegration.html</a></p></li> <li><p><strong>Automated testing for iOS4</strong><br> Automate the testing of your application by scripting touch events using the new UIAutomation Instrument.<br> Some links:<br></p> <ul> <li><a href="http://answers.oreilly.com/topic/1646-how-to-use-uiautomation-to-create-iphone-ui-tests/" rel="noreferrer">http://answers.oreilly.com/topic/1646-how-to-use-uiautomation-to-create-iphone-ui-tests/</a><br></li> <li><a href="http://cocoawithlove.com/2008/11/automated-user-interface-testing-on.html" rel="noreferrer">http://cocoawithlove.com/2008/11/automated-user-interface-testing-on.html</a><br></li> <li><a href="http://alexvollmer.com/posts/2010/07/03/working-with-uiautomation/" rel="noreferrer">http://alexvollmer.com/posts/2010/07/03/working-with-uiautomation/</a><br></li> </ul></li> </ul> <p><strong>MANUAL TESTING</strong><br> As much as I love automated testing it is, IMHO, not a substitute for manual testing. The main reason being that an automated can only do what it is told and only verify what it has been informed to view as pass/fail. A human can use it's intelligence to find faults and raise questions that appear while testing something else.</p> <ul> <li><strong>Exploratory Testing</strong><br> ET is a very low cost and effective way to find defects in a project. It take advantage of the intelligence of a human being and a teaches the testers/developers more about the project than any other testing technique i know of. Doing an ET session aimed at every feature deployed in the test environment is not only an effective way to find problems fast, but also a good way to learn and fun!<br> <a href="http://www.satisfice.com/articles/et-article.pdf" rel="noreferrer">http://www.satisfice.com/articles/et-article.pdf</a></li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload