Skip to content
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

Refactor AsciidoctorMojoTest from Groovy to Java #512

Merged

Conversation

abelsromero
Copy link
Member

Thank you for opening a pull request and contributing to asciidoctor-maven-plugin!

What kind of change does this PR introduce? (check at least one)

  • Bugfix
  • Feature
  • Documentation
  • Refactor
  • Build improvement
  • Other (please describe)

What is the goal of this pull request?
Make code more approachable by migrating the tests to Java from Groovy.
Nothing bad about Groovy, but JUnit + AssertJ have come to offer similar ease of use.
In the long term, also simplifies the build by removing groovy compilation steps.

Are there any alternative ways to implement this?
I am taking the opportunity to review the tests to remove duplication and unnecessary tests. But overall is a as-is migration.

Are there any implications of this pull request? Anything a user must know?
No

Is it related to an existing issue?

  • Yes
  • No

Finally, please add a corresponding entry to CHANGELOG.adoc

@abelsromero abelsromero force-pushed the refactor/migrate-mojoTest-to-Java branch from c15e596 to 09d919b Compare March 10, 2021 21:43
@coveralls
Copy link

coveralls commented Mar 10, 2021

Coverage Status

Coverage decreased (-1.4%) to 83.595% when pulling cdbc130 on abelsromero:refactor/migrate-mojoTest-to-Java into e7df5a6 on asciidoctor:master.

@abelsromero
Copy link
Member Author

Re-organized some tests under AsciidoctorIntegrationTest.

@abelsromero abelsromero force-pushed the refactor/migrate-mojoTest-to-Java branch 3 times, most recently from 00eefaf to 74c797b Compare March 13, 2021 19:33
@abelsromero abelsromero marked this pull request as ready for review March 13, 2021 19:33
@abelsromero
Copy link
Member Author

Pendind squash, but code is up for review

@abelsromero abelsromero changed the title Start migration of MojoTest to Java Refactor AsciidoctorMojoTest from Groovy to Java Mar 13, 2021
@abelsromero abelsromero force-pushed the refactor/migrate-mojoTest-to-Java branch 3 times, most recently from 496f7c9 to e7009cc Compare March 13, 2021 20:00
@abelsromero
Copy link
Member Author

AppVeyour error is the random network I've never been able to narrow down 😞

@abelsromero abelsromero force-pushed the refactor/migrate-mojoTest-to-Java branch from e7009cc to e0ef5a7 Compare March 13, 2021 20:46
* Split tests into AsciidoctorMojoTest and AsciidoctorIntegrationTest
* Rewrite AsciidoctorMojoTest to Java using Junit4 + Assertj
* Automated output directory creation to avoid creation/cleanup on every test
* Created `AsciidoctorAsserter` to easily validate converted documents
@abelsromero abelsromero force-pushed the refactor/migrate-mojoTest-to-Java branch from e0ef5a7 to cdbc130 Compare March 13, 2021 20:56
@abelsromero abelsromero merged commit 31653da into asciidoctor:master Mar 13, 2021
@abelsromero abelsromero deleted the refactor/migrate-mojoTest-to-Java branch April 10, 2021 12:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants