Agile QA

"Last week was good, yesterday was fast, and tomorrow has to be faster." 

Making the leap to agile software development can be fun if you are a project manager or business analyst, nerve racking if you are a developer, and a nightmare if you are a software quality engineer.  Whether you are just getting started in agile processes or are a veteran Scrum Master, CTS has three basic goals while testing in an agile process:

  • Test early
  • Test the process
  • Learn

Keeping up with risks, test cases, test results, automation, and performance tests can be very challenging in the agile world. Your first goal is to start testing early at a unit and component level of the system. CTS starts by quickly identifying test candidates for automation. The key to agile automation is at these unit and component levels since user interfaces are in a constant form of change. The more automation applied to these levels of testing, the more efficient your process will be.

The last two goals must go hand in hand. During retrospective processes, CTS identifies flaws in the agile process based on various metrics found in testing. With proper root cause analysis, CTS can take an agile process and make it faster.