I'm currently doing development and tests for a Windows Desktop Application that plays together with some PLCs. One of my main tasks is to perform Functional Tests on a System Level for each Alpha/Beta version.
There's a Test Document (MS Word) that defines the test cases and has an Accpeted/Not Accepted mark for each test case. When encountering errors, a screenshot is taken and put together with some short description into the Test Document.
All other deviations/observations that are not related to the Functional Tests are put into a separate Word Doc.
At the end of the tests, I'm creating some overview spreadsheet that lists all results and is a base for discussion.
Of course, every now and then some tests will fail. Some bugs are so huge that they'd be blocking the release and require a bugfix that results in a new delivery that results in a new build for the possible release. This build will then be retested. The failed test cases are to be repeated and possible other test cases also, depending on the impact of the change.
The common procedure results in creating a new copy of the (empty) test document and executing the test cases. Of course, most of the other cases won't be executed and will have no result in their checkbox. This doesn't look nice and is also not easy to get an overview (e.g. if you have two or more retest documents).
Sometimes we're also creating a Test Plan (Word) that defines a subset of the Test Cases to be executed.
Handling these documents is a bit tricky:
no linkage from overview to failed testcase (manual search)
test case document rather long (~60 pages), keeping an overview hard
for each retest of a failed build, a new copy of the word document is created
Recording test results and reviewing them is hard for me
Do you have any recommendations for handling the documents, recording results and decisions and versioning the documents on a per release/build base? How are you doing it? Examples welcome!
BTW: The toolset (MS Office) can't be changed (boss sez so).
Thanks a lot, Alex