Verifyica has various core interfaces / classes / annotations that make up the API.
See ANNOTATIONS for details.
The Argument interface is used to contain test arguments.
Any ArgumentSupplier method that returns a non-Argument Object will be wrapped as an Argument.
- the
Argumentname will beargument[<POSITIONAL INDEX>] - the
Argumentvalue type will beObject
Notes
- static
Argumentfactory methods create arguments that do NOT implementequals()
Interface with common methods for all Context implementations.
It's common purpose to get a reference to an scoped Map<String, Object>
An EngineContext is used to ...
- get the Engine Configuration
- get the associated context
Map<String, Object>
The ClassContext is used to ...
- get the EngineContext
- get information regarding the specific test class
- test class name
- test class instance
- test class argument parallelism
- get the associated context
Map<String, Object>
The ArgumentContext is used to ...
- get the ClassContext
- get the test argument being tested
- test argument name
- test argument value
- test argument index
- get the associated context
Map<String, Object>
Configuration has Properties to get configuration.
LockManager provides way to implement locking semantics.
Trap provides a way to run a task, capturing any exceptions that may occur.
- Use to clean up resources
Execution provides static methods to throw a Execution.ExecutionSkippedException to skip test execution and report the associated method as skipped.
It can only be used in methods annotated with...
@Verifyica.Prepare@Verifyica.BeforeAll@Verifyica.BeforeEach@Verifyica.Test@Verifyica.AfterEach@Verifyica.AfterAll@Verifyica.Conclude
Copyright (C) 2024-present Verifyica project authors and contributors