bsky-app/docs/testing.md
Ansh 8e9cf182c2
Performance optimization (#1676)
* upgrade sentry to support profiling monitoring

* remove console logs in production builds

* feeds tab bar and bottom bar animation centralized

* refactor FeedPage out of Home

* add script to start in production mode

* move FAB inner to reanimated

* move FABInner back to `Animated` RN animation

* add perf commands

* add testing with Maestro and perf with Flashlight

* fix merge conflicts

* fix resourceClass name in eas.json

* fix onEndReachedThreshold in Feed

* memoize styles

* go back to old styling for LoadLatestBtn

* remove reanimated code from useMinimalShellMode

* move shell animations to hook/reanimated for perf

* fix empty state issue

* make shell animation feel smoother

* make shell animation more smooth

* run animation with autorun

* specify keys for tab bar properly

* remove comments

* remove already imported dep

* fix lint

* add testing instructions

* mock sentry-expo for jest

* fix jest mocks

* Fix the load-latest button on desktop and tablet

* Fix: don't move the FAB in tablet mode

* Fix type error

* Fix tabs bar positioning on tablet

* Fix types

---------

Co-authored-by: Paul Frazee <pfrazee@gmail.com>
2023-10-13 18:54:35 -07:00

1.6 KiB

Testing instructions

Using Maestro E2E tests

  1. Install Maestro by following these instuctions. This will help us run the E2E tests.
  2. You can write Maestro tests in __e2e__/maestro directory by creating a new .yaml file or by modifying an existing one.
  3. You can also use Maestro Studio which automatically generates commands by recording your actions on the app. Therefore, you can create realistic tests without having to manually write any code. Use the maestro studio command to start recording your actions.

Using Flashlight for Performance Testing

  1. Make sure Maestro is installed (optional: only for auomated testing) by following the instructions above
  2. Install Flashlight by following these instructions
  3. The simplest way to get started is by running yarn perf:measure which will run a live preview of the performance test results. You can see a demo here
  4. The yarn perf:test:measure will run the scroll.yaml test located in __e2e__/maestro/scroll.yaml and give the results in .perf/results.json which can be viewed by running yarn:perf:results
  5. You can also run your own tests by running yarn perf:test <path_to_test> where <path_to_test> is the path to your test file. For example, yarn perf:test __e2e__/maestro/scroll.yaml will run the scroll.yaml test located in __e2e__/maestro/scroll.yaml.