Jul 1, 2011 at 2:38 PM
Edited Jul 27, 2011 at 6:44 PM
I am developing a web-services based system, and am using StoryQ for the "integration" tests of the various pieces of the system.
One thing that might be worthwhile as a diagnostic tool is to be able to deploy the running of the StoryQ tests as part of the general system deployment (with the appropriate configuration changes for pointing the deployment at the right service endpoints).
I was wondering whether anyone has tried this? The way it could work is to execute the StoryQ tests when navigating to a particular web page (or perhaps when hitting a button on a particular web page), and then the standard StoryQ report would be displayed.
The idea would be to have something similar to the FitNesse acceptance tests that are available when you install a new instance of FitNesse (though ours would not be quite so meta).
Pointers and comments appreciated!
Edit: OK, I'm going to try this. Does anyone have any pointers on how to get StoryQ to output HTML programmatically rather than to file?