-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gradle plugin #49
Gradle plugin #49
Conversation
Hi @luksrn ! Awesome job, thank you! So far I've only had the time to scan the code, but I'll try it soon as well, and merge the PR. Thanks, |
Hey @luksrn! I had some time in my hands, so I could take a closer look at your PR (sorry that it took me this long). I was able to try the plugin locally with the following steps:
👍 It works nicely 👍 The generated HTML report correctly contains the Scott report: And running the tests with A few questions:
Many thanks! |
Hey @dodie , how are you, man? I hope you're ok! I made the changes that you suggested. Good points. |
Hey @luksrn! Cool thanks! Thank you for all your effort! The plugin works as expected, and it's implemented really nicely! I'll release it at the end of the month along with a new version of Scott. |
Issue #44
Please read https://guides.gradle.org/publishing-plugins-to-gradle- plugin-portal /
After configuring your credentials you can publish the plugin locale at scott-gradle-plugin folder
$ ./gradlew tasks
$ ./gradlew publishPlugins
To test/approve the PR, I believe you can follow those flow to generate the artifacts and test the changes.
The Junit4 and Junit5 test reports keep detailed information, but only cucumber reports generated by scott.
🇧🇷