Skip to content

Conversation

d-stahl-ericsson
Copy link
Contributor

No description provided.

@d-stahl-ericsson
Copy link
Contributor Author

Addresses issue #31.

@p-backman-ericsson
Copy link
Contributor

👍
Although I am not really fond of the concept of defining outcome as not required and defining all members of outcome as not required. I would have set conclusion and verdict as required. You could still choose to not have an outcome. But perhaps it is a valid use case to only use a description?

@d-stahl-ericsson
Copy link
Contributor Author

The idea is that they are mandatory for test cases, but not for test suites. It's not always obvious what an explicit outcome of a test suite means, depending on the nature of that suite, e.g. if it's more of a transient ad-hoc collection of test cases that happened to be executed together. Consequently, if it makes sense you can define an outcome for the test suite as a whole, whereas test cases must have an explicit outcome.

@e-backmark-ericsson
Copy link
Member

e-backmark-ericsson commented Aug 23, 2016

Typo: failued -> failed

@d-stahl-ericsson d-stahl-ericsson force-pushed the topic-drop3-testsuitefinished branch from c767553 to a8dccd9 Compare August 31, 2016 07:10
@d-stahl-ericsson d-stahl-ericsson merged commit 9554a5d into eiffel-community:topic-drop3 Aug 31, 2016
@d-stahl-ericsson d-stahl-ericsson deleted the topic-drop3-testsuitefinished branch September 30, 2016 06:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants