Lessons Learned in The Agile Test-driven Methodology Experiment Agile Testing

Summarizing this simple experiment, one can find that, using the agile TDD methodology in development and testing:

  • Not much additional cost is incurred; when the developing teams are familiar with methods used, the extra time needed is rather small(less than 10%).
  • Substantially (about 50%)fewer defects are found in the source code. Also important is that the prepared code is amenable to refactoring. Analyzing the Hammurapi reports, one can find the proper scheme for code development.

Coincident with coding standards.

Coincident with coding standards.

On the other hand, we also want to underscore some weaknesses of the TDDmethod:

  • When we used the TDD method, the rule everything or nothing stands–if we break before finishing all tests(e.g., because there is no more time), we do not obtain anything; the module does not exist.
  • TDD does not replace unit testing–if we are working to a contract that states that unit testing has to be completed, we are obliged to prepare and execute these tests in addition to the TDD tests.
  • It is an agile methodology; hence, some organizations reject it. The last remark is at least controversial;the first two are much more important. However–in our opinion– he gain(a greater than 50% reduction in defects with only 10% additional time)is an interesting argument for using this method.

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

Agile Testing Topics