Developers vs Quality Assurance

spawnflaggersays...

For software/hardware designs of any substantial size, there's usually a separate (from the developer) person/team that does Quality Assurance (QA) testing & verification on a design. This has proven (over many decades) to be useful methodology to catch bugs because a developer has pre-conceived notions of how it should work and be used - so they don't think about edge cases. The QA person's job is to find a way to break it, so the final product has less bugs.

In the video above, the developer is on the left - you assumed she made the bucket lid and the pieces that go in the various holes. The QA person is on the right, demonstrating the problem(s) with the implementation. They get bonus points for making the dev's cry.

olyar15said:

I ... Don't get it. Is this supposed to be funny?

qachaossays...

been on both sides
i think this would be more devs vs users. The testers would be trying to create their own holes or trying to push a dump truck through an existing hole

Send this Article to a Friend



Separate multiple emails with a comma (,); limit 5 recipients






Your email has been sent successfully!

Manage this Video in Your Playlists




notify when someone comments
X

This website uses cookies.

This website uses cookies to improve user experience. By using this website you consent to all cookies in accordance with our Privacy Policy.

I agree
  
Learn More