Testing a digital bank with a digital twin

The approach of developing a digital twin has delivered major productivity improvements for industrial digitalisation over the last decade. The results are clear to see in high performance motor sport. To achieve high precision design and test automation, every facet of a racing cars’ product life cycle is modeled.

But how does the “digital twin” term apply to web and mobile app test automation you might ask yourself? Well we could blame Humpty Dumpty in Alice’s Adventures Through The Looking Glass who famously said “When I use a word, it means whatever I want it to mean”. 

There are three important parts of a digital twin:

  1. A model
  2. Evolving set of data related to the model
  3. A means of updating and adjusting the model 

Oh no, do I hear you saying! Not model based testing again. Have you been burnt by the promises of model based testing? You know the common three pain points:

  1. Modeling is too hard
  2. Models do not scale to the complexity of the problem in hand
  3. Generated tests miss bugs

When we introduce you to Vitaq AI, you will see that modeling is easy. Generating the tests that you normally think about and also the ones that quite often get missed. Using artificial intelligence helps you with the heavy lifting to scale with increased complexity. We even tie in your test data and use QA coverage to intelligently guide you.

To help you stand on the shoulders of your digital twin giant, Vitaq facilitates model updates and adjustments.

Digital bank demo

The best way to show you how all this fits together is by way of a worked example in Vitaq AI. So over a series of blog posts we will walk through how we created a digital twin for this digital bank app . We will then deploy AI-driven test automation to achieve coverage of all of the user journeys we need to test.

digital twin

 

To work out what we need to do to test our digital bank, we would first take a look at our user story map. Are yours still written on post-it notes and stuck on a whiteboard in the office? How’s that working out for you during lockdown? When you stand back and take a look at the top two rows of your map you will clearly see the relationship between user journeys (the famous Jeff Patton called these user activities) , steps and stories. Each user journey contains a set of steps that you must complete to reach your end goal.

Steps into actions to create your digital twin

They say life is a journey, not a destination but let’s be clear we all end being a long time dead. So it’s better to get started with automating something than trying to boil a test ocean manually. Pick the key “steps” needed to complete your user journeys, open Vitaq in your web browser and place them as Test Actions in the Vitaq AI Test Activity diagram window.

For the digital bank app we need steps that will navigate to the site, login, create accounts, deposit, withdraw and transfer. At each “step” you need to think about what are the “allowable next steps” for a user in the digital bank app. Then you can draw your connections in Vitaq from Test Action (step) to Test Action (step) as shown below.

Digital Twin

The light blue Test Actions (steps) of home, transfer and logout are “global” actions. Perfect when you have a step that you can take from any place in your app such as logout or home.  Rather than drawing connections to all action, you just create a global.

Follow through from the green start circle and think about your user journeys. Getting brain ache? That’s why we created the ability in Vitaq AI for you to quickly define your user journeys as a series of steps (actions) that we call sequences. Click on add sequence, name your journey, then click on the actions in the diagram to complete that journey.

digital twin

User Journey coverage

Want to know whether this Test Activity (Journey) map can “cover” all of your required user journeys? Well, we thought of that too. Even before we connect our digital twin to the digital bank app under test, we can run AI-driven Vitaq to automatically “step” through the “activity diagram” (map) to work out if we can achieve 100% coverage of our defined sequences (journeys).

User Journey Coverage

Digital twin: take a look under the hood in the next blog post

In the next post we’ll show you how to create the Test Automation code for each of the actions (steps) in the diagram (map). These are very short “snippets” of JavaScript code that drive the open source Selenium tool that connects to your browser. All written in industry standard Page Object Pattern (model) style. 

Leave a Reply