Using the equations about screen size as a test scenario for OneNote
Last time I shared a page I used Word and Onenote 2010 equation support to figure out how much larger laptop screen were based on the diagonal measurement of the screens. I mentioned in passing that I would use this to test the implementation of our equation support, and I have. Here's what I am going to do with this work as time goes by.
First, save a copy of the page so I can refer to it from here on out. This is mostly a housekeeping type of item for me, but I've relearned the lesson about making backups often enough that I don't want to overlook it here.
Next, document what I did. I'll add a test case to our database that describes in general how I created the page, and the motivation behind it. What I'm trying to do here is let anyone else who runs the test to do two things:
- Verify what I did to create the page works
- Use her own way of creating the page. Maybe she wants to number each equation more like a proof, or lay out the data in two columns. In short, what I want to do is focus on the scenario: using Office to figure out laptop screen sizes, and not on the one single way I approached the problem. As an example of the variety which could be injected in this test, screen shots of the different laptops could be pasted into the document (and verify the layout still looks as expected after), or use Excel instead of OneNote napkin math to solve the equations.
This second point is the more critical of the two. This is more likely to uncover small design issues that may get overlooked in a step by step type of test approach. For instance, if the test specifies to only use shortcut keys for copy and paste, design or functionality which depends on ribbon buttons or context menus may not be noticed. Or the next tester may want to use OneNote only and avoid the copy/paste from Word. It's up to her to use her own way to complete the scenario.
And as long as the scenario gets completed with no muss and fuss, the scenario gets logged as a pass. If there is muss and fuss, we log a bug and examine what we can do to get the scenario passing.
Questions, comments, concerns and criticisms always welcome,
John