How to overcome with some CBTA challenges?

[former_member410343]

Hello guys, I have automated many test compositions using CBTA, but I am facing some challenges to reuse some transactions, for example: there are transactions that were recorded in 2016 and now in 2017 they bring many new warning messages, making the adaption of the script time consuming, what is the best way to make a recording time proof in CBTA?

Greetings,

Paul

[Former Member · Accepted solution]

Hi Paul.

You have to consider if it would be quicker or cheaper to record script from the scratch or to update it. For example if there are new warning messages and they do not require an action, resolution might be to simply avoid it. But if process flow is somehow changed and script is no longer working, you need to update it. For this purpose I use some dummy test configuration which I set up as my original script. then I will start CBTA recorder and stop recording. Then I go to the exact point when an update is needed and start recording again. After performing required actions I again stop recording and finish the script. After that my dummy test configuration contains only new components and I copy them to right place in my original script.

I also saw similar approach with new CBTA SP7 where you do not need to create some dummy test configuration, but I have not checked it yet.

But in the end you can always use object spy and add adtitional components by hand.

Hope it helps.

Bye

[sabatale · Accepted solution]

I think you are talking about the Execute to Step feature. Available with Solution Manager 7.2.

[sabatale]

Automation testing is, by design, vulnerable to changes. Jan is right about re-recording. If you think it is too costly to recreate the scripts from scratch, then you should focus your efforts on automating only processes that are are extremely repetitive, short, or very well-known by your team.

Some guidelines to help you repair scripts:

1. Existing fields become mandatory: use Screen components and expose the mandatory parameter
2. New fields are introduced: Recreate the screens using CBTA Inspection feature, and expose the parameters for the new field
3. Existing fields become non-mandatory: Unexpose the mandatory parameter
4. Fields are removed completely: Recreate the screens using CBTA Inspection feature
5. Several new screens are introduced: Use the "Execute to Step" feature, then record additional screens and insert them where they belong

Please confirm the answer if it helps (this way, it helps others).