matrix-org / matrix-org/mx-tester
We need to test with sophisticated configurations
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 8
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Recent experience shows that deploying modules that pass tests with vanilla Synapse isn't a guarantee to ensure that it won't break a sophisticated deployment.
We need a configuration that uses e.g. workers, non-trivial storage, etc.
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
The issue names no files, tests, or entry points. Start by locating how mx-tester defines its deployment configuration, then determine how to represent workers and non-trivial storage; done means a sophisticated configuration is exercised successfully rather than only vanilla Synapse.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- infrastructure, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100