Extremes the Testing is a agile method, which places a testing in place of programming into the foreground of the software development. Extremes the Testing represents thus a reinforcement of the test-driven development.

With extremes the Testing the requirement of the test-driven development to have constantly executable software explained as the principle. The success ratio of the unit tests is held with 100 %. The implementation and success ratio of the acceptance tests serve as Metrik for the speed of the development procedure. While the test-driven development, extremes the Programming, which sees a testing as means for the purpose of program preparation, is e.g. the center of attention with extremes the Testing testing central. Extremes the Testing is a component some agiler processes.

Sometimes extremes Testing is used also only jokeful as name for test-driven development or extremes Programming. This use is however not completely correct. Extremes a Testing phase of some weeks can during the introduction by extremes Programming be used, in order to train the software developers in test-driven development.

Background

A goal extremes of the Testing is to hold the error number of a software as low as possible thus close zero. This is naturally usually a fundamental goal of the software development, however extremes the Testing is particularly exclusively concerned and practically with this aspect and no different one the software development. In order to achieve this goal, not the development of the desired goal product, but the development of an extensive test collection in the center of programming with extremes the Testing, which is to lead to an error free development process, is located. Differently than extremes the Programming extremes the Testing permits thereby no test omissions, also trivial tests must with extremes the Testing be programmed and accomplished.

Critical view

Extremes the Testing saves the danger to spend more time with the testing from software to when is meaningful. In addition Testing can lead extremes flexibility lacking, since changes draw a change on the specification or the draft also on a large number on tests.

Comparison with other beginnings

In the classical model of the software technology tests are downstream developed parallel and independently or at the outlet side. Tests are regarded as means for quality assurance (fulfilment of customer requirements, stability, reliability etc.), but not as means for software development.

With the test-driven development testing is included as a firm component into the development of the implementation. Tests serve to steer and advance the implementation. But for requirements (generally speaking as in the small one) tests are developed and implemented afterwards until the test confirms that the requirement is fulfilled. The degree of detail of the tests depends however on it, for like meaningfully the programmer the test judged. Trivial tests are not developed also with the test-driven development.

With extremes the Testing are developed for all requirements and components all conceivable tests, inclusive trivial tests.

Articles in category "Extreme Testing"

We found here 3 articles.

Related Websites

We found here 3 related websites.

• Dr. Dobb's | Extreme Testing | May 13, 2003
  Software tools and techniques for global software development. Dr. Dobb's features articles, source code, blogs,forums,video tutorials, and audio podcasts, ...


• Software Testing
  With the kind permission of Software Testing & Quality Engineering magazine, I am pleased to offer a PDF copy of my article in the March/April 1999 issue. ...


• SP99 Extreme for Web
  With Extreme Testing, you can develop software more quickly, with more confi- ... Extreme Testing is all about confidence. Unit Tests let ...