Pending Review
Last Updated: 26 Dec 2018 07:59 by ADMIN
Created on: 20 Dec 2018 18:31
Type: Feature Request
Custom developed step builder steps

I'd like the ability to create my own Step Builder steps.

This way, the QA team could use my custom built steps to achieve common task without our web based product.



In our product, we need the ability to search a table for specific cells and retrieve image input buttons on that cell row. Of course we can easily achieve this by doing a coded step. However, this is a very common task for us and if my QA team could just select a custom built step builder step that has its own specific parameters (TableID, CellText, ImageInputAltText, etc), then I would remove one area of them having to get into code behind to achieve their task. The QA, while able to do some development, its not their core competency, so I would like to minimize their exposure.


Possible Reasons my company would need such:

* Often times we need to count the number of times a cell with a certain word in it exist in a table.

* We have a common set of steps that always needs to occur together (enter in text, click search, find in table, click that link [the start of every process in our product])

* Find a row within a table that has two matching text cells.

1 comment
Daniel Djambov
Posted on: 26 Dec 2018 07:59

Thank you for your feedback, we appreciate the detailed information you provided in order to better understand your case.

I have added this feature request to our product management pipeline and it will be taken into consideration in our release planning.

In the mean time, can I offer you an approach that for me it sounds could help you achieve what you want. What I mean is using our Test As Step functionality in Test Studio with InheritParentData option. I'm not sure if you are familiar with it and already considered such implementation, but in case you didn't, here are more details how it works.

For example, you can create in your project a test, that is used as a common test by other tests and performs several operations specific for your application. In this common test you can write the code or add the steps necessary to handle the operations and data bind it in a way, that depending on which parent test calls it, child test will use different data during execution. Both parent and common child tests should have single row of data with same Data columns, child test should have InheritParentData option set to true, so when called from Parent test with Data Column named TableID for example = 11, child test will execute its steps and code with that data. If common child test is called from another parent test that has TableID data = 12 it will use this data, etc. The common child test will execute the same steps and operations, but with different data, based on from which test it is being called from.

This approach should be a little more powerful, from a single common custom step IMO, because it can use more steps in it, and still the code (if needed) in it will be stored and supported in a single test, so only one person can support it and others can only use it by calling it and changing the data values of their tests, without the need to write logic or code.

Please let me know if I was able to explain well this approach and if you think it can work for you also. 

If you have more questions or need additional details how this could be implemented, please let me know.

Thank you once again for your feedback and cooperation,

Best Regards,
Daniel Djambov
Progress Telerik
The New Release of Telerik Test Studio Is Here! Download, install,
and send us your feedback!