Home

Welcome to the AutomatedBugRaiser wiki!

What is AutomatedBugRaiser?

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:

1. A descriptive Bug title
2. System info
3. Browser info
4. Steps to reproduce (A video recording). Vokoscreen on Linux Ubuntu Studio
5. Logs

can be obtained using a Shell script, run from a Java program. One example of this 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.

What problem does this solve?

AutomatedBugRaiser, aims to save a tester's valuable time by preparing the documentation (or most of it) before she raises a bug.

1. Since there are no steps to be written, a screencapture video will always show how a test was executed.

2. Upon looking at the video it is hoped that finding issues when a tester "defocuses" on 2nd or multiple views could also surface..hopefully.

3. Last but not the least it could be useful as proof of test execution.

What environment does the current script work?

The current script and Java program work on Ubuntu Studio 16.10, Java 1.8, xdotool

How do I use this?

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.

What is the status of the project?

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