kmock/tech.antibytes.kmock.verification/NonFreezingAsserter

NonFreezingAsserter

class NonFreezingAsserter(coverAllInvocations: Boolean = false) : AsserterBase

Container which collects and holds actual references of proxy calls in a non freezing manner. The references are ordered by their invocation.

Author

Matthias Geisler

See also

Parameters

coverAllInvocations

flag to enable/disable capturing including explicit ignorable Proxies. Default is false.

Constructors

Link copied to clipboard
fun NonFreezingAsserter(coverAllInvocations: Boolean = false)

Functions

Link copied to clipboard
open override fun clear()

Clears the Container

Properties

Link copied to clipboard
open override val references: List<KMockContract.Reference>

Holds the actual references

Extensions

Link copied to clipboard
fun KMockContract.Asserter.assertOrder(action: KMockContract.ChainedAssertion.() -> Any)

Asserts a chain of Expectations. Each Expectation must be in strict order of the referenced Proxy invocations and all invocations must be present.

Link copied to clipboard
suspend fun KMockContract.Asserter.asyncAssertOrder(action: suspend KMockContract.ChainedAssertion.() -> Any)

Asserts a chain of Expectations in a coroutine Context. Each Expectation must be in strict order of the referenced Proxy invocations and all invocations must be present. Use that context only in combination with proxy access methods.

Link copied to clipboard
suspend fun KMockContract.Asserter.asyncVerifyOrder(action: suspend KMockContract.ChainedAssertion.() -> Any)

Verifies a chain of Expectations in a Coroutine Context. Each Expectation must be in order but gaps are allowed. Also the chain does not need to be exhaustive. Use that context only in combination with proxy access methods.

Link copied to clipboard
suspend fun KMockContract.Asserter.asyncVerifyStrictOrder(action: suspend KMockContract.ChainedAssertion.() -> Any)

Verifies a chain of Expectations in a Coroutine Context. Expectation between different proxies can contain gaps. Also the chain does not need to be exhaustive. Use that context only in combination with proxy access methods.

Link copied to clipboard
fun KMockContract.Asserter.verifyOrder(action: KMockContract.ChainedAssertion.() -> Any)

Verifies a chain of Expectations. Each Expectation must be in order but gaps are allowed. Also the chain does not need to be exhaustive.

Link copied to clipboard
fun KMockContract.Asserter.verifyStrictOrder(action: KMockContract.ChainedAssertion.() -> Any)

Verifies a chain of Expectations. Expectation between different proxies can contain gaps. Also the chain does not need to be exhaustive.