You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7Lines changed: 7 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -486,6 +486,9 @@ cim-compliance-report
486
486
**Description**
487
487
488
488
- This stage does the setup for executing UI tests and reports the results
489
+
- It is possible to parallelize UI tests execution by using pytest markers.
490
+
To do so, one must specify `ui_marker` parameter in buid-test-release.yml as in [example](https://github.com/splunk/splunk-add-on-for-amazon-web-services/blob/925fd189737507dd91cc5275c59a8b390550411c/.github/workflows/build-test-release.yml#L35).
491
+
Markers must be created prior and each test case must be marked (check [run-modinput-tests](#run-modinput-tests), and this [PR](https://github.com/splunk/splunk-add-on-for-amazon-web-services/pull/1237))
489
492
490
493
**Action used:**
491
494
- No action used
@@ -525,6 +528,10 @@ Junit XML file
525
528
**Description**
526
529
527
530
- This stage does the setup for executing Modinput tests and reports the results
531
+
- It is possible to parallelize Modinput tests execution by using pytest markers.
532
+
To do so, one must specify `marker` parameter in buid-test-release.yml as in [example](https://github.com/splunk/splunk-add-on-for-amazon-web-services/blob/603f37ee24565f23104c0297e55a0c72480f34c9/.github/workflows/build-test-release.yml#L33).
533
+
Markers must be created prior and each test case must be marked (check the following references: [ref1](https://github.com/splunk/splunk-add-on-for-amazon-web-services/blob/main/tests/modinput_functional/README-test.md),
0 commit comments