Release Pipeline
Everything starts from a commit, typically for a feature development. This should automatically trigger a build job on our CI server; the unit tests is also included in the job.
a. If any automation test needed for the feature, the automation cases can be implemented by tester in parallel.
If everything is OK, we can deploy everything in stage, this step is currently manual. Note: the deploying steps also include a step to report build version to winterfell.
The regression can be automatically trigger by this report on winterfell side upon the report
a. Additional exploratory tests and load tests might need to manually perform at this moment as it has better chance to discover defects.
winterfell offers the interface to analyze the test results
a. If regression failed, the failure analysis is performed. The additional patch is requested
Code merge from develop into master, which triggers again the build job and unit tests.
Deploys the build in production and reports winterfell
a. smoke test is triggered to quickly determine if anything suspicious during deployment. A rollback is executed in case of trouble
Components
- SCM (github)
- Niagara (automation test suite)
- Winterfell (infrastructure)
- CI Server
- Cloud (aws)
Test Flow
アニメ
