Creating First Test Project in Svatah

Svatah — Behavior Driven Code-less Automation

What is Svatah? Svatah is self automated test platform which with one time minimal input starts taking care of all your applications functional validation needs. With Svatah we can automate our entire regression stack in matter of days. This lets our developers focus more on development.

Svatah combines user behavior models with machine learning capabilities to create next generation of code-less test automation solution for web, APIs and mobile platforms. Thus, in future enterprises can utilize their domain experts to easily and rapidly automate their user stories which in turn will help them ship their product faster without compromising on quality.

Credits : Svatah ADE — Atul Sharma

1. Onboarding: (Svatah Cloud): Launch www.savtah.in and Register & Login to the Svatah Cloud portal.

Launch Svatah Cloud

Register & Login to the Svatah Cloud

2. Creating First Project: Navigate to ADD NEW from SVATAH menu.

ADD NEW PROJECT

2.1 Creating Project Config: The configuration details needed are vivid enough to define. We need to define the Project Name, Base URL, Browser Selection and Resolution, Screenshot capture at each step or only at test failure and parallel executors

SVATAH — PROJECT CONFIGURATION

This configuration will look like —

SVATAH — PROJECT CONFIGURATION

2.2 Creating Data Repository: Here you can keep your test data abstracted from the tests. Tests are user flows in context with Svatah. This looks like key, value pairs. Here in below example Starting Point is ‘Bangkok’ can be easily changed to say ‘New York’ and it will not require any change to be made in user flows. User flow only uses only keys. [StartingPoint: <CityName>]

SVATAH — DATA REPOSITORY

2.3 Creating Locators Repository: This is the central locator repository to keep and manage all locators for out User Journeys (E2E Flows). This looks like this and you can add the locators you need for your user flows. Sample example is shown below:

For More Details : https://www.svatah.in/docs#/locatorReference

SVATAH — LOCATORS REPOSITORY

SVATAH — LOCATORS REPOSITORY

2.4 Creating First User Flow: Below is how the User Journey Flow looks. We need to define the flow name and define the flow steps.

SVATAH — USER JOURNEYS

Few Svatah Keywords to know

Story — A typical story consist of multiple steps definitions which would be executed sequentially. A story is similar to a scenario where it is a logically modular grouping of steps which makes up a business functionality but a story in itself is not executable. A story must have unique name across the project as a story can be reused by another flow. A typical story looks like:

story : I want to login
+type+ the username *$usernamem* in field ~username~
+type+ the password *$password* in ~password~
+click+ on the login button using ~submitLoginButton~

story : I want to go to schedule build page
+click+ on the Schedule Build using ~scheduleBuildLink~
+validateText+ on the Schedule Build Page using ~buildPageText~ with *$ExpectedScheduleText*

Compose — Once you have created your stories for the project you can bind them together using compositions. A composition is grouping to sequential stories which tells us about the specific part of the user journey. This would look like:

compose : I want to verify text on schedule page
I want to login
I want to go to schedule build page

Test — nest a composition or a scenario as a step on another composition. Only condition is that all of these steps must follow a logical execution order. Once you are done you can execute this composition as :

test : I want to verify text on schedule page

First Flow — This is being carried over phptravels.net. We have 3 Story defined and composed. Also to test this entire stiched composition an E2E User Journey a test is created.

For more Actions and Action Dictionary Refer — https://www.svatah.in/docs#/reference & https://www.svatah.in/docs#/actionDictionary

SVATAH — USER JOURNEYS

SVATAH — USER JOURNEYS

SVATAH — USER JOURNEYS

2.5 First Project Creation: Once we follow above steps and complete, a project is created. This is how project looks:

SVATAH — PROJECT CREATION

2.6 Project Execution: Once you execute the project. You will get the report in below format mentioning Execution Start and End time, Browser used and Test Pass/Fail/ Skip.

We can Schedule the build if we need to run this periodically.

2.7 Results Dashboard: The detailed test execution report dashboard has multiple elements. Few important result metrics are shown below:

Current Build Summary —Provides visualization for Pass / Fail , Skip if any

Build Comparison — Provides the same metrics for last 5 builds

Overall Summary View: This shows story wise breakdown and steps wise pass/fail and skip view with link to view scheenshot of steps as per configuration.

Details Results View: User Journeys with Scheenshot mapped with steps Screenshot were set as in config to capture for each screens, so we see the screenshot for entire user journey and each element interacted by the codeless scripts are highlighted with a caption with action being performed as a plain narrative english.

Now you are ready to start creating your own flows using Svatah.