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
-
-
@horus
Each of the 200 plus tests needs an endpoint.
As an example ala HTTP: Endpoint meaning an embedded http server, where you simulate the http server response.
All the tests endpoints are in one...morbid obese... class...
Class looks more or less like this:
function testEndpoint1
....
<helper functions>
....
function testEndpoint200
...
When you open the file, you just ask yourself why. -
@IntrusionCM i see :/
Today I told 3 devs that they either get their shit together or they can pack their things and look for a job.
I can get easily pissed, but it's rather rare for me to get to that point easily.
Now my dear friends, can you guess what they did?
I give you a hint...
They made a test suite validating a network library.
So we have roughly 200 plus lovely splitted tests, neatly put in a directory structure - lovely organization.
(I might have written in the ticket that as a requirement... Cause I know my lil hellspawns)
But as I started looking at some tests, there was always something missing...
Network library...
So we needed to create an endpoint... And handle of course the tests communication with the endpoint *somewhere*.
I'd guess you know already what these mofos did...
Yeah. We have one class.... That handles all tests endpoints... Via different methods... Plus additional methods like utility functions....
The ticket was easy they said.
Me chewing their heads off was easy too.
Jesus Christ, I really doubt sometimes that some devs are able to go to a toilet.
Maybe thats the reason some wear baggy pants - easier to hide the pampers.
*rolls eyes*
rant