PMM-7 adjusted test pipelines

percona · Aug 17, 2023 · 307bbc1 · 307bbc1
1 parent ab4f2a7
commit 307bbc1
Showing 1 changed file with 26 additions and 13 deletions.
diff --git a/playwright-tests/README.md b/playwright-tests/README.md
@@ -37,35 +37,48 @@ this is it! tests are good to go on specified PMM server.
 
 ### Running tests:
 Execute command in the **playwright-tests** folder
-* **run all tests:** `npx playwright test`
-* **run desired "classes":** `npx playwright test `
-* **run desired groups/tags:** `npx playwright test --grep="${{ env.PMM_TEST_FLAG }}"`
+* run all tests: `npx playwright test`
+* run a single test file: `npx playwright test tests/todo-page.spec.ts`
+* run a set of test files: `npx playwright test tests/todo-page/ tests/landing-page/`
+* run files that have **my-spec** or **my-spec-2** in the file name: `npx playwright test my-spec my-spec-2`
+* run desired [groups/tags](https://playwright.dev/docs/test-annotations#tag-tests): `npx playwright test --grep @rbac`
 
 ### Test report
 Execute command in the **playwright-tests** folder: `npx playwright show-report`
 
 
 ## **Useful Command Line Arguments:**
+Full list of arguments available on [Playwright docs](https://playwright.dev/docs/test-cli#reference)  
+
 `--config="playwright.config.ts"` tells plyawright which configuration file to use to run tests. Useful when local run needs additional configuration, ex:
 
     `npx playwright test --config=local.config.ts`
 
-`--debug`  enables a more detailed output to the console, ex:
+`--debug`  Run tests with Playwright Inspector, ex:
 
-    `npx codeceptjs run-multiple parallel -c pr.codecept.js --debug`
+    `npx playwright test --debug`
 
-`--verbose`  enables the very detailed output information to the console, ex:
+`--pass-with-no-tests`  Allows the test suite to pass when no files are found.
 
-    `npx codeceptjs run-multiple parallel -c pr.codecept.js --verbose`
 
 `--grep="@tag"` runs only tests marked by specified tags. The following tags are available:
 
-    @inventory              Inventory functionality, removing nodes, services, etc.
-    @pmm-upgrade	        upgrade testing Scenarios to verify UI Upgrade for docker based PMM Server
-    @pre-upgrade	        upgrade testing Scenarios to verify Docker way Upgrade. Executed BEFORE the upgrade
-    @post-upgrade	        upgrade testing Scenarios to verify Docker way Upgrade. Executed AFTER the upgrade
-    @settings               PMM Settings functionality tests
-    @portal                 Integration tests between PMM and Percona Portal
+    @config                   PMM Settings functionality tests
+    @config-pre-upgrade       Config tests executed BEFORE the upgrade
+    @config-post-upgrade      Config tests executed AFTER the upgrade
+    @inventory                Inventory functionality, removing nodes, services, etc. 
+    @inventory-pre-upgrade    Inventory tests executed BEFORE the upgrade
+    @inventory-post-upgrade   Inventory tests executed AFTER the upgrade
+    @not-ui-pipeline          ???
+    @portal                   Integration tests between PMM and Percona Portal
+    @pre-pmm-portal-upgrade   tests executed BEFORE the upgrade
+    @post-pmm-portal-upgrade  tests executed AFTER the upgrade
+    @pmm-portal-upgrade       ???
+    @rbac                     User roles and access restrictions tests
+    @rbac-pre-upgrade         User roles tests executed BEFORE the upgrade
+    @rbac-post-upgrade        User rolestests executed AFTER the upgrade
+    @pmm-upgrade              Tests which actually perform the "UI Upgrade" of PMM Server
+
 
 
 ## Contributing