diff options
| author | Eric Bailey <git@esb.lol> | 2023-12-05 14:50:56 -0600 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-12-05 14:50:56 -0600 |
| commit | 5f553c29dfdac1bf81debe5e28983a9dbe74bd7f (patch) | |
| tree | 6bfabab5623050aed65cdbb8dcc6474aa8f9d9cb /docs | |
| parent | ed5a97d0fab249cab91539f0c4dc7d3084bc59a8 (diff) | |
| download | voidsky-5f553c29dfdac1bf81debe5e28983a9dbe74bd7f.tar.zst | |
E2E 🟢 (#2092)
* Add logged out e2e ctrl, fix login test * Fix log handling via env vars in expo * Fix create account test * Upgrade dev-env * Fix home screen tests * Fix composer tests * Fix curate-lists tests, split in two * Fix invite codes test * Fix curate-lists tests * Give up on mergefeed test * Fix mod lists * Fix app view url * Fix profile tests * Fix profile test with hack * Keep using globals * Fix two more * Fix thread view * Better skip for merge feed * Revert debug code
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/testing.md | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/docs/testing.md b/docs/testing.md index 123c58ebc..e9b9445e0 100644 --- a/docs/testing.md +++ b/docs/testing.md @@ -1,5 +1,8 @@ # Testing instructions +Make sure you've copied `.env.example` to `.env.test` and provided any required +values. + ### Using Maestro E2E tests 1. Install Maestro by following [these instructions](https://maestro.mobile.dev/getting-started/installing-maestro). 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. @@ -11,4 +14,4 @@ 2. Install Flashlight by following [these instructions](https://docs.flashlight.dev/) 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](https://github.com/bamlab/flashlight/assets/4534323/4038a342-f145-4c3b-8cde-17949bf52612) 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`. \ No newline at end of file +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`. |