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

Specs2 support #85

Merged
merged 51 commits into from
Apr 12, 2019
Merged

Specs2 support #85

merged 51 commits into from
Apr 12, 2019

Conversation

ultrasecreth
Copy link
Member

  • Adds support for specs2
  • Extract Scalatest specific code to it's own module
  • Adds support for Scalatest AsyncSpec (ScalaTest AsyncWordSpec and wasCalled #57)
  • Code improvements
  • Minor bug fixes
  • Minor features added

@ultrasecreth ultrasecreth force-pushed the specs2-support branch 4 times, most recently from d63e835 to c91a740 Compare April 4, 2019 18:10
@ultrasecreth
Copy link
Member Author

@mockitoguy this PR adds 2 new artefacts (mockito-scala-scalatest & mockito-scala-specs2), similar idea to mockito-junit-jupiter, would this be a problem with how the current publishing works? or just merging the PR and letting shipkit works its magic would be enough? - Thanks!

ultrasecreth and others added 23 commits April 7, 2019 16:01
…compatible.Assertion rather than Unit, this allows a verify line to be the last one in an Async test
… eqTo directly

defaultMatcher relies on the DefaultMatcher[T] type class, so the actual matcher to be used can be overridden by the user or any framework extension
@mockitoguy
Copy link
Member

No problem pushing multiple artifacts. Shipkit handles this (Mockito does it).

Are you sure you want to ship different versions? It is non standard and may increase entropy. Why don't we ship beta version for all artifacts? I realize that it would not be 100% correct but you get simplicity in return :)

If you are really keen on different versions, changes in Shipkit may be needed (there's only one way to find out...)

@ultrasecreth
Copy link
Member Author

@mockitoguy Cool, I'll try and see what happens :) worst case scenario the beta one will not be released at all!

@ultrasecreth ultrasecreth merged commit f69ec7d into release/1.x Apr 12, 2019
@ultrasecreth ultrasecreth deleted the specs2-support branch June 2, 2019 19:52
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.

None yet

3 participants