Final reuslts Agile Testing

Potential adopters of such approaches should not be overawed;this isn’t rocket science. Here are some simple guiding principles that we identified:

  • The earlier we find a problem, the less it costs to fix it.
  • Successful agile quality is not a technology issue, but a cultural one:
  • Everyone in the team is responsible for the quality of our component.
  • Define the automation vision early and stick with it.
  • Start your automation with something simple and build on it.
  • Remember that over the course of time your automation will grow; plan for this and don’t let it consume you.
  • When starting out, be very clear on why you are embracing automation and early testing. The cost factor is the primary driver and helps get buy-in across the whole team. We spent a lot of time reiterating to the delivery team that everyone was responsible for the component quality and that we could achieve high quality through automation.
  • There is always the temptation to architect yet another automation framework at the start of the project. Don’t! Look around at the simple tools that already exist(like JUnit) and build on them as required. Developers and testers are much more likely to use something simple that is quick and easy to use.
  • Once you have some automated tests in place, start measuring their effectiveness. There are many code coverage tools in the market, but start with something simple like EMMA(for Java coverage) to give you a picture of what your tests are doing. We started our measurements at a very crude level (just measuring class coverage). This made it easy for us to achieve high scores early and psychologically helped gain acceptance from the team. Later on we switched to more fine-grained analysis(method and branch coverage)out only after the process had become well established.
  • All our figures were graphically displayed for all to see–a great motivator!
  • We generated over 7,000 unit tests alone that ran as part of every build.
  • Do remember–ode cove orageitself does not improve
    product quality,actionsbased on its results can!
  • When your automation is running regularly and growing with each iteration, remember to keep an eye on its size and how long it takes to run. While the perception is always that lots of tests mean lots of good testing, beware of the automation beast and how it will end up consuming all the time and resource you have.
  • We have had great success with our laser-guided targeting of tests, but it is also worth considering regular refactoring of your test suites. This way you can purge anything that is not adding value and help to keep your regression capability lean and agile.

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

Agile Testing Topics