Specify which build states can / should be used

scenarioo / scenarioo-format

Specification of the next generation Scenarioo documentation format (for version 3.0 and upwards)

http://www.scenarioo.org

GNU Lesser General Public License v3.0

0 stars 2 forks source link

Specify which build states can / should be used #21

Closed bruderol closed 8 years ago

bruderol commented 8 years ago

currently even the failed and success states could be altered (through config) but the libraries usualy have an enum for this two special default styles, in general all names of states can be used.

In general the libraries should use failed and success and whatever other states the used technology (e.g. testing toolkit) usualy uses for things like pending, ìgnore etc.

bruderol commented 8 years ago

status field is a free text field
"success" and "failed" are default states to be used for successful (=green displayed) or failed (=red displayed) scenarios (case sensitive! in lower case!), all other statuses are treated as unknown or undefined and visualized orange-warning-style
Statuses can also be left empty (except for scenario) in which case they are calculated for use case and build from contained scenario states.

bruderol commented 8 years ago

currently the server has a configuration property for successful state, but that is not used consequently, which is why we should probably remove that config possibility.

bruderol commented 8 years ago

TODO: open an issue to remove the server side configuraiton that is not consistently used, then this can be closed.