|work...@lists.oasis-open.org||May 4, 2009 1:14 am|
|Hanssens Bart||May 4, 2009 4:08 am|
|work...@lists.oasis-open.org||May 4, 2009 5:17 am|
|Dennis E. Hamilton||May 4, 2009 6:52 am|
|Hanssens Bart||May 4, 2009 11:38 pm|
|Dennis E. Hamilton||May 5, 2009 9:19 am|
|Hanssens Bart||May 8, 2009 4:58 am|
|Hanssens Bart||May 11, 2009 7:55 am|
|robe...@us.ibm.com||May 11, 2009 9:24 am|
|Dennis E. Hamilton||Jun 2, 2009 4:01 pm|
|work...@lists.oasis-open.org||Jun 4, 2009 5:49 am|
|Hanssens Bart||Jun 4, 2009 6:07 am|
|Dennis E. Hamilton||Jun 4, 2009 10:17 am|
|robe...@us.ibm.com||Jun 4, 2009 11:43 am|
|Hanssens Bart||Jun 4, 2009 1:24 pm|
|work...@lists.oasis-open.org||Jun 5, 2009 2:04 pm|
|work...@lists.oasis-open.org||Jun 8, 2009 4:44 am|
|work...@lists.oasis-open.org||Jun 8, 2009 5:29 am|
|Hanssens Bart||Jun 8, 2009 5:40 am|
|work...@lists.oasis-open.org||Jun 9, 2009 1:19 pm|
|Subject:||RE: [oic] The Hague expense sheet scenario, continued|
|From:||Hanssens Bart (Bart...@fedict.be)|
|Date:||Jun 4, 2009 1:24:17 pm|
"Test point" in the sense of a specific measurement point in an electronic circuit is something I think of like that. In our case, the test point definition would include the threshhold condition.
"Test point" sounds good
It appears that we are asking that an ODF document of a particular nature (more or less) be created, but the tester has to know how to interact with the application in a way that achieves that result. I guess we are going to learn how to specify what the outcome should be in a way where a test developer would have to identify how that outcome is achievable, or not, with their product.
Correct. I'm focusing on office suites, and I'm trying to find a balance between being too implementation-specific ("press F11") and too "clueless" ("here's the raw XML, now you figure out how to recreate it")
In fact (I think I mentioned this before), a developer could create scripts for their favorite office suite. IIRC, the KOffice guys already have some scripts to create test documents for conformance / regression testing.
For example, how is it to be determined that the document conforms to ODF 1.1 (and that it is the intention to create an ODF 1.1 document) ?
Also, how are satisfaction of layout measures to be determined ? I assume the document must be rendered (on a printer?) in this case.
Rendering is challenging indeed :-) So the PDF I've added is merely a suggestion, not "the" correct answer: how "bold" is "Bold" ? I have no idea. Maybe the margin is 1.999cm instead of 2.0, that's probably good enough. But if I see a red border while the XML says it's black, that's obviously wrong...
For example, what exactly does "Apply 'oic-page' to current page" mean? What is the intended outcome.
Well, maybe it is possible in implementation X to define a page style (by clicking around or using a wizzard, whatever), but X might fail in actually using / applying it.
For example, test scenario step 1.1 assumes there is a UI provision for independently defining and naming page styles. That's a big item with tons of dependencies (A4, portrait, metric dimensions, and UI language and locality-specific behavior).
Hmmz yes, once again I'm trying to find the right balance between a scenario with truck loads of explicitly defined post- en pre-conditions (cumbersome to write and not very encouraging for potential testers) or being too vague...
--------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php