Skip to content

FEA502 Test Case

Test Case description Have different environments (staging, testing, production) with automated deployments to ensure smooth and controlled releases.
Test Case ID FEA502-TC01
Author/Designer Matias Korpela
Date of creation 25.3.2024
Class functional

Test description / objective

Have different environments (staging, testing, production) with automated deployments to ensure smooth and controlled releases.

Links to requirements or other sources

Test pre-state

  • The developer should be able to commit to the GitLab repositories

Test steps

  1. Make changes to code
  2. Commit to repo
  3. Wait for pipeline to run
  4. Check that changes are visible on staging/production environments.

Test end-state

  • The changes should be available on the staging/production environments

To be taken into account during test

  • The servers must be up and running

Test result (Pass/Fail Criteria)

Tukko running

  • PASS: Changes visible and website is up
  • FAIL: Changes not visible or website is down