Skip to content
This repository was archived by the owner on Aug 5, 2022. It is now read-only.

Conversation

@dawagner
Copy link
Contributor

@dawagner dawagner commented Jun 2, 2015

Two criterion display fixes/improvements.

clero added 2 commits June 2, 2015 20:47
InclusiveCriterion has a default state called "none", this state was
displayed through default Criterion behavior which is: if no valid state
is available, let's display "<none>".

This patch test explicitly the default value when formatting the state
of an InclusiveCriterion. It also introduces the test getLiteralValue
return when formatting a standard Criterion rather than testing the
generated string emptiness.
A difference can now be made between an inclusive criterion default
value and an exclusive criterion with an unknown state.

Signed-off-by: Jules Clero <julesx.clero@intel.com>
Criterion type, which can be inclusive or exclusive is displayed
sometimes with a capital letter and sometimes not.
This patch corrects this behaviour to always have the first letter
in capital.

Signed-off-by: Jules Clero <julesx.clero@intel.com>
@dawagner dawagner added the bug label Jun 2, 2015
@dawagner dawagner added this to the Version 3 milestone Jun 2, 2015
@coveralls
Copy link

Coverage Status

Coverage increased (+0.0%) to 69.94% when pulling db5bfd3 on dawagner:fix-criterion-display into 8807207 on 01org:next.

dawagner added a commit that referenced this pull request Jun 2, 2015
Fix criterion display

Two criterion display fixes/improvements.
@dawagner dawagner merged commit ccf78da into intel:next Jun 2, 2015
@dawagner dawagner deleted the fix-criterion-display branch June 2, 2015 18:58
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants