Create a smoke test for installers
- Dominant language
- Jinja
- Stars
- 168
- Forks
- 77
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 12
Description
Would like to design/create a smoke test consisting of several basic checks to be run or triggered at the end of the installer jobs to verify the installers are sane.
Verify each set of installers has some testing in place and documented:
- [ ] Linux installers - x64 linux installers are tested, need https://github.com/adoptium/installer/issues/375
- [ ] Windows installers - https://github.com/adoptium/installer/issues/559
- [ ] Mac installers
Related to https://github.com/AdoptOpenJDK/TSC/issues/151 and https://github.com/AdoptOpenJDK/openjdk-tests/issues/1421
Contributor guide
Research direction
Start by reviewing the installer jobs and the linked Linux and Windows issues, then check the related TSC and openjdk-tests issues for existing requirements. Done means each Linux, Windows, and Mac installer set has basic smoke checks that run or are triggered at the end of its installer job, with the coverage documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, release, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100