News for hackers. Stuff that matters.

valipour

Show HN: generate nicer nunit/specflow test reports using this new XSLT template

https://github.com/mvalipour/specflow-report-templates/tree/master/nunit-dream

Recently I was setting up the reporting for our acceptance tests that I noticed two issues.<p>(1) it's terribly simple in style! (2) it's missing some info such as namespaces (for when you have many folders in which you have tests) and categories.<p>So I edited the existing XSLT and rectified those two issues for me by adding twitter bootstrap style, prismJs syntax highlighting and...

( Read More... | no comments | on HN )
I would say get into the process than the code. this way you can justify your actions better to PMs and managers. People don't like their code to be watched, but they will eventually fix their coding-standard issues each time a red light comes up after they check-in. (styleCop is the tool for .NET community).
I want to agree with @thenerdfiles in that you should make somewhere a better place to work in. It only takes one thing: the potential there that will make you "able" to achieve this goal.

believe me, I worked at a very dynamic, fresh startup for 4 years but with no room given to me for introducing stuff. Moved to a very large organisation but with the potential given to me. I'm very happy now.