We are continuing on our path to show you how to test a digital banking app with a digital twin test automation approach.
In the previous post we put together our user journey map in a less than 30 minutes. 10 minutes to draw the 9 step “activity diagram” and 20 minutes to define the top 20 user journeys we wanted to focus our test automation on to get started.
The first snippet of code we need is for the dbankSite step in our activity map. This will inform our web browser that we want to navigate to the digital bank site under test.
You can also see that we have set the window size, so when we run Vitaq AI, it will place our browser neatly next to the Vitaq screen. Very simple and straightforward.
Intelligent Test Data for your Digital Twin
Now to tackle the login step. For this we will need some test data. A username and a password right? But what if you want to test for multiple usernames and passwords? You don’t want to keep editing the test code, so let’s use the intelligence of Vitaq to help us here.
Using the requestData Vitaq method, we can pull-in many different usernames and passwords. We can even have the data items selected using the machine learning AI algorithms in the Test Automation tool. All we need to do is define them as Test Activity variables in the activity diagram.
We can have very long lists of different usernames and passwords. Want to use real test data from your banking App database? You can call this too. Each time you run Vitaq AI it will select different test data, guided by the AI and the goals you set.
Test Activity variables can be ranges of values, lists of names, files, database access keys. Vitaq AI can auto-generate whatever test data you need.
In the next post we’ll take a look at how we can dynamically change our activity map as the test automation is running. We can enable or disable test actions (steps) dependent on the intelligent data that get’s generated or what happens in our app under test.