Data-driven testing without data configuration
View Patent ↗In software development, the provision of a testing tool which includes a method for defining a data source dynamically during an execution run, instead of programming such a definition within test script.
1. A method of testing software, said method comprising:
running a test of software, via executing a test script;
dynamically creating a verification point during said running of the test;
wherein said creating of a verification point comprises leaving the test script intact;
wherein said creating of a verification point comprises including a filter to narrow a scope of data capture and thereby reducing a size of a test report;
storing reference data in the verification point; and
subsequently employing the verification point and reference data in running at least one additional test of the software via executing the text script, while leaving the test script intact;
wherein the verification point comprises a statement for yielding output in the form of an object context.
2. The method according to claim 1 , wherein said test script is immune to user interface changes between tests.
3. The method according to claim 1 , wherein said storing comprises modifying the verification point.
4. The method according to claim 3 , wherein said modifying comprises including a reference to historical data in the verification point.
5. The method according to claim 4 , further comprising employing the verification point to refer to historical changes between product versions.
6. The method according to claim 5 , wherein said employing comprises employing the verification point to refer to historical changes between two product versions that are earlier versions than a current product version.
7. An apparatus comprising:
a main memory;
a software testing arrangement in communication with said main memory;
said software testing arrangement acting to:
run a test of software, via executing a test script;
dynamically create a verification point during said miming of the test;
wherein to create a verification point comprises leaving the test script intact;
wherein to create a verification point comprises including a filter to narrow a scope of data capture and thereby reducing a size of a test report;
store reference data in the verification point; and
subsequently employ the verification point and reference data in running at least one additional test of the software via executing the text script, while leaving the test script intact;
wherein the verification point comprises a statement for yielding output in the form of an object context.
8. The apparatus according to claim 7 , wherein said test script is immune to user interface changes between tests.
9. The apparatus according to claim 7 , wherein storing reference data in the verification point comprises modifying the verification point.
10. The apparatus according to claim 9 , wherein said software testing arrangement acts to modify the verification point via including a reference to historical data in the verification point.
11. The apparatus according to claim 10 , wherein said software testing arrangement further acts to employ the verification point to refer to historical changes between product versions.
12. The apparatus according to claim 11 , wherein said software testing arrangement acts to employ the verification point to refer to historical changes between two product versions that are earlier versions than a current product version.
13. A program storage device readable by machine, tangibly embodying a program of instructions executable by the machine to perform a method comprising:
accepting software; and
testing the software;
said testing comprising:
running a test of software, via executing a test script;
dynamically creating a verification point during said running of the test;
wherein said creating of a verification point comprises leaving the test script intact;
wherein said creating of a verification point comprises including a filter to narrow a scope of data capture and thereby reducing a size of a test report;
storing reference data in the verification point; and
subsequently employing the verification point and reference data in running at least one additional test of the software via executing the test script, while leaving the test script intact;
wherein the verification point comprises a statement for yielding output in the form of an object context.
14. The program storage device according to claim 13 , wherein said test script is immune to user interface changes between tests.
15. The program storage device according to claim 13 , wherein said storing comprises modifying the verification point.