Skip to content

chore(deps): Bump WireMock.Net from 1.5.28 to 1.5.35 #399

chore(deps): Bump WireMock.Net from 1.5.28 to 1.5.35

chore(deps): Bump WireMock.Net from 1.5.28 to 1.5.35 #399

GitHub Actions / Test Results BunsenBurner succeeded Sep 17, 2023 in 0s

Test Results BunsenBurner ✅

Tests passed successfully

✅ BunsenBurner.Tests/TestResults/test-results.trx

73 tests were completed in 2s with 73 passed, 0 failed and 0 skipped.

Test suite Passed Failed Skipped Time
BunsenBurner.Tests.AaaTests 22✅ 79ms
BunsenBurner.Tests.ActedLinqTests 5✅ 136ms
BunsenBurner.Tests.ArrangeLinqTests 5✅ 115ms
BunsenBurner.Tests.BddTests 21✅ 199ms
BunsenBurner.Tests.CacheTests 2✅ 69ms
BunsenBurner.Tests.ManualDisposalTests 2✅ 4ms
BunsenBurner.Tests.OnceTests 6✅ 260ms
BunsenBurner.Tests.TheoryTests 10✅ 1ms

✅ BunsenBurner.Tests.AaaTests

✅ Additional And assertions work
✅ Async methods operate correctly
✅ Expression based assertions on failures with data work
✅ Expression based assertions on failures work
✅ Expression based assertions on typed failures work
✅ Expression based assertions that are wrong fail
✅ Expression based assertions with data that are wrong fail
✅ Expression based assertions with data work
✅ Expression based assertions work
✅ Failure assertions throw on successful async functions
✅ Failure assertions work on async functions
✅ Failure assertions work on async functions with initial data
✅ Failure assertions work on sync functions
✅ Failure assertions work on sync functions and initial data
✅ Mixing sync and async methods operate correctly
✅ Mixing sync and async methods operate correctly
✅ Scenario can be reset back to acted
✅ Scenario can be reset back to arranged from acted
✅ Scenario can be reset back to arranged from asserted
✅ Scenario can have act redefined
✅ Scenario can have an async act redefined
✅ Sync methods operate correctly

✅ BunsenBurner.Tests.ActedLinqTests

✅ Acted Aaa scenarios can be combined with bind
✅ Acted Aaa scenarios can be combined with bind
✅ Acted Aaa scenarios can be selected
✅ Acted Bdd scenarios can be selected
✅ Scenarios can be combined with Sequence

✅ BunsenBurner.Tests.ArrangeLinqTests

✅ Arranged Aaa scenarios can be combined with bind
✅ Arranged Aaa scenarios can be combined with bind
✅ Arranged Aaa scenarios can be selected
✅ Arranged Bdd scenarios can be selected
✅ Scenarios can be combined with Sequence

✅ BunsenBurner.Tests.BddTests

✅ Additional And assertions work
✅ Async methods operate correctly
✅ Expression based assertions on failures with data work
✅ Expression based assertions on failures work
✅ Expression based assertions on typed failures work
✅ Expression based assertions that are wrong fail
✅ Expression based assertions with data that are wrong fail
✅ Expression based assertions with data work
✅ Expression based assertions work
✅ Failure assertions work on async functions
✅ Failure assertions work on async functions with initial data
✅ Failure assertions work on sync functions
✅ Failure assertions work on sync functions and initial data
✅ Mixing sync and async methods operate correctly
✅ Mixing sync and async methods operate correctly
✅ Scenario can be reset back to acted
✅ Scenario can be reset back to arranged from acted
✅ Scenario can be reset back to arranged from asserted
✅ Scenario can have act redefined
✅ Scenario can have an async act redefined
✅ Sync methods operate correctly

✅ BunsenBurner.Tests.CacheTests

✅ Cache is cleared and non-disposable values can be cached
✅ Caches dispose all disposable values

✅ BunsenBurner.Tests.ManualDisposalTests

✅ Disposal is automatic
✅ Manual disposal protects from automatic disposal

✅ BunsenBurner.Tests.OnceTests

✅ Once of T can be accessed in parallel without issue
✅ Once of T on ever runs once
✅ Once of T on ever runs once for an async function
✅ Once's can be combined
✅ Once's can be combined once
✅ Once's can be mapped

✅ BunsenBurner.Tests.TheoryTests

✅ Scenarios work well in theories(scenario: 1 can be converted to a string)
✅ Scenarios work well in theories(scenario: 10 can be converted to a string)
✅ Scenarios work well in theories(scenario: 2 can be converted to a string)
✅ Scenarios work well in theories(scenario: 3 can be converted to a string)
✅ Scenarios work well in theories(scenario: 4 can be converted to a string)
✅ Scenarios work well in theories(scenario: 5 can be converted to a string)
✅ Scenarios work well in theories(scenario: 6 can be converted to a string)
✅ Scenarios work well in theories(scenario: 7 can be converted to a string)
✅ Scenarios work well in theories(scenario: 8 can be converted to a string)
✅ Scenarios work well in theories(scenario: 9 can be converted to a string)