Software Testing Approach Only Hours Instead of Days Available

Imagine that you only have hours left instead of days to complete testing.  Does this sound familiar?  No matter how well we have planned for the resources, estimating testing efforts, prepared the test scripts and scenarios, it would be useless if we don’t have the time to execute or a testable system.  There are so many factors can contribute to the delay but how do you approach the situation so that critical functionality is tested?

Before we start discussing what can be done in this situation, I would like to emphasize that software testing is a process of finding defects to ensure that the system under test meets the requirements.  Thorough planning test efforts and monitoring test progress should not be taken lightly.  The time component in software testing is generally divided into two:

  1. Test to validate the requirements.  This is where you execute test cases and scenarios you have prepared during planning/development stage.  It is very common that test cases get updated as we me make progress especially working in Agile project methodology where changes are allowed (within reason) as end users see fit.  New test cases might be created as the result of better understanding of the system.
  2. Finding defects.  Once High and Medium priority test cases have been executed, more complicated test scenarios can be developed such as varying the inputs or negative scenarios that might occur on regular basis.

This seems to be a good plan if you have enough time to complete.  However, different approach should be taken when there is only a fraction of time remains from initial plan.  User Acceptance Testing (UAT) checklist would be the best place to start.  This will ensure that the main functionality are working.  Exploratory testing should also be considered to detect any obvious defects.  Any administration work such as updating test cases and recording test results can be postponed after UAT.  it is also important to make business users aware any limitations or defects that might arise and provide solutions and steps to work around until issues have been resolved.

In summary, going through UAT checklist as a starting point is not recommended and should be avoided.  It is important to have UAT checklist done as soon as possible to give us a practical perspective of which areas to focus.

Related Posts Plugin for WordPress, Blogger...