Make changing server and database for changing integration tests easier
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 16
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
The server, and to a lesser extend the database, against which integrations tests are ran are not easily configurable.
While most are, the test runs against a hard-coded server url.
It should be easy to switch from a docker compose setup where everything is connected, to a setup where the servers connection to the remote "reproduction" database, to the actual production REST API.
Contributor guide
No contributing guide indexed for this repository
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 tests/identical_test.py and its hard-coded server URL, then inspect how the integration tests currently obtain server and database connections. Make the endpoints switchable between docker compose, the remote reproduction database setup, and production REST API without editing individual tests. Done means the integration suite can run against each setup through configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- databases, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100