acceptance tests with different combinations of apps disabled/enabled
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 16
- Forks
- 16
- Avg merge
- 11h 11m
- Merged PRs (30d)
- 1
Description
it will be good to have a test matrix that runs all the API and webUI acceptance tests with different combinations of apps disabled/enabled.
e.g. a first cut would be to disable all core-bundled apps that are possible for sysadmins to disable. Then let all the tests run (except of course tests specific to the disabled apps), and see what happens.
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 by locating the API and webUI acceptance-test entry points and the configuration used to disable or enable apps. Review which core-bundled apps sysadmins can disable, then determine how tests specific to disabled apps are excluded. Done means the acceptance tests run across the requested app combinations and expose failures outside disabled-app-specific tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- api, frontend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100