We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Adding this to every test class is tedious and error-prone:
@AfterTest fun verify() { verifyNoUnverifiedExpectations(dep1) verifyNoUnverifiedExpectations(dep2) verifyNoUnverifiedExpectations(dep3) verifyNoUnmetExpectations(dep1) verifyNoUnmetExpectations(dep2) verifyNoUnmetExpectations(dep3) }
Is there a way to get mocks?
i.e.
@AfterTest fun verify() { mocks().forEach { // runs for dep1, dep2, dep3 verifyNoUnverifiedExpectations(it) verifyNoUnmetExpectations(it) } }
This would enable nice abstractions and helper methods to reduce boilerplate.
(Might require a Mocker stateholder similar to MocKMP. I chose your library because MocKMP is full of workarounds hacks and weird APIs.)
Mocker
The text was updated successfully, but these errors were encountered:
Hi @TWiStErRob
Sorry for my hiatus from the project. I like this suggestion, and I believe we could generate code to do something like this instead:
@AfterTest fun verify() { verifyMockative(this) }
I'll have a look as to whether we can generate a function for every test class, which would access the test properties and verify them.
Sorry, something went wrong.
Try to separate/enable the two different verifyNo classes in the API as they're significantly different functionality.
Nillerr
No branches or pull requests
Adding this to every test class is tedious and error-prone:
Is there a way to get mocks?
i.e.
This would enable nice abstractions and helper methods to reduce boilerplate.
(Might require a
Mocker
stateholder similar to MocKMP. I chose your library because MocKMP is full of workarounds hacks and weird APIs.)The text was updated successfully, but these errors were encountered: