I think this is a great use case for ARD. You have either a complete new UI screen or new fields that need validation. In that case, there is definitely expected behavior for that new UI screen and those new fields. At the very minimum, you would want to model the happy path, where all fields are filled in properly and the flow successfully completes whatever it is meant to do.
You would also want to validate negative test cases - what happens when I put bad or inappropriate or empty data in my new field? For example, what happens if I put non-numeric characters in a telephone field? And lastly, you might consider modelling business logic, for example, out zip code field may accept both US and international postal codes values.
Lastly, it doesnt matter that it is for a mainframe, the test execution may be different and their maybe some considerations specific to mainframe, but the actual test cases required will largely be the same.
Thanks,
Mimi
------------------------------
Client Services Consultant
Broadcom
------------------------------
Original Message:
Sent: 05-26-2020 07:43 PM
From: Luis Ledezma
Subject: New fields validation
Hello All,
We are currently working with a financial institution and some of the user stories are about new mainframe like screens creation with several fields on them.
Is there a way to model this type of validations where the User Story is just asking to have the new screen with certain fields on it? Or is it not recommended to use ARD for this type of testing?