Comments on: Windmill Reporting

By: mikeal

mikeal — Mon, 29 Dec 2008 20:56:57 +0000

So functest (the framework that windmill embeds) traverses up all your test modules. Any directory with init.py is a valid test module. You can use the directory/module hierarchy to separate out different test functionality. If you're writing a reporter class you probably want it to work with all your tests so you would want to stick it at the top of the module hierarchy.

But regardless of where you put the class, if it's in a test module that gets run it will be registered when the module is loaded. So if you put it in the folder your test is in, it should work, if not then something is wrong.

If something seems very off you can come on to IRC in #windmill on irc.freenode.net and someone should be around to help you debug it. Although right now during the holidays people seem to have been away a bit more.

By: cyril

cyril — Mon, 29 Dec 2008 20:48:25 +0000

Hi,

I am not fluent at all in python so I don t know where I should put this init.py

I try putting it in the same folder than my test but it did not work.

The response is probably here "you add a simple class to the highest level init.py with your report code" but I don t understand the meaning of this sentence.

By: Zero to Continuous Integration with Windmill | Windmill Testing Framework

Zero to Continuous Integration with Windmill | Windmill Testing Framework — Fri, 19 Sep 2008 09:09:57 +0000

[...] You can also read a great entry about adding reporting to your tests on Mikeal Rogers blog, here. [...]

By: Zero to Continuous Integration with Windmill | Adam Christian

Zero to Continuous Integration with Windmill | Adam Christian — Fri, 19 Sep 2008 06:30:13 +0000

[...] You can also read a great entry about adding reporting to your tests on Mikeal Rogers blog, here. [...]

By: JUnit Compatible Reporting for Windmill | Windmill Testing Framework

JUnit Compatible Reporting for Windmill | Windmill Testing Framework — Fri, 12 Sep 2008 23:17:34 +0000

[...] from functest import reports from datetime import datetime class JUnitReport(reports.FunctestReportInterface): def summary(self, test_list, totals_dict, stdout_capture): total_sec = 0 for entry in test_list: time_delta = entry.endtime - entry.starttime total_sec += time_delta.seconds out = ‘n’ out += ‘n’ for entry in test_list: if entry.result is not True: entry_time = entry.endtime - entry.starttime out += ‘n’ out += ‘n’ #out += str(stdout_capture) #until I can figure out how to get the traceback out += ‘There was an error in ‘+ entry.name out += ‘nn’ out += ” else: entry_time = entry.endtime - entry.starttime out += ‘n’ out += ‘nn’ out += ” f=open(’continuous_test.log’,'w’) f.write(out); f.close() reports.register_reporter(JUnitReport()) Happy automating! UPDATE: Mikeal has posted some additions/revisions to this code sample, here. [...]

By: Windmill Reporting | Windmill Testing Framework

Windmill Reporting | Windmill Testing Framework — Fri, 12 Sep 2008 23:14:15 +0000

[...] UPDATE: Mikeal has posted some additions/revisions to this code sample, here. [...]