Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@binhex Yeah, we have automated everything over the last year or so. And don't get me wrong, I don't dislike writing tests, just reports for functional tests. Which is unfortunately the one thing that can't be automated... :S
-
@LucaScorpion So if you have automated tests I'd look into getting a report generated off of your CI engine and having it sent to your senior eng. If the tests are properly named and written it should be self explanatory why they failed. e.g. xyz test failed to assert that my actual number of foo was bar.
-
@LucaScorpion You might also want to look at Hamcrest - it has cross language support for a variety of test matchers.
Stupid users gonna be stupid.
Best way to handle exception!
Now where's the rest of your face octocat..
I *hate* it when a senior asks me to write a functional test report. Like I thought we hired functional testers to do that sort of stuff? I'm a programmer, I only write 3 things: code, documentation, and more code. Not freaking reports about how something did not work before, and after this 1-line fix does work. Oh and don't forget to include screenshots and a description of the issue. Arghhh
undefined
report
argh
functional testing