Define steps manually

I’m submitting a …

• bug report
• feature request
• support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

Having code like this

@Test
@Step("TRegister")
public void test()
{
    step("Goto homepage");
    //code

    step("Assure not logged in status");
    //code

    ...
}

@Step("\"{stepName}\" step")
public void step(String stepName)
{
}

This yields in a report that looks like that:

What is the expected behavior?

But I want to have it to look like that: https://ci.qameta.io/job/allure2/job/master/Demo_Report/index.html#suites/fd187460706bbe14b8a84cc98c3fb991/1063eec919e2a469/

The icons indicate a passed/fail behaviour and timing seem to be correct.

What is the motivation / use case for changing the behavior?

If I would split my test case in many functions and annotate them correctly I would get that but the test case wouldn’t be readable anymore. I work on top of an high level api that reduces the code needed for testing to a few lines. So I would have to wrap (in average) less then 3 lines in a function. So it would be nice to define step during runtime so we could achieve the same behaviour as if it would be in annotatd functions.

Please tell us about your environment:

Allure version	2.4.1
Test framework	JUnit@4.12
Allure adaptor	allure-junit@2.0-BETA19
Generate report using	allure-maven@2.9

[baev]

you can use AllureLifecycle:

    public interface StepBody {
        void execute() throws Exception;
    }
    
    ...
    public static void step(final String name, final StepBody body)
        final String uuid = UUID.randomUUID().toString();
        final StepResult result = new StepResult()
                .withName(name);
        getLifecycle().startStep(uuid, result);
        try {
            body.execute();
            getLifecycle().updateStep(uuid, s -> s.withStatus(Status.PASSED));
        } catch (Exception e) {
            getLifecycle().updateStep(uuid, s -> s
                    .withStatus(getStatus(e).orElse(Status.BROKEN))
                    .withStatusDetails(getStatusDetails(e).orElse(null)));
            throw e;
        } finally {
            getLifecycle().stopStep(uuid);
        }
    }

[baranoff-ivan]

With Java 8 you could do something like that:

@Test
@Step("TRegister")
public void test()
{
    step("Goto homepage", () -> {
        //code
    });


    step("Assure not logged in status", () -> {
        //code
    });

    ...
}

@Step("\"{stepName}\" step")
public void step(String stepName, Runnable actions) {
   actions.run();
}

And that is your variant of implementation? How do you suppose to wrap actions in step mannually? Like below?

@Test
@Step("TRegister")
public void test()
{
    startStep("Goto homepage");
        //code
    stopStep("Goto homepage");

    startStep("Assure not logged in status");
        //code
    stopStep("Assure not logged in status");

    ...
}