Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Like 0.01 - 0.5 seconds each, depending on object creation.
My coworkers’ normal:
2-18 seconds each, depending on how bad they screwed up / triplicated object creation.
The entire test suite at work:
4+ days on an i9 MacBook Pro, or 1.5 hours on a large EC2 instance (with specs running massively parallel)
C0D4695162yTypically around 10-20 seconds each.
There's a lot of mock data most of the time to be created.
Around 2 hours to get through then all as they have to run synchronously 😕
I do enjoy getting to the end and having a failure appear 😵💫🔫
However long I spend in the lab
G4nin01382yTests? What are these test? Our company don't do those. Well we have like five automatic tests that check that the product doesn't crash on startup. And then like three physical testers that are supposed to verify every buggfix and new releases. They are perhaps lke 8months behind on testing so we are basicly just sending untested releases.
But we are operating a quality first buisness according to our website
ars134072yAbout 20 seconds for all Unit tests per project so far.
Levminer1172y0 seconds. I don't write tests.
I type 'make' and it all goes downhill from there
I work on a big site, with mocha end-to-end tests and as they run they do several thousand checks (but many are just done by looping through different options and checking the same thing still works )
But it doesn't matter much cause we rarely run the entire suite locally, we mostly just run them on a Buildserver when a PR is updated.