“Production verification” is a part of the Verification and validation procedures that are an integral part of Software quality.
In our view, our verification services are the last link in the Quality assurance most FI’s have in place.
Whereas hard and software elements have been verified in lower environments during the first 3 steps op the OTAP, it is still a very (very!) good idea to validate the process once in production.
It all starts with the embedding of our services. We become a customer of your FI (Bank) and open accounts and add those to our “money pool”. | |
Setup as your client, we can start using your infrastructure. Usually, we start with a basic transfer, but in fact we can do any type of product. We can embed happy flows where we can follow the complete end to end flow or a unhappy flow". The flows follow [the customer journey](#The customer journey) and either succeed or fail. Each verification can be executed on any platform or device. Verifications can be made to execute fully automated. These automated flows can be executed by us, or by your own changeteams after rollout | |
The fully automated verifications can be scheduled tun run at any given time, in any interval. With this schedule, you will get insight into how verifications run 24x7 | |
last but not least, we can detect if errors occur during the execution of these scheduled verifications. These alerts can be sent via any means to you, or support teams. There are even complex escalation schemes. |
The customer journey is the steps (sometimes also called click-paths) that an actual user performs to initiate a certain product.
as an example of a customer journey, lets look at this website example. in this example every number stands for functional step. On a more detailed view, even every number could have actual more steps a user needs to perform. For a more detailed overview we have written down some the actual script steps. |
Step | Substep | Action |
---|---|---|
1 | 1 | start browser |
2 | navigate to an URL | |
3 | Check if the website contains a certain text and a login button | |
2 | 1 | Click the login button |
2 | Fill in a UserID | |
3 | Fill an OTP from a mobile app (From another script) | |
4 | Click the validate button | |
5 | Check the login result message |
As you can see, there are lots of sub-steps that make up a ‘simple step’.
On our solution, we can set OK and NOK criteria for every step. from a journey perspective we like the all or nothing approach.