Added example and documentation of EiffelTestSuiteStartedEvent. #54
Conversation
| ### data.liveLogs | ||
| __Type:__ Object[] | ||
| __Required:__ No | ||
| __Description:__ An array of live log files available during execution. These shall not be presumed to be stored persistently; in other words, once the activity has finished there is no guarantee that these links are valid. Persistently stored logs shall be (re-)declared by [EiffelActivityFinishedEvent](./EiffelActivityFinishedEvent.md). |
There was a problem hiding this comment.
change activity has finished to test suite has finished. Also change EiffelActivityFinishedEvent to EiffelTestSuiteFinishedEvent
| "type": "EiffelTestSuiteStartedEvent", | ||
| "version": "1.0", | ||
| "time": 1234567890, | ||
| "domainId": "example.domain", |
There was a problem hiding this comment.
domainId should be inside source.
|
👍 |
|
Suggestion: Rephrase the first sentence to 'The EiffelTestSuiteStartedEvent declares that the execution of a test suite has started. ' and add a reference to what a 'test suite' means in the Eiffel context. Test suite executions are kind of a subclass of Activities, right. The definition of a 'test suite' should define what makes this kind of Activity so special that it needs its own lifecycle events. |
|
I have a question. Let's say someone is about to build a radiator showing the test progress in run time. I guess this would be done by picking up the EiffelTestSuiteStartedEvent and then listening to the EiffelTestCaseFinishedEvents that are linked to the same CONTEXT as in the initial EiffelTestSuiteStartedEvent. Please correct me if I'm wrong! Now to my question. Is there a way to get the number of expected test cases to be executed? I know this is not possible to know in some cases, but if the number of test cases is known then this would be very interesting data to a radiator, so that it could show a correct progress count down. |
|
Correct (although the link goes via TestCaseStarted to TestSuiteStarted). That being said, you have multiple options for displaying test execution status. You could look for events referencing a suite, as you mention, or you could go for tests referencing a particular artifact, or a particular requirement in a particular FlowContext, or something similar. Depends on your use case. Assuming that what you want to do is track progress of a test suite, then yes you can do that by using TestExecutionRecipeCreated. Slated for Drop 4 and so not available yet, but mentioned in #41 and #56. |
No description provided.