[Replying also to the list.]
2010/9/17 Finn Neuik <fin...@gmail.com>:
> I think a listener would be pretty generic - currently we're using XSLT to
> transform the test output into the results which TeamCity requires but
> looking at the listeners we can do everything using those instead. This
> would also have the advantage that I can remove the pause I need before
> doing the transform whilst waiting for the report to finishing spooling.
> I've come across a couple of issues - first of all the test results are only
> getting reported at the end of the test run rather than in realtime. I think
> is probably just something I'm missing in what TeamCity requires so should
> be easy enough to solve.
Listeners allow real time updates so this sounds like an issue with
TeamCity integration. Hope you can resolve it.
> The other is that some of our test names have characters which cannot be
> output to the windows console using the straight print statement due to code
> page issues, so I'll need to transform the output I guess.
Do you necessarily need to go through the console? Could you use files
instead? Or does TeamCity have an API you could you directly from the
listener? That would probably be the best solution.
> I'll try and solve these issues next week and share the results then.
Cool! If you come up with something generic, are you interested in
writing a wiki page about TeamCity integration? If there's some
generic code, starting a separate project might be even better option.
> Finn - the world can't have enough Finns I think!
Must agree with that! =)
Agile Tester/Developer/Consultant :: http://eliga.fi
Lead Developer of Robot Framework :: http://robotframework.org