Override step visibility of componentes per test

Currently, when i hide a step in a component, it is hidden everywhere the component is used.

The feature is generally helpful when trying to temporarily not use this step in a test, but ultimately it will be deleted or made available all the time upon completion, especially in scheduled test running often.

To modularize components it would be helpful to select the steps to run on a test per test basis.

E.g.: I have a component to click only some of a set of checkboxes, but in different tests it will be different checkboxes of the same set. With this approach i can build a component for this set of checkboxes with all checkboxes considered, but can select or deselect specific ones on each instance of a component.

In Real Life: i build a component to act with a GDPR layer and have to base my test on different selections of allowed services. With this approach i can build a "Handle GDPR Layer" component and everywhere i use it i can define the outcome of this and maintain the options available in a single component.

The workaround to make a component as template, unlink it after inserion and remove unwanted steps is just this, a workaround that harms the concept of reusable and maintainable components.

Relying on the already available UI, my suggestions would be, that when making a component and steps are hidden, these hidden steps are hidden by default on each new instance, but can then be activated or deactivated on a per test basis as described above.

Please authenticate to join the conversation.

Upvoters
Status

In Review

Board

πŸ’‘ Feature Request

Date

Over 2 years ago

Author

Sven Giesen

Subscribe to post

Get notified by email when there are changes.