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
-
Saying you don't have time for tests is silly. You will spend more time fixing bugs you missed then just writing the tests in the first place.
If your the only one trying to get testing done it probably won't happen. Might be worthwhile doing some passive job searching if you want that kind of thing. -
@unsignedint That's a great tip, thank you! I should just find a nest of bad code like that, it won't be hard. 😄
-
@reaver
I disagree.
Depends on scope.
small to medium scope apps can run without tests and if they are clean enough, you know where to look.
Bigger scope apps, well, it depends but usually tests are good call. -
@DubbaThony I don't necessarily believe 100% code coverage is useful but if you don't do tests you're asking for trouble. I've had to deal with too many bugs due to devs thinking they don't need to test their code. Sometimes bugs come up many years after they wrote their code
You need to decide how far you you take your testing depending on the project but doing no testing on a project is going to bite you in the arse. -
@reaver
Sometimes manually testing is just quicker on smaller projects and doing full tdd on small to medium project, depending on few things maybe shooting self in the knee.
Do you follow test driven development?
The week before project deadline...
Today I read a great article on mutation tests, how to use and why they are important. It looks like a great thing, but...
I have never wrote any unit test in any of my jobs. Nobody in my workplace does that. And now it seems like 100% test coverage is not enough (I remind you, that I have 0%), they all should mutate to check if the quality of unit tests is high.
It seems that I'm left behind. I played with tests in my free time, but it seems the more you write them, the better you get at it, so I should be writing them in my job, where I code most of my time. Not only that, of course, I would also want to ensure that what I'm working on is bug-free.
Still, it will be impossible to introduce unit tests to my project, because they are novelty to the whole team and our deadlines are tight. The other thing is, we are supposed to write minimum viable product, as it is a demo for a client, and every line of code matters. Some might say that we are delusional that after we finish demo we will make things the right way.
Did any one of you have a situation like this? How did you change your boss and team's mind?
rant
mutation
tdd
deadline
test
php