Software Testing and Quality Assurance

by Hung Nguyen

According to Associate Press (February 9, 2010, Yuri Kageyama, AP Business Writer), "Toyota is recalling 437,000 Prius and other hybrid vehicles worldwide to fix brake problem." Toyota is the world’s largest automaker with impeccable quality reputation up to now.

As it turns out, the cause of the problem is a bug in the software that controls the brake system. "There have been about 200 complaints in Japan and the U.S. about a delay when the brakes in the Prius were pressed in cold conditions and on some bumpy roads. The delay doesn’t indicate a brake failure. The company says the problem can be fixed in 40 minutes with new software that oversees the controls of the antilock brakes."...

by Michael Hackett

Talking about Testing is like the story of blind men describing an elephant. Each description depends on what part they touch. Software testing can be such a universally different job depending on so many things, what is common or normal is moot.

I don’t believe in a best practice. The motivation and goals of testing vary from project to project. For example, testing a web application for an commerce site is different than testing software needing FDA regulatory compliance is different than testing firmware for cars is different than testing corporate accounting software is different than testing a printer driver. To say there is one best practice for testing is ridiculous. But what are the common practices? What do most people do? How much regression testing is commonly automated?...

Enter to win a free iTouch and share your opinion with LogiGear's online survey!>>>

by Michael Hackett

The V-Model for Software Development specifies 4 kinds of testing:

• Unit Testing
• Integration Testing
• System Testing
• Acceptance Testing

What I’m finding is that of those only the Unit Testing is clear to me. The other kinds maybe good phases in a project, but for test design it doesn’t help much. It is hard to say which tests should go in a system test, an integration test or an acceptance test...

Enter to win a free iTouch and share your opinion with LogiGear's online survey!>>>

by Hans Buwalda

The V-Model for Software Development specifies 4 kinds of testing:

• Unit Testing
• Integration Testing
• System Testing
• Acceptance Testing

What I’m finding is that of those only the Unit Testing is clear to me. The other kinds maybe good phases in a project, but for test design it doesn’t help much. It is hard to say which tests should go in a system test, an integration test or an acceptance test...

Enter to win a free iTouch and share your opinion with LogiGear's online survey!>>>