How to test “untestable” applications
Testing of calculator №0. The beginning
Testing of calculator №1. Configuring of infrastructure. Adding of DUnit
Testing of calculator №2. Adding of business-logic test using visual controls
Testing of calculator №3. Expanding of test coverage
Testing of calculator №4. Changing of application’s architecture
Testing of calculator №5. Testing through “new architecture”
Testing of calculator №6.1. Testing using etalons
Testing of calculator №6.2. Testing using pseudo-random data
Testing of calculator №6.2.1. Applying of “classical TDD”
Testing of calculator №6.2.2. Processing of false data and boundary conditions
Testing of calculator №7. Comparing of floating-point numbers. Details about tests architecture
Repository
Testing of calculator №0. The beginning
Testing of calculator №1. Configuring of infrastructure. Adding of DUnit
Testing of calculator №2. Adding of business-logic test using visual controls
Testing of calculator №3. Expanding of test coverage
Testing of calculator №4. Changing of application’s architecture
Testing of calculator №5. Testing through “new architecture”
Testing of calculator №6.1. Testing using etalons
Testing of calculator №6.2. Testing using pseudo-random data
Testing of calculator №6.2.1. Applying of “classical TDD”
Testing of calculator №6.2.2. Processing of false data and boundary conditions
Testing of calculator №7. Comparing of floating-point numbers. Details about tests architecture
Repository
Комментариев нет:
Отправить комментарий