Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EiffelTestExecutionRecipeCreatedEvent #41

Closed
d-stahl-ericsson opened this issue Jun 23, 2016 · 2 comments
Closed

EiffelTestExecutionRecipeCreatedEvent #41

d-stahl-ericsson opened this issue Jun 23, 2016 · 2 comments
Labels
protocol All protocol changes
Milestone

Comments

@d-stahl-ericsson
Copy link
Contributor

Documentation and example required.

@d-stahl-ericsson d-stahl-ericsson added this to the Drop 4 milestone Jun 23, 2016
d-stahl-ericsson added a commit to d-stahl-ericsson/eiffel that referenced this issue Nov 3, 2016
As per eiffel-community#41. Note that there is a certain degree of
inconsistency in the naming of this event in issues
and documentation, respectively.

The correct name is EiffelTestExecutionRecipeCollectionCreatedEvent.
d-stahl-ericsson added a commit to d-stahl-ericsson/eiffel that referenced this issue Nov 15, 2016
As per eiffel-community#41. Note that there is a certain degree of
inconsistency in the naming of this event in issues
and documentation, respectively.

The correct name is EiffelTestExecutionRecipeCollectionCreatedEvent.
d-stahl-ericsson added a commit to d-stahl-ericsson/eiffel that referenced this issue Dec 1, 2016
As per eiffel-community#41. Note that there is a certain degree of
inconsistency in the naming of this event in issues
and documentation, respectively.

The correct name is EiffelTestExecutionRecipeCollectionCreatedEvent.
@d-stahl-ericsson
Copy link
Contributor Author

Internal workshop review input: Given the current structure, assuming 10k recipes the event will end up on the order of 5MB, which is bad. It should be a protocol design principle that events should not contain properties of highly variable size which is likely to cause very large event sizes.

For this particular event, the conclusion is that the TERC needs to be externally stored and linked via uri. However, a recommended format shall be provided (similar to what is currently proposed in the event).

@e-backmark-ericsson
Copy link
Member

👍

d-stahl-ericsson added a commit to d-stahl-ericsson/eiffel that referenced this issue Dec 16, 2016
As per eiffel-community#41. Note that there is a certain degree of
inconsistency in the naming of this event in issues
and documentation, respectively.

The correct name is EiffelTestExecutionRecipeCollectionCreatedEvent.
d-stahl-ericsson added a commit that referenced this issue Jan 23, 2017
Added EiffelTestExecutionRecipeCollectionCreatedEvent as per #41.
d-stahl-ericsson added a commit that referenced this issue Jan 26, 2017
Added EiffelTestExecutionRecipeCollectionCreatedEvent as per #41.
@magnusbaeck magnusbaeck added the protocol All protocol changes label Nov 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
protocol All protocol changes
Projects
None yet
Development

No branches or pull requests

3 participants