1407
Tests are code too (lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
[-] TheSlad@sh.itjust.works 6 points 1 year ago

Just dont write tests lol, that's what QA is for.

[-] DragonTypeWyvern@literature.cafe 17 points 1 year ago* (last edited 1 year ago)

This guy's a business major.

(He just fired half of QA)

[-] maniclucky@lemmy.world 6 points 1 year ago

He works for Bungie?

[-] TheSlad@sh.itjust.works 2 points 1 year ago

Hell no! I love QA, they find all the bugs I make since I dont bother with unit tests. I think every dev team should have 1:1 devs to testers.

[-] folkrav@lemmy.ca 2 points 1 year ago

Every time someone needs to change anything nontrivial, like a large feature or a refactor they just code away blindly, hope it doesn't make anything explode, and then wait for QA to pat them on the back or raise any potential bug? Does this mean your QA team makes a full product sweep for every single feature that gets merged? If that's the case, you'd need more than 1 QA per developer. If not, you're now stuck debugging blindly too, not knowing when the thing broke?

I worked with a team like yours at one point, and it was hell 😬 Each new feature is like poking away at a black box hoping it doesn't explode...

[-] TheSlad@sh.itjust.works 7 points 1 year ago

On the internet, nobody knows when you're being sarcastic.

[-] folkrav@lemmy.ca 1 points 1 year ago
[-] dan@upvote.au 1 points 1 year ago

What do you do when QA finds a bug though? Just fix it without writing a test to ensure it doesn't happen again?

[-] TheSlad@sh.itjust.works 3 points 1 year ago

Fix it then hire another QA

this post was submitted on 02 Nov 2023
1407 points (100.0% liked)

Programmer Humor

32563 readers
425 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS