Definition of an Agile Testing Process Agile Testing

While Section3.6.3 provides a summary of the Evo process principles, the Confirmit AS interpretation of the Evo method was as follows:

  • Identify stakeholders – end users,superusers,support,sales,IT operations,etc.
  • Define stakeholders’ real needs and the related product qualities – what was actually needed to support their business needs.
  • Identify past/status of product qualities and your goal–that is,how much you want to improve.
  • Identify candidate solutions for meeting your goals.
  • Develop a step-by-step plan for
  • delivering improvements to the process,and hence the product;
  • providing deliveries every week(with respect to stakeholder needs and product quality goals);and
  • measuring progress:are we moving towards our goals(again, with respect to stakeholder needs and product quality goals)?

Guided by Evo,Confirmit AS put in place a new requirements standard that meant that requirements had to

  • be clear and unambiguous,
  • be testable,
  • be quantified,
  • not involve solutions,and
  • have a stakeholder focus.

The focus with requirements had to be on the day-to-day operations of the Confirmit√ users and not represent a list of what they might or might not like. Following this process, all of the requirements for a new release of Confirmit√ Were defined and documented in just one week, as compared to the previous norm of four to five weeks.
In terms of Evo cycle time, a one-week-long Evo step was adopted in which the key activities were as follows:

  • On the Friday:
  • The Project Manager(PM) elivers the detailed plan for the next week’s version of the software(let’s call it Version N)to the customer Chief Technical Officer(CTO)prior to attending a weekly project management meeting.
  • The CTO reviews and approves or rejects the design and records their comments.
  • The PM and CTO attend the weekly project management meeting to discuss the Version N detailed plan and review CTO comments.
  • The developers focus on general maintenance and documentation tasks.
  • The QA team runs final build and setup for that week’s developed version(let’s call it Version N-1),installs setup on test servers,and performs initial crash test1 of Version N-1 prior to its release.
  • On the Monday:
  • The developers first generate the tests required to validate Version N and then begin development of the code.
  • The QA team reviews the results of the continuous integration(CI)process and reviews test plans and tests for Version N.
  • The users begin to use Version N-1 and compile feedback for the developers.
  • During Tuesday and Wednesday:
  • The developers continue to generate the tests required to validate Version N and develop the associated code.
  • The developers meet with the users to discuss the feedback from using Version N-1.
  • Incorporating the feedback from the users,the developers continue to generate the tests required to validate Version N and develop the associated code.
  • The QA team reviews the results of the CI process and reviews test plans and tests for Version N.
  • On the Thursday:
  • The developers complete the final tests for Version N,code,and execute the tests.the developers also complete the graphical user interface tests for the previous week’s version of the software(let’s call this Version N-2).
  • The QA team reviews the results of the CI process and reviews test plans and tests for Version N.1

A testing technique used to determine the fitness of a new build or release of the application under test to undergo further, more thorough testing.


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

Agile Testing Topics