CyberCoveLLC/threshold-ui
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: ✏️ fix flag name and a11y references

Browse Source
This commit is contained in:
cameronperera authored and Cameron Perera committed 2025-08-19 10:51:44 -05:00
1 parent 7801429530
commit 84359d8e79
2 files changed
+10 -10
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

ui/admin/README.md
+5 -5
View File
@@ -82,13 +82,13 @@ These environment variables may be used to customized the build.
| -------- | ------------- | ----------- |
| `APP_NAME` | Application Name | The user-facing name of the application, appearing in titles, etc. |
| `API_HOST` | | The host of the API, if different than UI (e.g. https://example.net:1234). |
| `DARK_MODE` | | Enable (`true`) to set the test browser appearance to dark for running tests in dark mode. |
| `COLOR_THEME` | | Define (`dark`) to set the test browser appearance to dark for running tests in dark mode. |
### Running Tests
* `pnpm test` runs full tests in random order with coverage
* `ember test --server`
* `DARK_MODE=true ember test --server` runs tests in dark mode
* `COLOR_THEME=dark ember test --server` runs tests in dark mode
Keep in mind that tests are executed in random order. This is intentional
and helps to prevent hard-to-debug order dependencies among tests.
@@ -102,9 +102,9 @@ Write acceptance tests like normal. Our a11y testing strategy will automatically
run `a11yAudit()` after [specific helper actions](tests/test-helper.js#L26), like visit, click, and fillIn.
Our a11y tests have their own pnpm commands:
* `pnpm test-ally` runs a11y tests for light and dark mode
* `pnpm test-ally:light` runs a11y tests just for light mode
* `pnpm test-ally:dark` runs a11y tests just for dark mode
* `pnpm test-a11y` runs a11y tests for light and dark mode
* `pnpm test-a11y:light` runs a11y tests just for light mode
* `pnpm test-a11y:dark` runs a11y tests just for dark mode
#### Light vs Dark Mode A11y Tests
ui/desktop/README.md
+5 -5
View File
@@ -102,7 +102,7 @@ These environment variables may be used to customized the build.
| `BYPASS_APP_UPDATER` | Disable app updater feature. For development use only. |
| `DISABLE_WINDOW_CHROME` | Disable window chrome. For internal use only. |
| `ENABLE_MIRAGE` | Enable (`true`) or disable (`false`) mirage. Default value is `true`. |
| `DARK_MODE` | Enable (`true`) to set the test browser appearance to dark for running tests in dark mode. |
| `COLOR_THEME` | Define (`dark`) to set the test browser appearance to dark for running tests in dark mode. |
### Building for Production
@@ -140,7 +140,7 @@ These environment variables may be used to customized the build.
### Running Tests
- `pnpm test` runs full tests in random order with coverage
- `DARK_MODE=true ember test --server` runs tests in dark mode
- `COLOR_THEME=dark ember test --server` runs tests in dark mode
Keep in mind that tests are executed in random order. This is intentional
and helps to prevent hard-to-debug order dependencies among tests.
@@ -154,9 +154,9 @@ Write acceptance tests like normal. Our a11y testing strategy will automatically
run `a11yAudit()` after [specific helper actions](tests/test-helper.js#L26), like visit, click, and fillIn.
Our a11y tests have their own pnpm commands:
* `pnpm test-ally` runs a11y tests for light and dark mode
* `pnpm test-ally:light` runs a11y tests just for light mode
* `pnpm test-ally:dark` runs a11y tests just for dark mode
* `pnpm test-a11y` runs a11y tests for light and dark mode
* `pnpm test-a11y:light` runs a11y tests just for light mode
* `pnpm test-a11y:dark` runs a11y tests just for dark mode
#### Light vs Dark Mode A11y Tests