-
Notifications
You must be signed in to change notification settings - Fork 6
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
Test docgen code at a granular level #71
Comments
Regarding this issue, I can tell you what it is the idea that I'm trying to implement in my own code:
Is this reasonable for you, @cmnbroad? |
Yes, a mocking framework is probably the right way to do this. Do you already have code that does this ? I'd like to solve this problem in Barclay before we add any more new features. |
I was exploring this a bit in my toolkit and I implemented some minor tests as a proof-of-concept. If you like, I can add a couple of tests with Mockito and remove the |
@magicDGS That would be very useful. I wouldn't remove the TestDoclet test though, since we definitely need to test both default and custom doclet cases. At some point we may have enough mocked unit tests that we can remove one of them, but for now I think we should keep both. At least this will give us a start in the direction of less file bloat. |
From @cmnbroad (#68 (comment)):
The text was updated successfully, but these errors were encountered: