posit-dev / posit-dev/images-shared
Expand Goss tests for Package Manager
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 22
Description
[!NOTE]
Moved from rstudio/platform-team#414
Context
Package Manager has the smallest goss test suite of the three products. Coverage could be expanded for service startup and repository management.
Current goss test templates
- https://github.com/posit-dev/images-package-manager/blob/main/package-manager/template/test/goss.yaml.jinja2 (100 lines)
Current coverage
Tests check: users, groups, packages, ports, processes, files, and commands.
Potential expansion areas
- Service startup and readiness verification
- API endpoint health checks
- Repository sync and package availability
- Configuration file validation
- License activation and status
- Multi-platform (amd64/arm64) specific checks
- Data directory permissions and ownership
Related: #458 (centralize common goss patterns)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with package-manager/template/test/goss.yaml.jinja2 and review its existing checks for users, groups, packages, ports, processes, files, and commands. Compare the potential expansion areas in this issue and review #458 for common Goss patterns. Done means the Package Manager Goss coverage is expanded for the selected service startup and repository-management checks.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100