Domain Testing: Divide and Conquer - Testing Education

APPENDIX A
In this analysis, I used online help and empirical observation of the product. I had no access to a specification or any other
authoritative source of information about the domains. I recommend that we get the programmer/designer/product manager to review
this.
I included domain risks in this outline because it seemed more natural to do that than to create a separate table. Notice that many of the
domain-defining risks I have identified are vague in some way (e.g. no identification of the specific nature of a potential failure). They
are vague because I don’t have detailed technical information or experiences with this product that would allow me to be any more
specific.
This document is crudely formatted because I find that more elaborate formatting lowers the probability that I will update it as new
information emerges. Normally, I would maintain this in a text editor with no formatting at all beyond indents and line breaks.
"???" denotes an issure or question to be investigated further.
Input Variables
Slides Sized For
Type: Enumerated
Default: On-screen Show
Values: [??? These are the values are observed in the product; not corroborated by information in any spec or help file.]
(presets)
On-screen Show [??? Is there a functional difference between this and Letter?)
Letter Paper (8.5x11 in)
Ledger Paper (11x17 in)