The EiffelIssueVerifiedEvent declares that an issue, typically a requirement, has been verified by some means. It is different from EiffelTestCaseFinishedEvent in that multiple test case executions may serve as the basis for a single verification or, conversely, multiple issues may be verified based on a single test case execution.
Type: Object[]
Required: Yes
Description: A list of verified (successfully or not) issues.
Type: String
Required: Yes
Legal values: BUG, IMPROVEMENT, FEATURE, WORK_ITEM, REQUIREMENT, OTHER
Description: The type of issue.
Type: String
Required: Yes
Description: The name of the issue tracker. This can unfortunately not be standardized, and is therefore context sensitive: though some trackers and ALM tools are more popular than others, an exhaustive enumeration is impossible, particularly when considering company specific internal solutions. Consequently one should not rely on the name as the primary method of retrieval, but rather data.issues.uri. data.issues.tracker together with data.issues.id is still useful for analysis and traceability, however, as long as it can be correctly interpreted.
Type: String
Required: Yes
Description: The identity of the issue. This is tracker dependent - most trackers have their own issue naming schemes.
Type: String
Required: Yes
Description: The URI of the issue.
Type: String
Required: Yes
Legal values: SUCCESS, FAILURE, INCONCLUSIVE
Description: The value of the verification.
SUCCESS signifies that the issue was successfully verified.
FAILURE signifies that verification of the issue failed.
INCONCLUSIVE signifies that the verification of the issue was inconclusive.
| Version | Introduced in | Changes |
|---|---|---|
| 1.0.0 | edition-bordeaux | Initial version. |