Build & Test Capabilities

It involves everything from the capability to write and build code to the different types of testing of the code.

Below is a list of the capabilities with a short description and possible link to the different components providing that capability.

Software Generation Capabilities

Most of our code is written manually.

See development application components to get an overview of our tools and applications.

We use Terraform to define infrastructure.

The project uses .Net, Java, or Typescript compilers.

The project can build different software packages.

See development application components for details on how we do this.

We use Auzure Pipelines to build the source code for releases..

See development application components to get a overview over tools and application we use.

Github Actions are used for Continuous Integration.

When a pull request is created a build is triggered that builds the code and run unit and integration tests.

This is setup for relevant GitHub repositories.

Examples

For Altinn 2, we have manual test scripts in TFS. For Altinn 3, there are no manual test scripts.

The DevOps teams use Github to store the automatic test scripts.

For functionality, for Altinn 2 platform, the tracking is performed in TFS.

For automatic tests covering Altinn 3 functionality, this is tracked in Azure Pipelines.

The DevOps team can perform automatic functional testing. Testing is done with the help of Cypress and runs from Azure DevOps pipelines.

Devops

As part of the development, unit tests are created. The tests run for every pull request.

Sonarcloud verifies test coverage.

The teams use Postman for API testing.