-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Automation of Tests that "check" is a good idea. Moving one step forward, when these checks fail is to raise a defect. A framework like TestNG allows you retries to confirm whether the check has failed. A lot of information such as
- A descriptive Bug title
- System info
- Browser info
- Steps to reproduce (A video recording). Vokoscreen on Linux Ubuntu Studio
- Logs All the above steps can be run using a Shell script, run from a Java program. This could be useful in Selenium Automation. Once the tests are run, the tester can just have one look at the failed tests before raising the issue. Hopefully this will save time.
AutomatedBugRaiser, aims to save a tester's valuable time by preparing the documentation (or most of it) before she raises a bug.
-
Since there are no steps to be written, a screencapture video will always show how a test was executed.
-
Upon looking at the video it is hoped that finding issues when a tester "defocuses" on 2nd or multiple views could also surface..hopefully.
-
Last but not the least it could be useful as proof of test execution.
The current script and Java program work on Ubuntu Studio 16.10, Java 1.8, xdotool
Right now we are able to address point 2, 3, and 4 from the Question (What is AutomatedBugRaiser?). Moving on, we would like to use it as follows
a. In a Selenium WebDriver test
b. Collect logs of a specific app under test