Allure reporting with webdriverIO | installation & configuration | Part 1
Вставка
- Опубліковано 17 лис 2024
- #webdriverio_typescript_series #appium #typescript #automationtesting
#webautomation #mobiletesting #webdriverio
This video will explain on how to integrate Allure reporting with webdriverIO | installation & configuration | Part 1
Blog - qavalidation.c...
To setup appium, appium inspector, android and ios simulators, refer these following blog posts -
qavalidation.co...
qavalidation.c...
qavalidation.c...
qavalidation.c...
qavalidation.c...
qavalidation.c...
qavalidation.co...
qavalidation.co...
Full webdriverio playlist -
• WebdriverIO typescript...
Selenium java complete series -
bit.ly/qavbox-...
Subscribe to this channel -
bit.ly/youtube...
Blog posts -
qavalidation.com
Make me awake & feel fresh always, so I can bring lot's of interesting topics for you all, Buy me a coffee?
buymeacoffee.co...
Thank you for watching!
Thank you! This helped!
thanks man, it was very helpful!
I am getting this error , do you have any idea to fix this ?
ERROR @wdio/local-runner: Failed launching test session: TypeError: ReporterClass is not a constructor
need help in using wdio-video-reporter with allure typescript
Nice video!! Can we generate index.html file without opening it with any server also can we attach screenshot after every it block executed also with a condition of test case failed attach screenshot because of size of report may get increased in case of attaching screenshot for every test cases irrespective of failure.
Yes sure, we can do that, and i really like this feature of allure reporting, I will be uploading another session on this topic.
@@qavbox thank you very much. Eagerly waiting for part 2 video.
How can we share this report with others? Will we need to share this complete report with all json files? Is there any way where a person with whom we are sharing the report can view it even if he don't have allure installed ?
You can send the allure report and related files as zip over email or put it into a central location so someone can access.
But best way is to keep these reports as build artifact's of any cicd tools you use for your reference.