Software Engineer Brian Driscoll uses an unpleasant client post-mortem to explain the importance of testing UI with external testers. Read more
http://www.brian-driscoll.com/2009/12/why-external-ui-testing-matters.html
Showing posts with label test case. Show all posts
Showing posts with label test case. Show all posts
Monday, December 21, 2009
Thursday, December 17, 2009
Testing the Limits with James Bach
This is an interesting article worth reading for those of you that belongs to the Testing domain.
http://blog.utest.com/testing-the-limits-with-james-bach-part-1/2009/12/
http://blog.utest.com/testing-the-limits-with-james-bach-part-1/2009/12/
Saturday, October 31, 2009
Does standards helping pushing testers to the max
Our main concern is whether testers sometimes find themselves adhering to standards not because they believe them to be valuable on their project, but because they fear the consequences of being "non-compliant". Read more in the link.
Saturday, March 14, 2009
140 words - 15 practical tips for test management
1. Cover each requirements with at least one test
2. Write functional tests first
3. Start with positive tests first to avoid show-stoppers
4. Expose your test plan to developers and product managers before QA starts
5. Use defects history for better coverage of existing problems
6. Write short, understandable tests.
7. Use parameters matrixes for multiple configurations
8. Convert each reported defect to test case, in case defect is not reported during test run.
9. Set effort estimation to assess the time required for test execution
10. Create execution sets for functional, sanity, regression tests
11. run test case only once in each QA cycle
12. Create reports for better tracking of your test execution
13. Learn to analyze your test management reports
14. Create understandable and clear defects
15. Use defects steps to reproduce to assure defect can be reproduced
2. Write functional tests first
3. Start with positive tests first to avoid show-stoppers
4. Expose your test plan to developers and product managers before QA starts
5. Use defects history for better coverage of existing problems
6. Write short, understandable tests.
7. Use parameters matrixes for multiple configurations
8. Convert each reported defect to test case, in case defect is not reported during test run.
9. Set effort estimation to assess the time required for test execution
10. Create execution sets for functional, sanity, regression tests
11. run test case only once in each QA cycle
12. Create reports for better tracking of your test execution
13. Learn to analyze your test management reports
14. Create understandable and clear defects
15. Use defects steps to reproduce to assure defect can be reproduced
Labels:
defect tracking,
test case,
test execution,
test management,
test run
Subscribe to:
Posts (Atom)
