- [Instructor] One of the quick impact
of properly testing your code
is the peace of mind that comes with it.
Knowing that core functionalities of your application
have been well-tested before being pushed to production
means you don't get called by 2:00 AM in the morning
to fix bugs.
Another major reason why we write tests
is to ensure that our code follows standards of clean
and quality code.
Quality code is code that is easy to understand,
maintain and also well-structured.
Quality code can also be relative to style guides
of the organization for which it is written.
Testing rules can be written
to ensure the style guide is enforced.
Code also needs to be tested in a team development project
to ensure that team members do not push bugs
into the central repository.
When a pull request is submitted,
tests run on the feature branch
before it is merged into the destination branch.
If the tests fail, the developer is notified
that there are bugs to be fixed before they can be allowed
to merge with the central repository.
Another major reason and a merit to testing
is in the value of the application.
The more bugs were remove from our application
through testing,
the more the value of the application increases.
It is therefore important to view testing
as the practice of increasing the value of an application
by removing its defects.
We can go on and on talking about why testing
is so important in software applications.
However, from the points discussed so far,
we can conclude that testing should be a standard practice
in our development flow as it helps detect
and remove defects from our applications.