v0.14.8 Testing checklist #3417
Closed
xoscar
started this conversation in
Release testing
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Testing Tracetest
This is the checklist on what we should do to assert that Tracetest is working fine on each release version. On each version release, we can copy the contents of this template checklist and open a Github Discussion to start each test.
On Tracetest, we work in two ways to test the entire system and guarantee that everything is working fine. One is through automatic tests, where we run unit, integration, and end-to-end tests on Tracetest CLI, Web UI, and Server.
Another source of tests is the manual tests that we execute on each release, simulating users and checking if everything is ok on these tests.
Manual Tests
Our manual tests aim to do some sanity checks to see if the main features are working as expected. Usually, we run it on each Tracetest release.
Tests to validate on Release Candidate
Test server installation via CLI
TRACETEST_DEV
env for docker installTRACETEST_DEV
env for k8s installTest DataStore provisioning and basic test
/settings
page. The provisioned Data Store should be selectedTest Tracetest examples
Testing benchmark
Test specific features added/changed on this release:
Tests to validate on Final Release
Pipeline
Test CLI updates
Docs
Add Major Changes
Test specific features added/changed on this release:
Beta Was this translation helpful? Give feedback.
All reactions