ODS 3.0 Dev Env and E2E Tests - opendevstack/PMC GitHub Wiki
Owners(s): @stitakis and @georgfedermann / Size: XL / Benefit: High increase of consistency & developerment productivity / Status: in-progress
Goal: Full automated creation of a virtual machine with full installed ODS version + dependencies (Atlassian stack) E2E Tests will assure that the ODS installation is done properly and is fully functional
Roadmap:
First cut
- #549: ODS Dev Env automated installation on centos (script installation of ODS in a centos 7.7+ VM w/o Atlassian stack, nexus and sonarqube) for local E2E Test "Create project"
- #488 Automated scripted installation of Sonarqube in ODS image
- #288 Automated scripted installation of Nexus in ODS image
- E2E Test of quickstarters pipelines (create component, build components) without ProvApp calling webhook proxy
Status: Done
CI Environment
- Scripted creation of VM Ware image (to considers alternatively VirtualBox, AMI, Vagrant, etc...)
- Setup minimal CI infrastructure (in AWS) that integrates with github (polling strategy), creates VM images of ODS Dev Env and publish to S3.
Status: not started
Full installation
- #549 Automated scripted installation of Atlassian stack (docker images bitbucket, jira, confluence and crowd) in ODS image (resolve licenses installation)
- #549 Automate ProvApp configuration in ODS Dev Env
Status: done
E2E Test
- #644 Quickstarters test
- E2E Tests project creation and components (quickstarters) using ProvApp that capture screenshots and generate E2E Test document
Status: in-progress