Closed oomelianchuk closed 4 years ago
The issue can probably be fixed by editing the describeChild
method to match the following code:
@Override
protected Description describeChild(FrameworkMethod method)
{
return childDescriptions.computeIfAbsent(method, (m) -> {
return Description.createTestDescription(getTestClass().getJavaClass(), m.getName(), method.getAnnotations());
});
}
added the fix
@oomelianchuk and @h-arlt : Can be recheck.
Works as desired.
There is an option to add a description to
org.junit.@Ignore
to make Allure display a reason for test ignorance, like this:@Ignore("not implemented yet")
/@Ignore("it's possible to add property with missing key")
so that allure report looks like this for the class:
and for the method:
Currently, this works only for class level and a test method annotated in the named above way will still be displayed as:
This behavior can be caused by overriding the
describeChild
method ofBlockJUnit4ClassRunner
in theNeodymiumRunner
. The method from Neodymium doesn't pass test method annotations to the description, which makes it impossible for allure to figure out the ignorance reason.