What to do you mean by Agile Testing Process Agile Testing

In determining the testing approach to be used, there were a number of issues to be considered:

  • The characteristics of the development and testing process(as described earlier), plus the historical situation we inherited, meant that this was a “special needs” testing project.
    1. The common manifestation of this problem in the IT industry is to exclaim that the system is too poor to salvage and should be rewritten from scratch because the issue of understanding the problem is so large.
    We had to find an approach that would accommodate the magnitude of the challenge, work with it, and deliver progressive improvement by identifying and isolating the most significant defects as quickly as possible. These would then be fixed on a case by case basis.At the same time, we also had to provide confidence that the ultimate goal of a high-quality robust system was achievable.
  • Although initially we had the commitment of all of the key stakeholders, we knew we would have to work hard to ensure that we retained this support throughout the process.

The details of our agile testing approach are as follows:

  • The software solution is correct –Despite the problems that we knew existed,we put forward the hypothesis that the software solution was correct (even with the work-arounds and reliability issues). This provided us with a working baseline from which to proceed.
  • User test run-through –Using a copy of the current version of the software, we asked the users to run through the standard tests that they would normally undertake to validate the system and to show us the results that they would expect.
  • Employ test automation –We captured these tests(including the navigation through the software and the specific verifications required) using functional testing tools(classic capture–replay tools) and printed out the results, both screen shots and reports, provided these to the users, and asked them to check and sign off these tests.
  • Minimum test harness – We developed a process to reliably prepare a release package,installation instructions,and a set of minimum tests to run all of the key functions of the system to prove that all major functions would run without crashing. It is disappointing how many releases were deployed into production and crashed, often because of configuration and release errors rather than software bugs.
  • Regression testing baseline The signed-off automated tests provided us with a suite of regression tests, which gave reasonable test coverage over all components of the system. It was then possible to run the tests from a common baseline and get identical results on successive runs.
  • Incremental new test development Working closely with the developers and users,we then built a set of specific tests for the new functions being developed and worked with the users to define precisely what the new behavior of the system should be and where any other changes to the system might be anticipated.
  • Test new build The automated regression tests and the new tests were then run against the new version of the system.The assumption was that if the system was correct following the new development, then there should be no changes to any part of the system except those containing new functionality.
  • Review and analyze defects However,of course, in practice the system was not correct; differences started to appear in a number of areas. Each unexpected result was reviewed with the users to investigate the problem further, working through each example to identify the bug.
  • Log,fix,and retest defects cycle Once a bug was identified,it was logged and passed back to the developers for correction.Once fixed,the software was retested using the regression testing tools, iterating round this loop as many times as was necessary until all the bugs were resolved.
  • Changes to facilitate testingIn the options market,option pricing depends on the time to expiry,that is,the difference between current date and the expiry of the options contract. The solution took the current date from the computer system clock. We needed to change the software to take the current date from a database field so that if we ran the same test on different days we would get identical results.

Finally we got to a point where we had resolved all the material bugs and the system was successfully released. Following release, only one bug was discovered, which we were then able to track back to an item that had been signed off incorrectly. This result confirmed the suitability and success of the agile approach that we had adopted.

Face Book Twitter Google Plus Instagram Youtube Linkedin Myspace Pinterest Soundcloud Wikipedia

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

Agile Testing Topics