What do you mean by Agile Testing Process Agile Testing

The details of the agile testing process we are currently following are shown as follows,but this process has grown and developed over time and I’m certain it will continue to change and evolve:

  • Co-location of test and development–This allows test input during the design and development phase, and development input in the test phase.
  • Unit tests, developed alongwith the code,are run in every build–Any unit test failures result in a “bad build,” which must be fixed immediately.
  • Static analysis is run against the code in every build– Any static analysis problems result in a “bad build,” which must be fixed immediately.
  • Automated build verification test(BVT)of every good buildtests basic core function on a single distributed platform.
  • Automated functional verification test (FVT) of every good build– test more functions,including across every operating system that we need to support.
  • Development uses “stories” as the unit of function– Each story has “success criteria” that must be demonstrated at the end of the iteration.These success criteria clarify any ambiguity when trying to determine if a story was complete.
  • Reduced test planning– Only do actual test plans for the more complex stories.Simple stories are tested using exploratory testing.
  • Automate what we can– Rather than automating everything,we automate only key tests because automating everything would take too long.Try to automate the tests that will give best coverage and the most complex areas of code.
  • Pseudo-translation and accessibility testing every iteration– We used tools to test that all visible text is translated/translatable and that GUIs are accessible in every iteration.This prevents a backlog of problems building up in these areas and reminds development to write their code appropriately.
  • Define “test stories” as part of the planning process/burndown– This allows us to track large test work items such as setting up the automation infrastructure,adding major new test automation function, and “test-only” work-items such as globalization verification testing and translation verification testing.
  • Introduction of system verification tests(SVTs)as test/development stories– System tests such as long runs,stress, load,large topologies,and so forth,take a lot of time and effort to do properly,so these are entered as stories in the planning for the iteration.If the SVT stories do not get prioritized into the iteration,thetesting does not get done.
  • Everyone is a software engineer– There is no hard line between testers and developers.People specialize in certain areas,but developers do some testing when they are free,and testers do development and fix defects when they are free.
  • Low defect backlog– We carefully track the number of open defects toward the end of each iteration with a requirement of no high-severity defects and a target of less than fifteen low-severity defects open at the end of every iteration. This prevents a defect backlog from growing over time.
  • Lessons learned and reflections for test in every iteration– Along with the development side of things,the test team have a “lessons learned” session at the end of every iteration.We have actions for what we can change in our testing process to make things better.This keeps our testing processes as up-to-date and meaningful as possible.


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