Solutions of the Agile Approach Agile Testing

The agile approach to automated unit and integration testing brought a number of clear benefits to the project:

  • The focus on thorough and continuous automated regression testing certainly reduced the overall number of bugs at any point during the project’s life cycle,but it also helped developers to work side-by-side without inadvertently interfering with each other’s efforts.Unit testing with mock objects allowed the development of code units in virtual isolation of each other.
  • Since each unit test was focused on a particular part of the system,it could therefore be quite thorough.In some cases,for example,it was used to simulate failure conditions or housekeeping functions that would be hard to arrange or observe through the user interface.
  • Writing tests before code forced developers to reason about what the code needed to do before deciding how it was going to work.This separate definition of function and design tended to produce cleaner code and tests that were well aligned with stated requirements rather than the developed solution.In turn,this made the tests and code easier to verify.

The things that worked less well were generally related to the pain of improving the quality and test coverage of legacy code.Poor code encourages poor tests and poor tests can slow the pace of change.The choice and use of tools is also vitally important.Arguably,however,most of these problems were uncovered by the adopted approach rather than fundamentally caused by it.

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

Agile Testing Topics