Complete 360 Testing

Following on from my previous post[^] about completing the build pipeline for our ASP.NET Web API services build process, I have also completed the unit testing and integration testing too. For every class / method there is a corresponding unit test. For every layer in the architecture, there are suites of tests. From the Controllers, to the Models, to the data layer and services, there are tests that exercise each particular part of the code-base.

These are developed during the development cycle, and added to the build once the code is checked in so they can then be exercised during the build process.

Most recently I have created a suite of tests that get executed after deployment that run a battery of tests against the actual (non-production) deployed endpoint. This is the perfect complement to the unit tests that are executed during the build. This ensures that the RESTful services operate correctly from their deployment location. We can use the output from these tests to provide evidence of scalability, performance and other infrastructural requirements.

We can be absolutely certain that after each code check-in (which triggers a build, which triggers a deployment) that the services operate correctly.