Improving the xunit reporting from freshen

dexterous commented 13 years ago

We've been using freshen-0.2 to write our first suite of acceptance tests for the last three months at work and are finding it to be very helpful.

The one piece missing, however, was that once we hooked our tests up to a CI server and enabled --with-xunit, the xunit output wasn't very helpful. All the features.scenarios were reported as FreshenTestCase.runTest.

So, I took it upon myself to add in the support to have feature and scenario names mapped to test class and method names appropriately so that when the CI server reports a failure/error, we know exactly where to look.

This pull request is essentially comprised of 4 chunks of changes, viz:

[Vayana@3f6c0cff] is just a little cleanup before I started
[Vayana@23e11fdd, Vayana@75b4949c, Vayana@94251d06, Vayana@d5845ab0, Vayana@f96c13e] These are the actual feature.
[Vayana@ffa88120, Vayana@26ffc023] This was just my OCD; I just needed to reduce the test execution down to a single step. We can now run all the tests with nosetest --with-freshen tests/
[Vayana@5dd40720] This was a weird quirk in python's class loading/initialization that I noticed. I was building on python 2.6.6 but my CI server still had python 2.6.5 and super apparently wasn't all that super in 2.6.5.

Hope you find these changes good enough to pull in. We plan to invest in freshen for the foreseeable future and would love to see it grow.

dexterous commented 13 years ago

Not sure if @jerico-dev gets notified of these automatically, hence putting in a quick mention.

ghost commented 13 years ago

Hi dexterous! Yes, I'm getting (and reading) these messages. I'd rather prefer rlisagor to pull, though, as he's the main author of the project. Thanks for your contribution, btw. Sounds like a very useful change, not only for those who use CI but also for better output in PyDev and other tools that have test integration.

dexterous commented 13 years ago

Heh, although that's not what I started out with! :P

I noticed @rlisagor's reply on #14 later; but reasoned that subclassing would help other tools that introspect, much like you did. PyDev should definitely benefit from this as well as, I guess, other plugins like cover and prof.

I'm glad you liked the change and hope we can pull it in soon. I've deployed the latest code from my repo onto our CI server for now, but would love to go back to pulling the package from pypi.

dexterous commented 13 years ago

Just in case you noticed something weird- I transferred ownership of my original fork to the github organization we created for our work repos and then forked from there. That's why the source of the changes is now Vayana@master and not dexterous@master, even though they both point to the same tree.

rlisagor / freshen

Improving the xunit reporting from freshen #35