Large enterprise automation demands to keep the execution time as low as possible. For example consider this scenario
Make a new transaction for a new user and the admin need to validate the transaction and take action (approve / reject). two scenarios are
Create User1 > Login User1 > Make a transaction1 > Logout(User1) > Admin Login > Validate Transaction> Approve transaction1 ::Execution Time (8min)
Create User2 > Login User2 > Make a transaction2 > Logout(User2) > Admin Login > Validate Transaction> Reject transaction2 ::Execution Time (8min)
To reduce the transaction time we can combine the above two different scenarios and make into one.
Create User1 > Login User1 > Make two transaction (1&2) > Logout (User1) > Admin > Login > Validate Transaction1> Approve transaction1 > Validate Transaction2> Reject transaction2 ::Execution Time (12 min)
If the business logic allows such transactions as described, it’s always better to combine the similar patterns. So that the test execution time can be dramatically decreased.
In the above example I had saved 4 min / Test Case.
Credit: http://fasteningcode.com/index.php/2017/09/20/automation-flow/
Leave a comment