SOFTWARE TESTING

I have got a chance to work at previous www.aitecs.com, now Moog as software tester for five months. Worked with software for infusion pumps. It was a great experience for me as a tester and want to share with some impressions. 1. Same rules. The first lesson I learned that same rules for testing apply everywhere. Embedded software frightened a little. I thought it should be very different, and I do not know how to test. I learned that all the rules that apply to web site test, application testing, also apply to embedded software testing. Testing the software of infusion pump got me back to pure testing. Analyzing the new functionality, applying mixed of black and some white box methods, searching through requirements made me feel real tester. 2. Validation. For me verification and validation used to be only theoretical expressions. And not clear enough what they mean. I have been testing a few IT projects and mainly worked with verification. Used to verify the software is made accord...

The Do’s: 1. Identify test cases for each module 2. Write test cases in each executable step. 3. Design more functional test cases. 4. Clearly identify the expected results for each test case 5. Design the test cases for workflow so that the test cases follow a sequence in the web application during testing. For example for mail applications say yahoo, it has to start with a registration process for new users, then signing up, composing mail, sending mail etc. 6. Security is high priority in web testing. Hence document enough test cases related to application security. 7. Develop a trace ability matrix to understand the test case coverage with the requirements just a paste form the article. What i already do - 1, 2, 4. 3 - do not understand what the auhtor means. long worflow is rather rear - 5, 6- seldom do security testing - only authorization and roles. 7 would be a good practise - but that is a must only for bigger projects. missed one requirement in test cases set in a ...