Support nested composite steps

Description

Having @Composite steps calling other @Composite steps does not seem to work at all:

In the given scenario neither the substeps will be resolved nor called. So Then second top button is enabled will not be marked as pending and Then first top button is enabled won't fail.

That's not nice as it might break your steps if you do some refactorings to them. Composite-calls should not need know if they again resolve to Composite steps.

Assignee

Mauro Talevi

Reporter

Mark Michaelis

Labels

None

Components

Fix versions

Affects versions

Priority

Major
Configure