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
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,11 +26,12 @@ Supported browsers aka hosts:
26
26
* Support for Allure Report
27
27
* Support for .xlsx files
28
28
* Support for Fake & Mock data
29
+
* Support for BrowserStack
29
30
## TEST RESULTS
30
-
* After each CI/CD cycle run, tests results will be automatically uploaded to [kamil_nowocin/allure_report](https://kamil-nowocin.github.io/Test_Automation-automationpractice/)
31
+
* After each CI/CD cycle run, tests results will be automatically uploaded to [kamil_nowocin/github.io/allure_report](https://kamil-nowocin.github.io/Test_Automation-automationpractice/)
31
32
* After each LOCAL cycle run, tests results will be stored in build/allure-report.
32
33
In terminal type `allure generate build/allure-report --clean` to generate local Allure Test Results
33
-
##LOGS
34
+
##TEST LOGS
34
35
There are two types of log information saved after each test run:
35
36
* Detailed logs in log directory. Warning! These logs will be deleted when you launch new test run.
36
37
* Colorful logs in testdata.xls file. Warning! These logs will be overwritten when you launch new test run. <sub><sup>(Only for TestNG runners)</sup></sub>
0 commit comments