As developers, we usually aim at working on challenging problems, trying to navigate through the complex connections, and coming up with a solution. But how many times do we care to look at all the possible ways through which our code can fail to provide the expected outcome? As much as it is hard to try to break something that we as developers have written ourselves, it forms one of the most important aspects of the development cycle.
This is the time when testing becomes an important aspect of the development life cycle. The aim of application testing can be summed up by answering the following questions:
- Are the individual components in the code performing as per the expectations?
- Does the flow of the code from one component to another as is desired?
- Was the final outcome of the application the same that we thought of?
- Are there some deviations in the standard behavior?
- Did the application handle all the expected scenarios and provided a fail-safe over for the unexpected...