• frits (unregistered)

    frits

  • Architester (unregistered)

    Yesterday I was refactoring a application that had been running well. After my efforts, I went to run the unit tests. To my dismay, those tests were meaningless. "Who designed these?", my mind screamed. Oh yeah: me. Time is a necessity. Make it.

  • dkf (nodebb)

    I feel very sorry for that QA Engineer, and I suspect this story is really very lightly anonymised indeed.

  • Gargravarr (unregistered)

    There is literally nothing more dangerous than a CTO with an industry journal.

  • Anon (unregistered)

    Why is the punch line about the average time for a developer to leave? The majority of the article focuses on what a nightmare this is for the QA Engineer and the IT Manager. For all we know, the developers are perfectly happy.

  • DocMonster (unregistered) in reply to Gargravarr

    Especially when they aren't technical themselves. Nothing worse than someone who thinks they know computers dictating to actual professionals how to do their jobs and unwilling to listen to criticism. Essentially if Michael Scott (of The Office) was head of IT.

  • axusgrad (unregistered)

    Weren't the industry journal recommendations actually correct in this article? It seemed more a problem with how CTO director applied them, than DTAP/staging being a bad idea.

  • Herby (unregistered)

    I was waiting for some long latent bug to destroy the business. I suspect that eventually it will happen, only a matter of time.

  • OlegYch (unregistered)

    been there more branches=more merges=more bugs nothing like a new QA process to kill any development progress

  • OlegYch (unregistered)

    why don't comments here maintain line breaks?

  • blakey rat (unregistered)

    I'm just doing it for attention, but no one likes me. I don't understand why. I'd start my own version of this site, but I just can't figure out how. I'm so lonely...

  • HDS (unregistered)

    @axusgrad : I don't think they are a problem at all. But most such systems have dependencies. E.g. you cannot do CI without source control (or rather: yhou should'nt try it). Without satisfying those dependencies, you are just creating an abomination.

  • Gargravarr (unregistered) in reply to axusgrad

    Yep, that's exactly it. The fact that the CTO dictated his interpretation of those journals to the people actually using them, and then enforcing them (I bet the dev team came into work on Monday morning to find an email instructing them they now have to use 8 different VMs each) without actually taking the time to understand how they were actually going to use them causes a pot o' WTF like this.

    Kudos to the QA person for not throwing in the towel, but she could see how quick this house of cards was going to turn into a prison. With this kind of thoughtless steamrollering by the CTO, sounds like the QA process becomes more damaging than bad code, and would wind up with the devs (at least partially) accountable for not getting the fix into production. I can see the devs going elsewhere after a while.

  • Dieter H (unregistered)

    Having all your tickets sent back to you without an explanation and without a bug would do it.

  • jay (unregistered)

    "This article sucks. This writer sucks. This theme sucks. This website sucks." I give you permission to stop visiting this site. Problem solved.

  • urkerab (nodebb) in reply to OlegYch

    why don't comments here maintain line breaks?

    They're written in MarkDown, so you have to follow its rules, except there's no preview, so good luck!

Leave a comment on “Test Overflow”

Log In or post as a guest

Replying to comment #:

« Return to Article