digidem / digidem/comapeo-core-react-native
Use separate Browserstack org for running e2e tests
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 1
- Forks
- 0
- Avg merge
- 8h 24m
- Merged PRs (30d)
- 9
Description
We currently use the same Browserstack org as the CoMapeo Mobile repo. Ideally a separate org can be used to prevent hitting concurrent device run limits that would cause higher priority workflows in the mobile repo to slow down, as well as allowing more device + API coverage for the e2e tests in this repo.
This issue is less urgent for now since the mobile repo has switched to running e2e tests on a less frequent schedule.
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
Review the e2e test setup that currently uses the shared BrowserStack organization, then compare its needs with the CoMapeo Mobile repository's setup. Done means this repository uses a separate organization and can expand device and API coverage without causing concurrent-run limits for the mobile repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100