Skip to content

[Drift Audit] Maestro rule doc lists stale test category directories #9382

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
daxmobile wants to merge 1 commit into
base: develop
Choose a base branch
from
Draft

[Drift Audit] Maestro rule doc lists stale test category directories #9382

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 21 additions & 15 deletions .cursor/rules/maestro-ui-tests.mdc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,25 +18,31 @@ keywords: ["maestro", "ui tests", "testing", "maestro cloud", "tags"]

## Types of UI tests
The Maestro tests are organized into the following (non-exhaustive) main categories:
- `ad_click_detection` - Tests for ad click detection functionality
- `ads_preview` - Tests for Android Design System (ADS) preview functionality
- `app_tp` - App Tracking Protection tests
- `autofill` - Password manager and autofill functionality tests
- `bookmarks` - Bookmark management tests
- `browsing` - General web browsing tests
- `custom_tabs` - Custom tabs functionality tests
- `ad_click_detection_flows` - Tests for ad click detection functionality
- `ads_preview_flows` - Tests for Android Design System (ADS) preview functionality
- `app_tp` - App Tracking Protection tests
- `autofill` - Password manager and autofill functionality tests
- `binary_upload` - Smoke test used to validate an uploaded build binary
- `bookmarks` - Bookmark management tests
- `browsing` - General web browsing tests
- `custom_tabs` - Custom tabs functionality tests
- `deeplink` - Deeplink / `duck` scheme navigation tests
- `duckplayer` - DuckPlayer tests. Some of these can only be run locally.
- `favorites` - Favorites management tests
- `favorites` - Favorites management tests
- `fire_button` - Fire button (data clearing) tests
- `input_screen` - Input Screen and Experimental Address Bar that provides Search and Duck.ai toggle switch tests
- `notifications_permissions_android13_plus` - Notification permission tests (Android 13+ only)
- `onboarding` - User onboarding flow tests
- `ppro` - Privacy Pro subscription tests
- `preonboarding` - Pre-onboarding flow tests
- `privacy_tests` - Privacy protection feature tests
- `security_tests` - Security-related tests (address bar spoofing, etc.)
- `sync` - Sync & Backup functionality tests
- `tabs` - Tab management tests
- `omnibar` - Omnibar tests, including the split omnibar layout
- `onboarding` - User onboarding and pre-onboarding flow tests
- `performance` - Page load benchmarks (cold and warm)
- `ppro` - Privacy Pro subscription tests
- `privacy_tests` - Privacy protection feature tests
- `privacy_tests_internal` - Privacy protection tests that require an `internal` build
- `security_tests` - Security-related tests (address bar spoofing, etc.)
- `serp` - Tests driven from the search results page
- `sync_flows` - Sync & Backup functionality tests
- `tabs` - Tab management tests
- `unified_input_screen` - Unified input bar tests, exercising the `nativeInputToggle` / `inputWithAiToggle` combinations across omnibar positions

## Shared flows
Inside `.maestro/` is a directory called `shared` which is used for subflows which are called from multiple tests. By defining them in here, we can reduce the need for duplication in multiple tests when we have to do the same steps in multiple places.
Expand Down
Loading