You are here: » Software Testing » 20 Software Testing Best Practices

20 Software Testing Best Practices

I read an article today that presented a top-20 list of software testing tips and best practices.  Nothing too Earth-shattering on the list, but I thought it was worthwhile to share it with you.  I am not going to be adding any commentary, but if you want to read the full article it can be found here.  So here is the list in no particular order:

  1. Go in to the test with a positive mindset
  2. Create test cases that focus on valid outcomes, and then add in some invalid ones, to test for unexpected results
  3. Do not let the programmers test the code          
  4. Craft the test cases concurrent with the formation of the requirements to make sure everything can be adequately tested
  5. When critical response times are required, the performance of the application must be factored into the test plan
  6. Test specifically for unintended results
  7. Analyze the results as deeply as possible to identify solutions as well as problems
  8. Share test cases with developers so everyone is on the same page
  9. Prioritize all tasks
  10. Utilize bug graphs for regression testing
  11. Keep developers away from the test environment
  12. Get in the habit of jotting down notes as you progress through the testing process
  13. Invest in improving your skills, for example earning your ISEB Foundation, ISEB Intermediate, ISTQB Foundation, or ISTQB Advanced certification
  14. Understand that sometimes changes in code bases may be needed for testing the application to make sure that bogus transactions are not triggered
  15. Always aim to maximize QA coverage, and realize that 100% may not be attainable
  16. Combine test cases to facilitate regression tests
  17. Split the test plan into smaller chunks, or functional modules
  18. Involve testing personnel during the requirements and design phases
  19. Communicate as much as possible with the developers to enable a greater understanding of what is being tested
  20. Write bug reports clearly so they are not open to interpretation

Related posts:

  1. What is Thread-Based Test Management in Software Testing?
  2. Best Practices for Enhancing Software Testing Efficiency: Part II

Filed Under: Software Testing

Leave a Reply