[pytest-dev] [rant] introduction of the new mark api will be deferred further - due to bad rotten spaghetti code

RonnyPfannschmidt opensource at ronnypfannschmidt.de
Wed Sep 6 06:20:02 EDT 2017


Hi everyone,

due pretty much damn bad code quality and complete lack of tests in a 
manageable granularity
i am unable to move many internals to a new api anytime soon (things
just fall apart sprinkled all over the place)

additionally with the current state of tests its feels pretty much
impossible to show what i need in a granular manageable and
comprehensible manner (all the tests in the domain that i need to
tighten/correct are end2end test which means they have zero value now
that i need to change things)

my current main problem is, that i cannot demonstrate the correct
interaction of mark evaluation with nodes in a code amount that could
fit a my head

this is pretty much the results of years of neglecting to write fine
granular tests while also not cleaning up

so the effort to fix this will require weeks of work and likely
introduce accidental internal api breaks en mass as i try to get more
granular tests working.

I feel pretty much helpless  and betrayed in front of such a task, i'm
not sure if i want to even start anymore.

I'm pretty pissed off and angry that the code is at such a state to
begin with.

-- Ronny



More information about the pytest-dev mailing list