Nested Steps

[janschaefer]

The idea of steps is the following. Often you want to hide certain details of a step, because they are not directly important for a certain scenario. For example:

when().I_fill_out_the_registration_form_with_valid_values();

will fill out the registration form with valid values, but the concrete values are not shown. If a developer is interested in the concrete values she can look into the implementation of the step. However, in the report these details are completely gone. Thus, if someone reads the report and he wants to know the values, he has to ask a developer.

Nested Steps

Nested steps are steps that happen within another step. For example, the above step could be defined as follows:

public SELF I_fill_out_the_registration_form_with_valid_values() {
    return I_enter_as_name("Franky")
        .and().I_enter_as_email_address("[email protected]")
        .and().I_enter_as_password("password1234")
        .and().I_enter_as_repeated_password("password1234");
}

The idea is now that in the generated report these sub-steps can be made visible somehow. For example by expanding the parent step. That way, the original scenario stays small, but the details can still be looked up.

Annotation

Nested steps should get an additional annotation @NestedSteps to indicate that the step contains sub-steps.

[janschaefer]

Thank you for starting this long-wished feature :-). On a first glance it looks pretty good. I will give you more feedback as soon as possible.