MPCONFIG settings are not easily testable in API tests
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
In our API tests (REST Assured), I know how to set database settings at the start of a test and unset them at the end. This allows me to exercise functionality, increase code coverage, etc.
MPCONFIG settings are used increasingly but from what I can tell, it's not easy to test them from our API tests.
A case in point is this PR I'm working on:
- #10122
I created some new MPCONFIG settings and I'd like to make sure they're working. It's easy enough to manually test but how do I vary MPCONFIG settings in API tests?
See also the related thread in Zulip.
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 the API tests using REST Assured and compare their existing database-setting setup and cleanup with the MPCONFIG settings discussed in PR #10122. Read the linked Zulip thread for the intended testing approach; done should include a documented, repeatable way to vary MPCONFIG settings in API tests and verify the new settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100