I am looking for some new ideas on testing hand held scanners with the ability to input data with a key pad (written is DOS). Most of the test plans that are currently available to me have a basic format of "Test Condition" and "expected result" and "pass-fail" the steps are laid out telling the user exactly what to do and then the screen shot is in the expected result field. The plans are long and tedious. I need to figure out a way to make them more efficient and easier to get through. Any ideas on test plan templates and designing testplans that are easy to update would be helpful.
The futuristic vision is what you need, right ? I suggest take help of simulators and robotics. They will punch input data, would update the plans, test case results and you will be happy to get everything served on your table.
You may visit Japan where lot of prototyping is going on in areas like robotics, artificil vision, pattern recognition.
Sounds to me that you are describing a test case, as opposed to a test plan.
Are you in a regulated (FDA) environment? Do you want your tests to be repeatable - by someone other than yourself?
I would suggest that at a minimum your test case should state:
1. Functionality (or requirement) you are testing.
2. What the expected result is.
3. What the actual result is. (Pass or Fail)
Sometimes you can combine 1 & 2 like so - "Verify that by entering a proper User Name & Password, the application opens."
Functionality and Expected Result in one sentence.
The current test case template we are utilizing is:
1. Step #
2. Test Action (functionality)
3. Expected Results
4. Actual Results (handwritten in during execution)
5. Pass or Fail check boxes
6. Tester Initials and Date
We also print out screen shots for every step, if applicable, as we are in a regulated environment, and as such require hard copy proof.
It all depends on what your company requires as proof of testing. If you do a search of these forums, you will find that many do not agree with this "old fashioned" approach, and advocate a paperless testing system.
Good luck with your test effort. Let us know what approach you decide is best for your project!
the company I'm working for IS big on testing proof because if you don't keep a record of what you tested and how it will come back and bite you. I like the idea of doing actual results because often I'm trying to squish that in and around my expected results.
As far as ideas, I'm not looking for a miracle or robotics....things move way too slow here for that to happen. However they are doing some automated testing but it is for regression testing because they haven't come up with a way to test the application that is currently being evaluated. The automated test verifies that the old version can be used in the new environnment and that things won't break on the scanner.
I'm looking for ideas to update my test plans or test cases (not sure what the difference is) so that they are easier to maintain and easier to do without feeling like I could fall asleep.
No need to reinvent the wheel. There are companies out there that provide test tools for scanners, cell phones, remote controls, and calculators for use in final production test. They also provide hardware necessary to interface to those devices. Result logging is included. And they undoubtedly have integrated solutions for test plans and testcase layout.