Why refactoring?
Testing at the speed and scale of Agile requires automation and maintainable test design. And one root of the maintenance problems is copy/paste.
That’s the reason why CucumberStudio enables test refactoring. Tests should be reviewed and refactored continuously, just like code. This section describes the main refactoring principles.
Promote
When you have a group of steps you want to reuse across multiple scenarios, extract them into an action word. This refactoring technique makes your steps reusable and easy to maintain. Don’t repeat yourself!
-
First select the group of steps and select Convert into action word:
Click the image to enlarge it.
-
If several scenarios already use this group of steps, then select the ones you want to apply the refactoring to:
Click the image to enlarge it.
-
You are done. The action word has been created with the group of steps and the scenarios you have selected now call the new action word directly.
Click the image to enlarge it.
Inline
Inline is the opposite of promote. It replaces an action word by its steps in every object where this action word is called.
-
Select your action word and click on Inline:
Click the image to enlarge it.
-
Review all the objects (scenarios and action words) calling the action word to be inlined:
Click the image to enlarge it.
-
All the references to this action word have been replaced by the steps of the action word.
Click the image to enlarge it.
Rename
Make sure that action word naming is meaningful because it keeps test readability and do not hesitate to rename an action word: all the references (call) to this action word are updated automatically.
Click the image to enlarge it.