Eggplant AI Testing vs Vitaq AI

Eggplant AI Testing vs Vitaq AI

Comparison to Eggplant AI testing

So you like the look of Eggplant AI testing and its new incarnation DAI. Well Vitaq existed way before Eggplant AI.  It wasn’t built with $50m of Private Equity funding, so you don’t have to help pay back $330m by paying huge fees to use a tool with the same capabilities. We developed Vitaq AI with our own money and a small team of dedicated developers. So you can access all of the same powerful benefits at a fraction of the cost. We also don’t force you to use an arcane proprietary scripting language. Vitaq has full support for JavaScript, Python and NoCode Scriptworks. All working on top of the open and most pupular test frameworks such as Selenium and Appium. 

Just like Eggplant AI, Vitaq AI provides users with an easy way to model your test space by creating a visual test activity diagram. We’ll show you how simple this process by modeling the complete list of Test Requirements for our e-commerce AutomationPractice.com (https://vitaq.io/2020/11/01/selenium-automation-practice-site/).  We previously previously showed you how to use Jira to divide them in the most modular way. So let’s start performing Vitaq AI Test Automation to achieve the required 100% QA coverage results.

AI test planning in Jira

Let’s find out how we can take modular sections of requirements out of our Jira list to map to our VitaqAI Test Automation Tool:-

1) Below you will see our list of high level test requirements documented into Jira.

how to map requirements to test cases in jira

 

Diagrams like Eggplant AI Testing

2)  Open the Vitaq AI Test Automation Tool and just like the Eggplant AI approach you add the common test actions. These are the actions needed to achieve the user journeys described in Jira. Such as testing the sign-in of already registered users and new registration of a user. All the way through to checking their account details including wishlists, credit slips and the like to signing out. In addition to this add the new letter registration and contact us test action to increase the test space coverage.

We have simply divided this section of our test space into a single test activity diagram. All done by connecting each common test action to the next action it is ‘allowed’ to go to in the e-commerce AutomationPractice.com application. Resulting in single test activity diagram comprised of common test actions needed to meet the Jira test requirements.  The model for registration and user account test space is shown below:-

Model based testing

3) Now to capture the user-journey requirements defined in Jira:. Click on the Sequences tab besides Test Action Scripts tab.

Sequences

What is Sequences tab in Vitaq-AI Test Automation Tool?

Sequences:- Sequences in VitaqAI are referred to as user- journeys where we define the traversal path of the test run.

User Journeys

4) To Create Your User Journey Coverage Under Sequences Tab. Click on + Button

5) Enter the Sequence Name VTB_10. Keep the Add Sequence window open till you select your user journey by selecting respective test actions as required for your test run.

user journey

In the Above Screenshot, you can see numbering is taking place. On each test action in the sequence while selecting each and every test action in turn. This provides the user with an easy to visualise specification of our user journey goals for testing.

6) Click on Ok Button of Add Sequence Dialog Box. and we will see that VTB_10 has been added under the Sequences Tab.

These user-journey coverage goals are used by Vitaq AI’s machine learning algorithms.  They focus the automated-test scenarios generated to create the optimal set of tests to achieve 100% QA coverage.

To capture all of the test space defined in our Jira requirements we only needed to complete four Vitaq Diagrams. The Test Activity diagrams grouped the common test actions needed to execute user-journeys for particular types of test scenarios. Such as user registration or product purchase and check-out. The four different test activities are shown below:-

Test Activity Diagram one

Model 1

Activity Diagram Two

Model 2

Diagram Three

Test Activity Diagram Four

Model 4

Divide and Conquer

Why have four Test Activity Diagrams been created, why not just one?

By creating four Test Activity Diagrams we have divided and conquered the test space into four easy to visualise and hence debug user journey coverage groups. This is a more productive way of working with Vitaq AI Test Automation.

Rather than creating one big Test Activity Diagram which would be harder to debug. Having four diagrams instead of one also increases the opportunity of deploying more dynamic variability in the automated tests. Vitaq AI will create many variable tests to meet the user-journey coverage goals, so there are more chances of finding bugs.