Skip to content
This repository has been archived by the owner. It is now read-only.

Support for multiple FitNesse results and drilling into the html output #4

Merged
merged 13 commits into from Mar 3, 2012

Conversation

Projects
None yet
2 participants
@cpfeiffer
Copy link

cpfeiffer commented Feb 23, 2012

Hi Simon,

here's my work regarding multiple results files and drilling down from the toplevel page down into the html results.

I don't actually use the FitNesse executor, but I modified the URL such that it should include the html output in the XML results; so it should work in that scenario as well.

If you have any questions or feedback, just yell.

Thanks,
Carsten

swestcott and others added some commits Sep 15, 2011

Support for hierarchical test results up to the html content
Now that we support multiple test results (suites), we have hierarchical
results: a toplevel compound result with child results. Additionally, we
now support displaying the FitNesse html details for a result, if
available.
Make the hierarchy more sensible and fix FitNesseResults deserialization
A little refactoring to make the hierarchy of FitNesse results
(Compound results, aggregated results, single results and html details).

Additionally, manually restore the "details" member variable on XStream
deserialization, because for some reason it is not automatically
initialized.
@cpfeiffer

This comment has been minimized.

Copy link
Author

cpfeiffer commented Feb 23, 2012

I'm a bit surprised about some changes in the diff... e.g. I'm pretty sure I didn't (manually) do the changes in pom.xml. I'm wondering whether I messed up something because I originally cloned from jenkins-ci instead of your repository. But then, the HEAD of that and yours look identical to me...

swestcott added a commit that referenced this pull request Mar 3, 2012

Merge pull request #4 from cpfeiffer/master
Support for multiple FitNesse results and drilling into the html output

@swestcott swestcott merged commit c01c78f into swestcott:master Mar 3, 2012

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.