Lecture 9. Test Execution: New Feature Testing -> Quick Intro -> Test Estimates -> Entry/Exit Criteria -> Test Plan -> Aggressive Testing From Jason Fisher -> Lecture RecapThis testing technique was introduced by my friend Jason Fisher.
In start-ups we have loads of small new features to release, and releases might happen several times a week. There can also be situations when there are many developers and only one tester. Here is what can be done in such an environment:
1. After the coding is finished and the code is pushed to the test environment, the developer and the tester get together and begin discussing test scenarios. They outline major flows on a white board, and they decide who tests what. Right – both the developer and the tester will be doing testing.
2. The testing starts, and the communication is done person-to-person or via Yahoo! Messenger. All bugs are fixed by the developer as soon as they are found. New builds are pushed promptly after the bug fixes are checked in into the CVS.
3. After the major flows seem to work, the developer gets back to his business and the tester spends several hours:
– Planning the testing, e.g., using the black list-white list technique
– Executing the testing, e.g., by going through the flows on the white list
4. After found bugs are fixed and verified, the tester does a quick system test followed by an acceptance test. If everything is fine, the tester gives the green light to push to production.
It sounds simple, but it works fabulously. Next ->
Lecture 9. Test Execution: New Feature Testing -> Quick Intro -> Test Estimates -> Entry/Exit Criteria -> Test Plan -> Aggressive Testing From Jason Fisher -> Lecture Recap
