Add E2E performance product tests

Open
#3,685 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
react-native, typescript
Domain
mobile, performance, testing

Research direction

Start by reviewing the existing E2E tests, which currently focus on errors, and the related context in pull request 3684. Cover app start, manually instrumented active spans, and navigation through react-navigation or expo-router, checking frames, app-start measurements, HTTP spans, and TTID/TTFD spans and measurements.

Written by the indexing model from the issue text.

Description

React-Native Tests Traces
Description

Currently, E2E tests only focus on errors.

### What scenarios to test?
- [ ] App start
- [ ] Manually instrumented active span
- [ ] Navigation react-navigation or expo-touter

### What should be checked?
- [ ] Slow/frozen frames
- [ ] Total frames
- [ ] App start measurement
- [ ] Http spans
- [ ] TTID/TTFD spans and measurements

Context:

Dominant language
TypeScript
Stars
1.8k
Forks
367
Avg merge
1d 6h
Merged PRs (30d)
94

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/sentry-react-native

All issues in getsentry/sentry-react-native

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.