digidem / digidem/comapeo-core-react-native
Make @comapeo/core's tests shareable with core-react-native
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1
- Forks
- 0
- Avg merge
- 8h 24m
- Merged PRs (30d)
- 9
Description
Context
Milestone-doc nice-to-have. We re-implement a lot of behaviour that core already tests; running (a subset of) core's tests against the RPC-bridged manager would catch divergence between core and the bridge.
Scope (to refine)
- Investigate making core's tests runnable against core-react (and then core-react against core-react-native).
-
assertpolyfill for the Jasmine-based React Native test runner. - Decide which core suites are meaningful across the IPC boundary.
Depends on / relates to the backend test infrastructure (#38) and the e2e suite.
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 reviewing the core test suites, the core-react-native Jasmine-based test runner, and the related backend test infrastructure in #38. Determine which suites can run across the IPC boundary and what assert polyfill support is needed; done means a documented subset runs against the RPC-bridged manager and can detect divergence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin, react-native
- Domain
- mobile-dev, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100