Test After Development

Introduction

Software is split into the following two parts:

• The application code implements the software features.
• The test code includes the tests that test the behavior of the application code.

There are two high-level test process approaches. One emphasizes writing test code after the application code, and the other emphasizes writing test code before the application code. This lesson focuses on the first approach.

Test after development approach

The test after development (TAD) approach is when the test code is written after the application code. It emphasizes designing the software by first delving into the implementation of the application code. This concept is illustrated below:

Disadvantages of TAD

There are a few disadvantages of the TAD approach:

• Bias: Focus may inadvertently shift to testing implementation rather than the actual requirements.
• Overcomplication: The application code may include sections that are redundant or not required at all.
• Slow development time: The application code may have testability challenges that only surface when attempts are made to write the test code.
• Poor design: Focusing too much on the implementation details may lead to poor design because the focus is placed on implementation.
• Incomplete

...