MetaMask / MetaMask/metamask-mobile
Create a bitrise workflow for the tests that measures the response time of problematic screens
- Dominant language
- TypeScript
- Stars
- 3k
- Forks
- 1.7k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 669
Description
### What is this about?
This task's purpose is to create a workflow that will run in the smoke pipeline for the tests that measure screen responses.
To accomplish this we can follow a similar workflow setup as [here](https://github.com/MetaMask/metamask-mobile/blob/main/bitrise.yml#L883#L896)
Another point to note is that we should have a new tag that we would use to identify these tests. Perhaps call them "ScreenMeasurements" or whichever other name you can think of.
### Scenario
_No response_
### Design
_No response_
### Technical Details
_No response_
### Threat Modeling Framework
_No response_
### Acceptance Criteria
The workflow should run as part of the smoke pipeline
The test should run as part of the new workflow
### Stakeholder review needed before the work gets merged
- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)
### References
_No response_
Contributor guide
Research direction
Start by reviewing the analogous workflow in bitrise.yml around lines 883-896 and locating the screen-response tests that need a dedicated tag. Add the workflow to the smoke pipeline and ensure the tagged tests run in it; completion is verified when both acceptance criteria are met.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- ci-cd, mobile, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100