Appeal 2007-1416
Application 09/881,791
text into logical statements. In some embodiments, discussed
subsequently, each logical statement is then examiner by type to
indicate if it is a testable assertion.” (Specification 19, ll. 20-22).
Specifications are first divided by context, and then by sentence.
(Specification 22, ll. 6, 16). It is then decided whether a sentence is a
testable assertion, by various means, including natural language
processing, keywords or other techniques. (Specification 22, l. 21 ff).
Appellants continue, “The discovered assertions are added to an
assertion result set, in operation 512.” (Specification 21, ll. 30-31).
2. Pavela teaches an automated system and method for testing software
programs where the system test designer is relieved from writing test
programs from scratch. (Col. 1, line 60). A script file, sometimes
called a source file #318, is constructed in a structured way from a
template #302 (see Fig. 4). The source file is used to generate test
cases, test plans and other testing tools. (Col 6. l. 51+, Figure 3). The
template for the source file has different sections, each commencing
with a header. (Figure 4, those lines beginning with :h4). Some
sections of the source file have just lines of descriptive text, such as
the Objectives section #402. (Figure 5, #502). Other sections have an
ordered list (starting with :ol) of procedures. (Figure 6, #602 to
#616). The lines in this section contain commands (#602A-#616A),
and parameters for guiding the execution of the respective command
(#602B-616B). These lines are called tags and tag parameters. (Col.
6, line 4). They are used to generate test plans in conversational
language using script macros. (Col. 6, l. 34). They are also scanned
to identify system elements #132 that are tested by the test case. (Col.
5
Page: Previous 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Next
Last modified: September 9, 2013