Why QA People always think to break my Application ?

Gihan Liyanage

:sigh: " Let me break your Application " :(

Gihan Liyanage http://gihansampathliyanage.wordpress.com

OriginalGriff

Because if they don't, the user will. And that's not good at all...

Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)

Argonia

Are you sure you understand the meaning of Quality Assurance?

Microsoft ... the only place where VARIANT_TRUE != true

Gihan Liyanage

Is it breaking Systems ? or finding issues ? :-D

Gihan Liyanage http://gihansampathliyanage.wordpress.com

Gihan Liyanage

Hmm, yeah, But I hate when heard, "Let me break your System" ;)

Gihan Liyanage http://gihansampathliyanage.wordpress.com

Pete OHanlon

Both. If they find a way to break your system, you can be sure that an end user will as well. Accept the fact that they are there to prevent you getting a major kicking from users.

Gihan Liyanage

But any how user will kik us, and also before that, QA people also kik us.. :laugh:

Gihan Liyanage http://gihansampathliyanage.wordpress.com

OriginalGriff

One QA person will kick you if they break it. One thousand users will want to kick you if they break it...

Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)

OriginalGriff

So write better code that they can't break. Because if they can't, there is a much better chance that the users won't either.

Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)

Gihan Liyanage

Hmm. you are right, But its very difficult to have a perfect code always. Don't you think they should change their mind, Because some times they like enemies,

Gihan Liyanage http://gihansampathliyanage.wordpress.com

OriginalGriff

Gihan Liyanage wrote:

Don't you think they should change their mind

No, I think you should change your mind! Why? Simple:

Gihan Liyanage wrote:

its very difficult to have a perfect code always

So someone has to find the problems. And a good tester is one who finds them, not one that doesn't. They are problem solvers, just like developers, but their problem is to work out where you might have got it wrong... If you start giving them software to test that they can;t break, perhaps they will stop assuming it will break when you give it to them? There is an old joke in development: "I'll double your salary when you hand over the code! But I'll halve it for every bug we find..."

Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)

CHill60

QA People also don't usually demand their money back !! Trust me ... a QA Team (even if it is only one person) is a Good Thing. They are not your enemy. They are your friend - sometimes love hurts.

Pete OHanlon

Think of it another way. If you do your job properly, they won't break it.

Mike Hankey

Questionable Attitude (QA) do it just because they love making our lives miserable while giving themselves job security. :)

Have you ever just looked at someone and knew the wheel was turning but the hamster was dead?

TheWebDeveloper

Its called testing

Dan Neely

I feel your pain. A good QA person should be all "MUAHAHAHAHAH!!!!!!!!!! I'm going to smash your application into elventy zillion little pieces. MUAHAHAHAHAH!!!!!!!!!!" Non-motivated testers let lots of bugs into production; and they're never the people who get blamed when the big boss is doing a demo and something blows up in front of the customer.

Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt

Pualee

QA people are 'graded' on how many bugs they find... their job depends on it. So instead of working with you to ensure there are no bugs in the program, they do everything possible to invent problems that they can highlight just before release. It is really a bad situation. I don't have a solution... but umm... that's my opinion. I used to throw in some obvious low liars into my code, so they could write those up and not start questioning arbitrary things like, what happens if the end user is malicious and puts a stick of dynamite under the server room. Will the client gracefully shut down and save work locally until the server comes back up again? What about if the client computer is exploded too... is that redundant as well X|

Deflinek

Pualee wrote:

QA people are 'graded' on how many bugs they find... their job depends on it.

This is just as bad as measuring dev's performance by number of lines of code. Fortunately this is not always the case :)

-- "My software never has bugs. It just develops random features."

BobJanova

That's the developer vs tester game! Developers play by trying to catch mistakes before the tester gets to see them!

Stefan_Lang

Pualee wrote:

Will the client gracefully shut down and save work locally until the server comes back up again?

Of course, and it will automatically call in tech service to clean up the mess and fix it, and serve coffee and donuts to the users while they wait :-D

GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)