All About the Apps
cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Automation Testing: Why are we making it so complex? Part 2: all modules big and small

BrianPalagyi

Thanks for the comment and for reading!

 

I see where you are going, but if you think about it, when you have a single module that ‘just’ clicks exit?  You would more than likely have additional steps (exit and clean up, exit and reset to home page, exit and review check out … ), at least I feel that you would.  Then we see the problem with allowing modules to have single steps is it’s a slippery slope to then have a module for any ‘OK’ button or a module for ‘NAME’ field, because these are repeatable steps and become single clicks or actions.  Once you allow these, then you are starting to build a module for every object in your Shared Object Repository, which isn’t what you want either. It’s like building with LEGO building blocks, you can use the very small ones to (the ones that are the 1x1’s) to build a building, but it will be BEYOND tedious and the benefits of larger blocks are not being leveraged.  You want these modules to have enough meat on them to make the useful.  There are exceptions to any rule, but I would be VERY careful in allowing them and make sure you have fully investigated the whole of the testing scenario before proceeding.

0 Kudos
About the Author

BrianPalagyi

I have more than 12 years in IT, with focus on Application Lifecycle and Delivery Management. Lately my focus has been in looking at the concepts of SAFe and DevOps transformations within organizations.

Comments
vaishnavi_alm

I am currently implementing business process testing for my customer and the timing is right for me to have landed at this article. Very well put. Thanks for sharing the best practices.

 

I would like to differ on one point, though. "Never have a module that is only one execution line long". I think it sometimes helps. A simple scenario that comes to mind, is this: When a website changes a one-click Exit process to a two-step process. Earlier the users could click on one button - "Exit" to exit a page. Now, they are presented with a message that reads "This will navigate you away from the page" and two buttons: Ok and Cancel. If the business flow involves multiple calls to Exit process, wouldn't it help if this was modularized?

 

BrianPalagyi

Thanks for the comment and for reading!

 

I see where you are going, but if you think about it, when you have a single module that ‘just’ clicks exit?  You would more than likely have additional steps (exit and clean up, exit and reset to home page, exit and review check out … ), at least I feel that you would.  Then we see the problem with allowing modules to have single steps is it’s a slippery slope to then have a module for any ‘OK’ button or a module for ‘NAME’ field, because these are repeatable steps and become single clicks or actions.  Once you allow these, then you are starting to build a module for every object in your Shared Object Repository, which isn’t what you want either. It’s like building with LEGO building blocks, you can use the very small ones to (the ones that are the 1x1’s) to build a building, but it will be BEYOND tedious and the benefits of larger blocks are not being leveraged.  You want these modules to have enough meat on them to make the useful.  There are exceptions to any rule, but I would be VERY careful in allowing them and make sure you have fully investigated the whole of the testing scenario before proceeding.

Events
June 6 - 8, 2017
Las Vegas, Nevada
Discover 2017 Las Vegas
Join us for HPE Discover 2017 in Las Vegas. The event will be held at the Venetian | Palazzo from June 6-8, 2017.
Read more
Each Month in 2017
Online
Software Expert Days - 2017
Join us online to talk directly with our Software experts during online Expert Days. Find information here about past, current, and upcoming Expert Da...
Read more
View all