MQE-1672: AllureAdapter does not output BROKEN test steps

[KevinBKozan]

Description

• Fixed broken steps not showing up at all
• Fixed ActionGroup nesting issues when the test abruptly ends

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/verification tests (if applicable)
• All automated tests passed successfully (all builds on Travis CI are green)
• Changes to Framework doesn't have backward incompatible changes for tests or have related Pull Request with fixes to tests

[coveralls]

Coverage increased (+1.6%) to 56.119% when pulling 1b60a53 on MQE-1672 into 5c7bea5 on develop.

[coveralls]

Coverage remained the same at 56.119% when pulling 2f7ae70 on MQE-1672 into 95b1eec on develop.

[jilu1]

One comment, otherwise looks good.

[jilu1]

Is the BROKEN status accurate?

[KevinBKozan]

I think so, yes. Class Status only has mappings for FAILED BROKEN PASSED CANCELED PENDING, so I think it makes sense.

Also, refer to AllureCodeception.php ln 339, you'll see two functions testError() and testFail().

• testError() => hard error in test, like a fatal PHP error
• testFail() => exception thrown in the test cause a true failure (not an error)

Based on that delinitation and mapping to Codeception's existing hooks I think it makes sense for this to be Status::BROKEN

[jilu1]

That makes sense.

[jilu1]

Works as expected. Approve it.