New answers tagged documentation
Given the mandate to use Microsoft Office, I'd look at using spreadsheets to manage the test execution, working something like this: The master list of all test cases for the project is either a Word document or an Excel spreadsheet, linked from the Test Plan. Each test run can be either a separate spreadsheet or a worksheet within a single spreadsheet, ...
This is a huge question! I've worked at similar places where they want a QA team to work without the QA tools like bug-tracking software, for example. If you're being forced to use Microsoft Office, then it might be worth splitting up the document, so rather than tracking the defects in one test document per iteration, you could literally have one page per ...
Even i feel external documentation is a burden, better way will be distributing page elements meaningfully in into different smaller classes with comments and apt names.
Top 50 recent answers are included