Ranter
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
Comments
-
C0D4681385yTest00[n].class.method.scenarioIAmTesting.
When you run all tests and something fails, I don't have to go read the test class to work out what's failed. -
@C0D4 Interesting !
Maybe I’ll do something similar.
Right now if a test fails, I just need to double click on it to see description.
Here is an example -
vicary4815yEasy, spam the issue tracker with features and regressions. Now name the tests with only issue IDs.
-
@spongessuck I find having method being the first in line more manageable. If I'm testing a class with multiple methods, seeing method first adds a nice additional grouping for all the cases
Related Rants
-
bananaerror3We've had a bunch of flaky tests in our repo for a while now that no one could be bothered to fix; we'd just r...
-
m1442So today, again, I discovered the importance of unitests. I was solving this performance issue, in which we ha...
-
netikras2> Run 'All Tests' with Coverage No tests failing Coverage >95% Hell yeah! I've tasted TDD and I don't want t...
Do you guys take time to properly name your Unit tests ?
I kinda feel it's waste of time. (There are comments with description of the test tho)
question
unittests