Refining the Agile Testing Process Agile Testing

Having achieved this significant initial success,we then subsequently repeated the process for the second release. A number of improvements were introduced in the testing process leading up to this release:

  • Refine test automation A number of additional regression test tools were deployed.Of particular help was a tool that compared databases, so that we could inspect every record in pairs of tables and identify any differences in those tables and report them. This proved to be very useful in identifying a range of unexpected differences in the system’s data that were not immediately apparent to the user (since they related to trades that the user might not be inspecting for some months until they were closer to the expiry dates of those trades).
  • Address system performanceA performance pack was developed that was able to capture system load information while regression tests were executed. We could then compare the performance data of runs and identify any increases in run times or system load.These could then be inspected(in conjunction with profiling tools) to identify any specific areas of code that were generating problems.

The testing team continued to work with the software for a further year, before finally handing over the regression test environment to the developers to be integrated into their normal development and test approach.

In the longer term, the results of this approach were impressive.There was only one major crash of the system following the second release,and the system was never unavailable on key end-of-period dates.

A tremendous success,one would think.Well it was, in many respects,and it provided a model that has been reused many times in similar circumstances for other customers.However, as you will see in the next section of the case study, this was not the universal perspective of all parties involved!

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd Protection Status

Agile Testing Topics