If i met one i will try to explain the risks involved in delivering a software with a bug. The system may crash and the data in the databse may be corrupted, resulting in the heavy losses to the company. Also i will tell him how much reqork will be needed later on if some problem arises resulting in the drastic increase in the software cost. Also the customer trust will get hampered.
geetanjali
Sep 1st, 2005
i will explain if the product will release without testing it can cause loose of quality, customer relaibilty, loss of reputation, and even loss of life, in a normal IT company there are 1:1 tester to developer, but in NASA there are 7:1 tester to developer, because it involve high risk of lifes, and country reputation... it is all because of testing we relay on products which involve loss of life
sriram
Oct 15th, 2005
geetanjali Wrote: i will explain if the product will release without testing it can cause loose of quality, customer relaibilty, loss of reputation, and even loss of life, in a normal IT company there are 1:1 tester to developer, but in NASA there are 7:1 tester to developer, because it involve high risk of lifes, and country reputation... it is all because of testing we relay on products which involve loss of life
haricharan reddy
Apr 9th, 2006
thanks geeta.as it was a perfect anser to the person who needs to be unnderstand that how imporant the testing is .........
Actually, Its quite project specific, we cannot talk about the life hazards when we are testing a stapler.. can we? That would be quite generic..
Let be particular to Software testing, which mostly doesnt have any life hazards.. we have to put it in such a way the person understands the importance of testing from generic facts.. rather than examples.. 'If u talk about an example like NASA project, obviously the clients reaction wud be 'I dont run a NASA out here, I dont want to spend more'.. Isnt that true? 1. Software testing can compensate for the fact that the software development process does not identify the true needs of the user, and thus test to determine whether or not the user’s needs have been met regardless of the specifications.
2. Finding defects early in the software development process when they can be corrected at significantly less cost than detected later in the software development process.
3. Removing defects of all types prior to software going into a production state when it is significantly cheaper than during operation.
4. Identifying weaknesses in the software development process so that those processes
can be improved and thus mature the software development process. Mature processes produce software more effectively and efficiently.
Nobody is perfect. A good developer doesn't make many mistakes, but they still make mistakes. If they believe that they can do all of their own testing, they are like a doctor who operates on himself, a writer who edits his own writing. There will always be a first test; the only question is, do you want an important customer watching while it is performed?
A cynical reason for testing is that a good tester is paid much less than a good developer. I am a good tester, and I am a very poor developer. I make lots of bugs when I write code. Testers are supposed to be cunning and evil little men, who live to embarrass their betters (well, better paid at least)
In 1994 disney world introduced lion king game in summer vacation, the publicity of the game was done very well, when the product was launched, the product was failure, games worked only on specific system like (windows 98, xp, linux) b'cos they failed to do system testing, the cost of replacement was very high. So testing is very important.
Initially, Depending upon on individual interests people choose their fields,
But if they do not believe in testing then i would ask them to go through the book "Lessons Learned in S/W Testing" by CEM KANER.
And also i would ask them why are they not interested (rather than convinicing them with my ideas), which gives me a clear idea of what type ok knowledge, why do they think Testing is not important etc.So, depending upon the view i will explain them with an answer.
We can even give example of Vehicles like Car, if new Car has been launched in the market then it is supposed to be test first, before Customer using it , parts like breaks, tyre, horn headlight are working fine or not in day and night time as well, as it involves the risk of life of a customer, which is indirectly related to our company's status, name, fame, reputation and so on.
Did u ever have to deal with someone who doesn't believe in testing? What did u do?