(Moving this topic to a new thread so that the main issue I'm having with the other one doesn't get overlooked!)
Hi Peter, <OffTopic> Interestingly enough we are planning on pushing results back from the cucumber plugin to another system – so I wonder if there is some commonality that the plugin should expose rather than requiring many plugins parsing the same files. </OffTopic> /James Hi James, I think there may be some benefit. If we could structure it so that the user wouldn't need to enter cucumber configuration related settings more than once, that would be nice. Setting up the gherkin parser within a common codebase would save some code. In my case, I implemented a gherkin callback to generate HP Quality Center specific objects that worked pretty well. The formatter / reporter push based parsing mechanism is fairly easy to use so I'm not sure having the common codebase deliver an additional API for the test cases would be to beneficial. Any particular benefits that you're thinking of? Pete -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
