You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Status of a failing test is marked as broken by this adapter in the xmls under allure-results. Which results in test shown as broken instead of failed in the report.
I'm using "allure-framework/allure-phpunit": "1.3.0" and allure command line version 2.13.0
The text was updated successfully, but these errors were encountered:
One should not throw exceptions to fail a test, but rather use special asserting tools to either check results of test, or expect an exception (thus, catching it but not allowing test suite to fail due to unhandled test exception).
Some code would help to clarify, though.
You're right. Perhaps, we're passing custom exception in parent::onNotSuccessfulTest($newException); is causing test to appear broken instead of failed.
We use
public function onNotSuccessfulTest(Throwable $e){
$newException = new \Exception(
$e->getMessage()
. "\n" . $e->getTraceAsString(),
0
);
parent::onNotSuccessfulTest($newException);
}
Status of a failing test is marked as broken by this adapter in the xmls under allure-results. Which results in test shown as broken instead of failed in the report.
I'm using "allure-framework/allure-phpunit": "1.3.0" and allure command line version 2.13.0
The text was updated successfully, but these errors were encountered: