-
Notifications
You must be signed in to change notification settings - Fork 466
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
Add FAQ to documentation #1212
Add FAQ to documentation #1212
Conversation
For now, there are two FAQ items explaining optional dependencies in general and explaining why there are two class mocking variants ByteBuddy vs. CGLIB. Closes spockframework#1165.
Codecov Report
@@ Coverage Diff @@
## master #1212 +/- ##
=========================================
Coverage 76.27% 76.27%
Complexity 3678 3678
=========================================
Files 396 396
Lines 11264 11264
Branches 1382 1382
=========================================
Hits 8592 8592
Misses 2193 2193
Partials 479 479 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should also be mentioned, that spock will use ByteBuddy if both libraries are on the classpath.
Also please format according to one sentence per line, I know that not every part of the guide follows that guideline yet, but new documentation should.
Co-authored-by: Leonard Brünings <lord_damokles@gmx.net>
Co-authored-by: Leonard Brünings <lord_damokles@gmx.net>
Co-authored-by: Leonard Brünings <lord_damokles@gmx.net>
For now, there are two FAQ items explaining optional dependencies in general and
explaining why there are two class mocking variants ByteBuddy vs. CGLIB.
Closes #1165.
This change is