Add ClassLoader assertions

[scordio]

This restores ce3ee9b and will include the changes of #2650.

Closes #2639.

[github-actions]

JUnit test results

  3 999 files  +1    3 999 suites  +1   56s ⏱️ -15s
19 314 tests +4  19 295 ✔️ +4  19 💤 ±0  0 ❌ ±0 
19 411 runs  +3  19 391 ✔️ +3  20 💤 ±0  0 ❌ ±0 

Results for commit b8e803d. ± Comparison against base commit 5ac5e82.

This pull request removes 1179 and adds 1075 tests. Note that renamed tests count towards both.

  

  b
  -1000000000-01-01T00:00:00Z
  07:10
  07:10Z
  07:23
  07:23Z
  2017-03-08T07:10
  2017-03-08T07:10-05:00[America/New_York]
…

AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[1] org.assertj.core.api.InstantAssert@1, org.assertj.core.api.InstantAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@51, 2017-03-12T07:12:00Z, 2017-03-12T07:12:00Z, 2017-03-08T07:10:00Z, 2017-03-08T07:10:00Z, 
Expecting actual:
  2017-03-12T07:10:00Z
to be close to:
  2017-03-08T07:10:00Z
within 50 Hours but difference was 96 Hours, null
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[2] org.assertj.core.api.InstantAssert@1, org.assertj.core.api.InstantAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@21, 2017-03-12T07:10:00.001Z, 2017-03-12T07:10:00.001Z, -1000000000-01-01T00:00:00Z, -1000000000-01-01T00:00:00Z, 
Expecting actual:
  2017-03-12T07:10:00Z
to be close to:
  -1000000000-01-01T00:00:00Z
within 2 Millis but difference was PT8765837682367H10M, null
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[3] org.assertj.core.api.LocalDateTimeAssert@1, org.assertj.core.api.LocalDateTimeAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@51, 2017-03-10T07:12, 2017-03-10T07:12:00, 2017-03-08T07:10, 2017-03-08T07:10:00, 
Expecting actual:
  2017-03-12T07:10
to be close to:
  2017-03-08T07:10
within 50 Hours but difference was 96 Hours, null
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[4] org.assertj.core.api.LocalDateAssert@1, org.assertj.core.api.LocalDateAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@22, 2017-03-10, 2017-03-10, 2017-03-27, 2017-03-27, 
Expecting actual:
  2017-03-12
to be close to:
  2017-03-27
within 3 Days but difference was 15 Days, org.assertj.core.data.TemporalUnitWithinOffset@20
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[5] org.assertj.core.api.LocalTimeAssert@1, org.assertj.core.api.LocalTimeAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@24, 07:12, 07:12:00, 07:23, 07:23:00, 
Expecting actual:
  07:10
to be close to:
  07:23
within 5 Minutes but difference was 13 Minutes, org.assertj.core.data.TemporalUnitWithinOffset@20
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[6] org.assertj.core.api.OffsetDateTimeAssert@1, org.assertj.core.api.OffsetDateTimeAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@29, 2017-03-12T07:12Z, 2017-03-12T07:12:00Z, 2017-03-12T07:23Z, 2017-03-12T07:23:00Z, 
Expecting actual:
  2017-03-12T07:10Z
to be close to:
  2017-03-12T07:23Z
within 10 Minutes but difference was 13 Minutes, null
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[7] org.assertj.core.api.ZonedDateTimeAssert@1, org.assertj.core.api.ZonedDateTimeAssert@1, org.assertj.core.data.TemporalUnitLessThanOffset@7e, 2017-03-10T07:12-05:00[America/New_York], 2017-03-10T07:12:00-05:00[America/New_York], 2017-03-08T07:10-05:00[America/New_York], 2017-03-08T07:10:00-05:00[America/New_York], 
Expecting actual:
  2017-03-12T07:10-04:00[America/New_York]
to be close to:
  2017-03-08T07:10-05:00[America/New_York]
by less than 95 Hours but difference was 95 Hours, null
AbstractTemporalAssert isCloseTo ‑ should fail if actual is null (ArgumentsAccessor)[8] org.assertj.core.api.OffsetTimeAssert@1, org.assertj.core.api.OffsetTimeAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@21, 07:12Z, 07:12:00Z, 07:23Z, 07:23:00Z, 
Expecting actual:
  07:10Z
to be close to:
  07:23Z
within 2 Minutes but difference was 13 Minutes, org.assertj.core.data.TemporalUnitWithinOffset@20
AbstractTemporalAssert isCloseTo ‑ should fail if offset parameter is null (ArgumentsAccessor)[1] org.assertj.core.api.InstantAssert@1, org.assertj.core.api.InstantAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@51, 2017-03-12T07:12:00Z, 2017-03-12T07:12:00Z, 2017-03-08T07:10:00Z, 2017-03-08T07:10:00Z, 
Expecting actual:
  2017-03-12T07:10:00Z
to be close to:
  2017-03-08T07:10:00Z
within 50 Hours but difference was 96 Hours, null
AbstractTemporalAssert isCloseTo ‑ should fail if offset parameter is null (ArgumentsAccessor)[2] org.assertj.core.api.InstantAssert@1, org.assertj.core.api.InstantAssert@1, org.assertj.core.data.TemporalUnitWithinOffset@21, 2017-03-12T07:10:00.001Z, 2017-03-12T07:10:00.001Z, -1000000000-01-01T00:00:00Z, -1000000000-01-01T00:00:00Z, 
Expecting actual:
  2017-03-12T07:10:00Z
to be close to:
  -1000000000-01-01T00:00:00Z
within 2 Millis but difference was PT8765837682367H10M, null
…

♻️ This comment has been updated with latest results.