Рет қаралды 190
Million dollar worth of man hour effort in testing is preparation of test data. Why so
Applications are full of user flows and scenarios. Every flow is a user journey where the user (application) moves through multiple states to achieve an outcome. This outcome is a successful transaction
Imagine you wake up tomorrow as the test engineer at Paytm. Wallet transactions are core to your business. Users add and transfer money.
How do you, as the test engineer, ensure PayTM never fails on this?
You will try to test this core logic, possibly this way
Step 1 Login with an User i.e. you create a valid user
Step 2 User adds Rs 100 to wallet i.e. You add dummy amount in user walltet
Step 3 User makes Rs 50 txn i.e. You make user remove dummy amount
Step 4 Check wallet balance as Rs 50 i.e. You check db for account balance
This four-step flow needs the user (application) to move from steps 1 to 3 as conditional states, i.e. you, the test engineer, load and reload the application in these exact states to complete a transaction.
But more complex end-to-end flows need more complex data preparation.
That is the million-dollar effort test engineers put in to test all critical flows end-to-end.
In this webinar, you will find a way to avoid test preparation completely.