Best Practices for creating and using step groups

What kinds of things should be in a step group?

Cut out "steps that are used over and over again" or "parts that are common to multiple scenarios" and put them in a step group. This will allow you to create and manage scenarios more smoothly and efficiently.

For an overview of step groups and their basic usage, please refer to this help page.

Points to keep in mind when creating and editing step groups

• Keep step groups as short and concise as possible.
• Use an easy-to-understand naming convention for step group names. Also, be sure to include labels and explanations so that everyone can visualize what is being done.
• Avoid creating step groups ahead of time that may or may not be reused. Create a step group when you are sure it will be reused and when you need it.

Use Cases

• Find steps that will be used repeatedly in the test, such as login/register/exit, and group them into step groups. Also, if users have different privileges, you can create and manage scenarios more efficiently by creating separate login step groups for each privilege (e.g., General Member/Premier Member, etc.).

• For example, step groups are effective for steps such as entering data into a form. By grouping together steps that are used repeatedly in multiple scenarios, such as membership information entry and data registration, scenario creation can be made more efficient.
  

• By making the creation/deletion of data necessary for testing also a step group, the test can be prepared by simply adding step groups at the beginning and end of the scenario. For example, you could use a step group to create a user at the beginning of the scenario, and then use a step group to delete that user when the test is finished.
  In this way, it is also possible to prepare multiple scenarios by using [step group for data registration] + [verification perspective] + [step group for data deletion] to cut out the parts that can be shared among the step groups.
  

• As an advanced use case, it is also possible to pass values between step groups. It is possible to use a JS step within a step group to obtain a value, and then use that obtained value within another step group.
  

• For testing abnormal systems such as errors, there are cases where scenarios can be created that take into account "cases where elements are not displayed correctly" by combining screen reloads in the wait step and JS step.