-
Notifications
You must be signed in to change notification settings - Fork 168
Add ScalaTest Listeners-Adaptor #162
Comments
@eroshenkoam |
Will jump from this https://github.com/allure-framework/allure-jenkins-plugin/blob/master/src/main/java/ru/yandex/qatools/allure/jenkins/AllureReportCollector.java#L53, tell me if there is some trick |
if you have folders with allure xml results than you need to use AllureReportGenerator like this:
after that in allureOutputDirectory you will see the json's in the 'data' subdirectory |
This one is planned for the nearest future. |
@dmakhno Please look at the following repositories: https://github.com/allure-framework/allure-scalatest and https://github.com/allure-framework/allure-scalatest-example They contain a working adapter implementation. What I still don't get is how to annotate "should" blocks with method annotations like @title and so on. Any issues or proposals about it? |
Btw, forgot to say that currently adapter is not deployed to Maven so in order to test the example you need to do "sbt publish-local". |
Let's deploy adapter to Maven Central and then close this. |
Deployed 1.3.9-SNAPSHOT to Maven Central. Need someone else to test the example. |
It seems need to implement Reporter with specific to
Allure functionality, taking in account that ScalaTest may have nested suites
I hope 'ru.yandex.qatools.allure.annotations' will work as expected without any actions.
This should allow to start using it with sbt by passing reporter param to Runner:
something like
and then, incrementally,
new sbt-plugin might add this dependencies for all test, providing step that executed after test, testQuick, testOnly sbt command to generate report.
@bvenners, @cheeseng, you might be interested in this. If you have ideas how to do it better, please share your thought.
Inspired By: Selenium Camp 2014
The text was updated successfully, but these errors were encountered: