The Azure Mission-Critical reference implementation contains various kinds of tests used at different stages. These include:
- Unit tests. These validate that the business logic of the application works as expected. Azure Mission-Critical contains a sample suite of C# unit tests that are automatically executed before every container build.
- Load tests. These can help to evaluate the capacity, scalability and potential bottlenecks of a given workload and stack.
- Smoke tests. These identify if the infrastructure and workload are available and act as expected. Smoke tests are executed as part of every deployment.
- UI tests. These validate that the user interface was deployed and works as expected. Currently Azure Mission-Critical only captures screenshots of several pages after deployment without any actual testing.
- Failure Injection tests. These are done in two ways: First, the Azure Mission-Critical reference implementation integrates Azure Chaos Studio for automated testing as part of the deployment pipelines. Secondly, manual failure injection test can be conducted. See below for details.
Additionally, the Azure Mission-Critical Online repository contains a user load generator to create synthetic load patterns which can be used to simulate real life traffic. This can also be used completely independently of the reference implementation.
Distributed applications need to be resilient to service and component outages. Failure Injection testing (also known as Fault Injection or Chaos Engineering) is the practice of subjecting applications and services to real-world stresses and failures.
Resilience is a property of an entire system and injecting faults helps to find issues in the application. Addressing these issues helps to validate application resiliency to unreliable conditions, missing dependencies and other errors.
Manual failure injection testing was initially performed across both global and deployment stamp resources. Please consult the Failure Injection article for details.
Azure Mission-Critical integrates Azure Chaos Studio to deploy and run a set of Azure Chaos Studio Experiments to inject various faults at the global and stamp levels.
The Azure Mission-Critical reference implementation uses existing testing capabilities and frameworks whenever possible. The subsequent sections contain an overview of the used tools and frameworks.
- Locust for load testing
- Playwright for UI testing
Locust is an open source Load Testing framework. See locust on the Azure Mission-Critical-Online repository for more details about the implementation and configuration.
Playwright is an open source Node.js library to automate Chromium, Firefox and WebKit with a single API. See ui-test-playwright for more details about how UI testing works.