Effective Software Testing in 10 steps


I was thinking about product testing that can be performed more effectively. And here are 10 guidelines that I come up with for effective software testing. These guidelines are of course applicable once product arrives for testing. :)
  1. Get the product’s domain knowledge E.g. if product under test is a web application then tester should know about web server, CGI, etc. If product under test supports Solaris zones then tester should know types of zones and how they work etc. This will help tester come up with different test cases.
  2. Ensure that tester has all insights of test-bed. This will ensure that tester understands the environment where product will be tested. Sometimes changing system parameters (on test-bed) can severely affect product.
  3. Define Test plan for ultimate goal of testing. E.g. test plan should state clearly if tests requires white box testing along with black box testing.
  4. It is also important that test plan states overall scope of test cycle (I am not covering all granularities of test plan). Scope should cover different types of testing that can be performed over entire product testing cycle.
  5. Develop test cases to cover all functionality of product under test. It is always helpful to get inputs from developer who has developed the feature while coming up with different test cases. Ensure that negative test cases are also covered along functional test cases.  E.g. In case of network application what if there is loss in network connection? Does application crash due to sudden network disruptions?
  6. Never ignore security test cases.
  7. Keep all matrices in hand to measure continued progress of software testing. This should not be the only task of Test Leads or Managers. A tester should measure his individual performance to fine tune his performance. Graphical representation of these matrices using simple tools such as excel will provide a helpful insight.
  8. Automate as many test cases as possible if feature is well stabilized. Freeze on automation tool well in advance that will be used by all team members. It will be helpful to include name of automation tool in test plan itself. Tester should not try to automate a feature which is under development ( Not valid in case of unit testing). Due to constant changes during development of a particular feature, it wouldn’t make any sense to automate test cases and waste valuable time.
  9. While executing performance testing cycle, get all the numbers in advance for a product under test. E.g. during load testing what will be the maximum load (e.g. number of users allowed) that application can handle, should be known in advance. During stress testing, ensure that exact breaking point of application is noted.
  10. Compatibility testing is also important and should be aligned with environment where customer will possibly deploy the product.
Though above guidelines do not cover each and every aspect of software testing, still it provides broad picture of what needs to be done. Do you have any more inputs to add then let everyone know in comments below.

By Mandar Pise

Opinions expressed by techsutram contributors are their own.

1 comment:

  1. First of all. Thanks very much for your useful post.

    I just came across your blog and wanted to drop you a note telling you how impressed I was with the information you have posted here.

    Please let me introduce you some info related to this post and I hope that it is useful for software testing community.

    There is a good Software Testing resource site, Have alook

    http://SoftwareTestingNet.com

    simi

    ReplyDelete

    Your valuable comments are welcome. (Moderated)


Instagram