embedded 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 according to requirements and conforms to the analysis documents. The certified medical device required to prepare software validation reports. Validation report states that users may use the software, it is safe to use and does what is intended to do. Every small project of new or changed functionality should end with validation report.

3. Higher regression testing. I called it higher with intention to show more wise way to do the regression testing. In my experience regression testing would mean test the main functions of the product, having checklist in my head. OK, sometimes short word document. What I discovered to be a great help – testing procedures. That is a list of test cases, created using software requirements and grouped according to logical division of functionality. In any need of regression testing, the tester evaluates the scope of it, selects certain procedures and follows them step by step.

4. I love pair testing. Two eyes see a lot, but four eyes have a chance to see more. Usually I would find an ‘interesting’ functionality and show it to a developer. He would start thinking creatively, linking things together, and suggesting other issues to check. The results sometimes were great. Also it was really cool just to express loudly opinion about certain function, button, message etc of the program and hear the person thinking. Those dialogs usually end with new issues in test track system, and I believe, a chance for improved quality.

Comments

Unknown said…
I recently came across your blog and have been reading along. I thought I would leave my first comment. I don't know what to say except that I have enjoyed reading. Nice blog. I will keep visiting this blog very often.
Software Testing Tools
JTAG said…
I would like to exchange links with you. Please see my blog: http://boundaryscan.blogspot.com

This blog provides a brief overview of the boundary-scan architecture and the new technology trends that make using boundary-scan essential for dramatically reducing development and production costs. I also describe the various uses of boundary-scan and its application.
I never got such kind of work in my career but wanted to do so. Its great to read your experience about this kind of testing. Hope someday I will also do get a chance too.
ipad 3 said…
Thanks for sharing this great information. I really enjoyed reading about this,and I'm going to let other people know about this as well.
kaviya said…
Thank you for the info. It sounds pretty user friendly. I guess I’ll pick one up for fun.




Embedded Software Development
custom software said…
nicely written...quite detailed.. helpful both in terms of knowledge and use....
Lot of useful points are there. Its really keeps me updated.
Vee Eee Technologies
PikeTec said…
may look at embedded software test automation tool TPT http://www.piketec.com/products/tpt.php
kaareem9 said…
The certified medical device required to prepare software validation reports. Validation report states that users may use the software, it is safe to use and does what is intended to do.

automateandvalidate
Bikram said…
Much higher regression testing. I also known as it much higher with intention to show even more wise method to do the regression testing. Within my experience regression testing would indicate test the main functions of this product, having checklist within my head. OK, sometimes brief word document. Precisely what I discovered to become a great help - testing treatments. Who is a list of test cases, created utilizing software specifications and also grouped based on logical unit of performance. In any need of regression testing, the tester evaluates the range of it, selects certain procedures and also applies them thorough. automateandvalidate

Popular posts from this blog

Ieškomas testuotojas: ASW

Retrofitting testing - what is it?

Security testing