-
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 bug. A lot of information such as:
- A descriptive Bug title
- System info
- Browser info
- Steps to reproduce (A video recording). Byzanz on Linux Ubuntu Studio
- Logs
which are needed to raise a bug can be obtained using a shell script, run from a Java program (Please see BugRaiserHighLevel - this is just descriptive) . One example of this is that it could be useful in Selenium Webdriver Automation. Once the tests are run, the tester can just have one look at the failed tests before raising the issue. Imagine a situation when there are several failed tests over several failed test cycles, such an approach could hopefully 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 20, Java 1.8
You can just use the Java code and script file in your tests. Some automated tests are written in Java. You could add or remove any system calls depending on what kind of information you want while your test is running. I have also included a TestNG class BugRaiserSource, which contains an actual site and an actual path where I store my testfile
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 - Done (Please see BugRaiserSource)
b.
System requirements: Linux 64 bit Ubuntu 20 Java 1.8 recordmydesktop Selenium 3.5.3 GeckoDriver 0.16 Firefox 54