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

SuiteSetUp colored yellow in test summary #80

Closed
jediwhale opened this issue Apr 30, 2012 · 7 comments
Closed

SuiteSetUp colored yellow in test summary #80

jediwhale opened this issue Apr 30, 2012 · 7 comments

Comments

@jediwhale
Copy link
Collaborator

From SO:

FitNesse's SuiteSetup page is shown as yellow instead of green in the test results. This can be corrected by adding a dummy test that has at least one green cell. But surely a setup page shouldn't require an actual test cell?

@amolenaar
Copy link
Collaborator

Hi,

I think I just corrected this (#52). I feel the setup page should not contain any (functional) test. It's still counted as an ignored page though.

@jediwhale
Copy link
Collaborator Author

great!

@mightymuke
Copy link

Hi,
While the SuiteSetup page is now green in the test results, the test summary still shows 1 ignored page. Is this the intended behaviour? ie - this this what is meant by the comment "It's still counted as an ignored page though."?
Would it not be preferable to treat it the same as a Setup page?
Thanks.

@amolenaar
Copy link
Collaborator

Yes it is :)

I kept that as is. I found that not too much ignoring, since the test will make the result bar turn green. Changing this is slightly more involved.
A setup page is included (as in: literally included in the to be executed page). So the behaviour is different from the start.

@mightymuke
Copy link

OK - thanks.

Our build server (Jenkins) processes the XML response, and marks the ignored test as yellow. Would you expect applications that process the XML to implement the same logic as your fix, or do you expect the slightly more involved solution will be investigated at a later stage?

I have implemented a work around by transforming the XML before delivering it to Jenkins, but it feels a little dodgy.

Thanks.

@amolenaar
Copy link
Collaborator

Hi,

It was a little more coding than I expected. Now if a SuiteSetUp/TearDown contains no tests it's colored green (pass) and is counted as a "right" test case. Also the logic for test pages and test history is unified.

Regards,

Arjan

@mightymuke
Copy link

Looks awesome - thanks very much!

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

No branches or pull requests

3 participants