Testing Overview

Building testing frameworks from scratch requires a lot of boilerplate code. It is also hard to know how to get started without examples.

To ensure the quality and reliability of your software projects, Ensono Stacks includes a range of integrated testing frameworks. These frameworks are designed to be easily bootstrapped and customized to fit your specific project needs. The tests integrated within each stack is summarised in this table:

Testing Type	.Net	Java	Frontend/NX	Data
Unit	✔	✔	✔	✔
Component	✔	✔	N/A	✖
Integration	✔	✔	N/A	✖
Contract	✔	✔	✖	N/A
Data Validation	N/A	N/A	N/A	✔
Functional	✔	✔	✔	✖
End-to-end	N/A*	N/A*	✔	✔
Linting	✔	✔	✔	✔
Vulnerability Scanning	✔	✔	✔	✔
Static code analysis	✔	✔	✔	✔
Security	✔	✔	✔	✔
Performance*	✖	✖	✖	✖

* Tests are available as a standalone solution that can be applied to the Stack.

Types of Testing

This summary outlines key areas of testing integrated within Ensono Stacks as well as some standalone solutions for testing Stacks applications.

Unit Testing

All of our Stacks come with Unit testing built in. This ensures that each individual unit (function/method) works in isolation. Examples:

• Java stack
• DotNet stack
• Data stack
• NX plugins

Component Testing

Our .Net and Java Stacks come with Component testing built in. Components tests take the individual component (I.e. Service bus implementation, API, Function App, etc.) and test it as a whole in a white box format. All external dependencies are mocked. This allows us to ensure that, before deployment, our component is functioning as expected in isolation, reducing the risk of deployment and liklihood that post-deployment issues are due to this components functionality. Examples:

• Java stack
• DotNet stack

Performance Testing

Performance testing ensures that your application can handle the expected load and perform well under stress. Ensono Stacks uses Gatling for performance testing. Further information can be found here.

UI Testing

Playwright

Playwright is the preferred tool within the Ensono Stacks. It is a powerful tool for cross-browser web automation. It supports multiple browsers and provides capabilities for both functional and visual regression testing. For more details on how Ensono utilizes Playwright within Ensono Stacks, refer to the following documentation:

• General Testing: Testing with Playwright
• Visual Regression Testing: Playwright Visual Testing
• Accessibility Testing: Accessibility Testing with Playwright
• Applitools Integration: Playwright with Applitools Eyes

API Testing

Ensono Stacks .NET

The Ensono Stacks .NET includes a functional testing framework using xUnit and BDDfy. This framework allows you to write and run tests to ensure that your API behaves correctly. For more details, refer to the Functionally Testing the API documentation.

Ensono Stacks Java

The Ensono Stacks Java includes an API testing framework using Serenity BDD and Rest Assured. This framework allows you to write and run tests to ensure that your API behaves correctly. For more details, refer to the Running API tests with Serenity documentation.

Contract Testing with Pact

Contract testing ensures that the interactions between services are working as expected. Ensono Stacks uses Pact for Bi-Directional contract testing. For further information please refer to the API Contract Testing with Pact documentation.

Functional Testing

ServiceBus Testing

Ensono Stacks .NET includes comprehensive functional and unit tests for ServiceBus operations to ensure the correct handling of topics, queues, and messages.

The GitHub repository folder containing the ServiceBus unit tests can be found here. These tests ensure that the various components of the ServiceBus, such as validators, serializers, routers, listeners, and custom processors, function correctly and handle different scenarios as expected.

Functional tests can be found in the GitHub repository folder here. Key areas of coverage include:

• Adding messages to the queue
• Checking the existence of topics
• Reading messages from the queue
• Clearing messages from the queue

CosmosDB Testing

Ensono Stacks .NET includes unit and integration tests for CosmosDB operations to ensure correct data handling and repository functionality. These include:

• Unit tests for verifying the repository implementation and its functionality using a mock repository. The unit test example are in the CosmosDbMenuRepositoryTests.cs in this repository folder.

• Integration tests for CosmosDB Document Storage, validating communication with CosmosDB, data encoding/decoding, and various search operations, including tests for single/multiple fields, ordering, partition keys, and SQL queries. The integration tests are in the repository folder here.

SonarCloud

Ensono Stacks integrates with SonarCloud for our Static Code Analysis. This analysis includes scans for:

• Security
• Reliability
• Maintainability
• Test coverage
• Duplicated code
• Coding standards

Infrastructure Testing

Within the AKS infrastructure, there is a suite of infrastructure tests using the tool InSpec. These tests check the expected state of resources deployed into Azure to ensure the quality of the infrastructure that our Stacks applications are deploy to.

Getting Started

To get started with testing in Ensono Stacks, refer to the detailed documentation for each testing tool and framework. Each guide provides setup instructions, configuration details, and example tests to help you integrate testing into your development workflow.

For more information on setting up your workspace, see the Getting Started guide.

Conclusion

Ensono Stacks offers a robust set of tools and frameworks to ensure the quality and reliability of your software projects. By leveraging these tools, you can automate testing, catch issues early, and deliver high-quality software with confidence.