matrix-org / matrix-org/complement-crypto
Allow UI introspection of test environments
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 18
- Forks
- 12
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 6
Description
If you make a room with Alice and Bob and send messages, it would be nice if we could provide a way for Element X or Element Web R to hook into one of these accounts so the test author can:
- see if the test configuration makes sense
- sanity check for any obvious errors that the test is not catching
For Element X this would just involve dumping the sqlite directory somewhere and then making the app read it. For Element Web R this would involve exposing the Chrome session of the client instance. The latter feels doable at this stage.
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 test room/account setup and the client-instance handling for Element X and Element Web R. Investigate how a test could expose the SQLite directory or Chrome session, and consider the work complete when a test author can inspect a running test environment and sanity-check its state through one of those clients.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sqlite
- Domain
- developer-experience, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100