All Classes and Interfaces

Class
Description
The class contains some useful methods to work with AllureLifecycle.
Step context.
Runnable that allows to throw an exception and return any type.
Callable that allows to throw an exception and return void.
Runnable that allows to throw an exception and return any type.
Runnable that allows to throw an exception and return void.
The type Allure 2 model jackson.
Defines common file naming constants for Allure result artifacts.
Mutable execution context that stores a stack of running Allure executable keys.
Adapter-owned lifecycle identity.
Used by Allure Enterprise to link test cases with related test methods.
The Allure lifecycle: one class, three method groups.
Signals that Allure results could not be written.
 
Thread binding returned by AllureLifecycle.bind(AllureExternalKey), AllureLifecycle.bindDetached(AllureExternalKey), or AllureLifecycle.bindEmpty() that restores the previous thread context when closed.
Thread-local binding for the current Allure execution context.
Collection of utils used by Allure integration to extract meta information from test cases via reflection.
Utility methods used by AspectJ-based Allure integrations.
Used to mark methods that produce attachments.
Provides binary attachment content for custom values returned by methods annotated with Attachment.
Additional options for an attachment.
Aspects (AspectJ) for handling Attachment.
Notifies about Allure test container lifecycle.
Annotation that allows to attach a description for a test.
Used to mark tests with epic label.
Wrapper annotation for Epic.
Utility methods for translating exceptions into Allure status details.
Used to mark tests with feature label.
Wrapper annotation for Feature.
Writes Allure result model objects and attachments to the file system.
The TestPlanSupplier that reads test plan from file, specified in ALLURE_TESTPLAN_PATH environment variable.
Notifies about Allure test fixtures lifecycle events.
Used to mark tests as flaky (unstable).
Allure HTTP exchange attachment payload.
Builder for HttpExchange.
HTTP body captured in an exchange attachment.
Multipart body part captured in an exchange attachment.
HTTP cookie captured in an exchange attachment.
Error captured while processing an HTTP exchange.
Informational HTTP response captured before a final response.
Name-value pair used by HTTP exchange attachments.
HTTP request captured in an exchange attachment.
Builder for HttpExchangeRequest.
HTTP response captured in an exchange attachment.
Serializes HTTP exchange attachments using the Jackson runtime bundled with allure-java-commons.
Streaming body metadata captured in an exchange attachment.
Used to link tests with issues.
Wrapper annotation for Issue.
Internal serialization shared by Allure modules without exposing the bundled Jackson API.
Marker annotation.
Wrapper annotation for LabelAnnotation.
This annotation used to specify project leads for test case.
Marker interface for lifecycle listeners.
Dispatches lifecycle events to the registered listeners.
Use this annotation to add some links to results.
Marker annotation.
Wrapper annotation for LinkAnnotation.
Wrapper annotation for Link.
Used to mute tests.
Utility methods for resolving human-readable test and step names.
Utility methods for safe object string conversion.
This annotation used to specify owner for test case.
This annotation used to add parameters to results from method parameters.
Utility methods for converting Java method arguments into Allure parameters.
The collection of properties utils methods.
Utility methods for creating and enriching Allure result model objects.
Internal service loader util.
Used to set severity for tests.
Enumerates standard Allure severity levels.
Annotations to mark step methods.
Notifies about Allure step lifecycle events.
AspectJ advice that turns Step methods into Allure steps.
Wrapper annotation for Story.
Used to mark test case with a story label.
Listener that notifies about Allure Lifecycle events.
Represents a loaded Allure test plan.
Reads Allure test plans without exposing the bundled JSON implementation.
Marker interface for all test plan suppliers.
Fallback model for an Allure test plan with an unknown schema.
Allure test plan model for version 1.0.
Test plan test case.
Used to link tests with test cases in external test management system.
Wrapper annotation for TmsLink.
Utility methods to resolve well-known attachment file extensions.