32

Why is there so much hate against QA in general??

I read tons of rants about how bad testers are... and as a dev who does a lot of QA work, IT SUCKS!

We (devs) have to accept that are work needs to be tested! Otherwise we want be successful with our products.

BUT the testers need to know the development business! They should be trained at the same level as the devs are.

BECAUSE if the mug on my desk is smarter than the tester it is not going to work!
If the tester has full access to all the technologies, environments and tools (and are capable of using it) he has the ability to HELP!

I THINK that testing should be more than just follow predefined steps and let a random tool generate a bugreport.

I am sure that some of you are lucky enough to work with highly skilled testers so please let them help

Comments
  • 5
    I agree with you bro, but in my case I faced a tester asking: Error 404, Not Found. if its caused by the mobile app or from the server when the error message clearly says in the title: Server Response

    They need to be trained, my code aint the best but to detect the problem in my a code a trained personnel must check and not some random guy
  • 4
    Testers are not bad... I just have to blame it on someone when they send me the ticket back with feedback.
  • 2
    Maybe because they create all those bugs...? Duh!
  • 3
    Couldn't agree more. Good QA takes skilled testers. Not all companies realize the importance of testing though, so in many cases anything above component testing is performed by the users themselves, skilled in their trade but useless when it comes to testing software.
  • 0
    All software if not tested is bug-free. It takes a tester to free software from bugs and be able to prove it.
  • 5
    @mt3o I could not disagree more.
    1. No software is bug free.
    2. No tester can ever prove that a tool is bug free.
    3. A tester should only prove the existence of bugs
  • 1
    @boom they don't create the bugs they just recognize their symptoms...
  • 2
    @gitpush yes I work in the same team with some of 'those'. They should not be allowed to do the job... they need IT Knowledge!
  • 1
  • 2
    @needToRoll they need to be put aside until they are capable of doing their job. It is management (and HR) fault for putting the wrong people with on board. They put newbie with people that know what the fuck they are doing, and guess what, delays and slow work is the result because of the need to act as baby sitters and/or teachers yet finish coding
  • 1
    I feel like the one that writes the code should do the testing. Keep everyone honest with a code coverage tool. Less to get fucked up that way
  • 1
    User experiences are like jokes. If you to explain it, then it's bad!

    You should always write your own unit and integration tests.

    If QA peeps are trained devs, then they won't use the software like a normal user. QA should be staffed with normal Joe blows. I always get my 60 yo dad, who worked construction, to tell me what he thinks of my UI.
  • 0
    @boom Let's agree on the premise that the bugs are coming from incorrect code or specs... last time I checked neither was written by QA...
  • 1
    @aqparks UAT and experience should be tested by a normal user... everything else by a professional IMO
  • 0
    @dev0urer That does not count for all tests... you will never find bugs that are based on something you misunderstood...
  • 0
    I was been sarcastic. Take it easy.. @needToRoll
  • 0
    @boom nice to know that you are... but if had this argument for real
  • 1
    @dev0urer Code coverage tools lead to people testing until they get 100% code coverage, which is nothing at all like 100% use case coverage.
Add Comment