GH-2639: Implement skeleton for ClassLoaderAssert - #2645
Conversation
4ebafef to
4420781
Compare
|
I am out for the rest of today and part of tomorrow, so I will likely continue to look at this on Sunday at some point |
|
Sure, take your time @ascopes, and thank you! |
27211b4 to
f782571
Compare
f782571 to
e607f2d
Compare
e607f2d to
eaf3da2
Compare
|
Added a commit at the start that addresses a transitive issue with the Future tests on the Windows runner. I will cherry-pick this onto a separate branch so it can be reviewed separately first. |
0ce5b8b to
576fe97
Compare
576fe97 to
775ee47
Compare
775ee47 to
c8ceb18
Compare
- Implement skeleton type for AbstractClassLoaderAssert. - Implement ClassLoaderAssert implementation. - Hook up with Assertions, Assumptions, BDDAssertions, BDDAssumptions, BDDSoftAssertionsProvider, InstanceOfAssertFactories, StandardSoftAssertionsProvider, WithAssertions, and WithAssumptions. - Write ClassLoaderAssert-bound tests for Assertions, Assumptions, BDDAssertions, BDDAssumptions, InstanceOfAssertFactories, WithAssertions. - AssertionsUtil#expectAssumptionNotMetException now returns an AssumptionViolatedException rather than void, as to match with the API for AssertionsUtil#expectAssertionError. Since nothing relied on the return value before as this was a void method, this should not break anything existing.
c8ceb18 to
2694870
Compare
|
This is now merged. Thanks, @ascopes! I applied some changes like adding the version tags and some missing Also, I reverted the changes for |
First PR for #2639.
BDDSoftAssertionsProvider, InstanceOfAssertFactories,
StandardSoftAssertionsProvider, WithAssertions, and WithAssumptions.
BDDAssertions, BDDAssumptions, InstanceOfAssertFactories,
WithAssertions.
an AssumptionViolatedException rather than void, as to match with
the API for AssertionsUtil#expectAssertionError. Since nothing
relied on the return value before as this was a void method, this
should not break anything existing.
I will add code examples to the second PR once a solid API has
been agreed on, as it prevents missing anything and creating
erroneous documentation.