Graphical model for test case viewing, editing, and reporting
Various techniques for interacting with a test case via a graphical model are disclosed. For example, one method involves displaying a first icon, which represents a first testing activity within a test case; displaying a second icon, which represents a second testing activity within the test case; and displaying a connector, which couples the first icon and the second icon. An assertion (e.g., against test results obtained by performing the first testing activity) is associated with the connector.
1. A method comprising:
retrieving, from a memory device, test case data defining a particular test including:
a plurality of test nodes, each node including logic for performing one or more respective testing activities on one or more software entities; and
a particular test flow for performing testing activities corresponding to one or more of the plurality of test nodes;
dynamically generating, using a processor device, a graphical model of the particular test for display on a graphical user interface based on the test case data, the graphical model including at least:
a first icon, wherein the first icon represents a first test activity of a first node in the plurality of nodes;
a second icon, wherein the second icon represents a second test activity of a second node in the plurality of nodes; and
first connector coupling at least the first icon and the second icon, representing a first flow path of the particular test from the first testing activity to the second testing activity;
receiving, via the graphical user interface, user input specifying a modification of the displayed graphical model;
modifying the test case data based, at least in part, on the modification of the graphical model; and
updating display of the graphical model based at least in part on the user input.
2. The method of claim 1 , wherein
the user input modifying the graphical model comprises user input adding a new icon to the graphical model, wherein the new icon represents a third testing activity; and
the method further comprises updating the test case to include a third test node configured to perform the third testing activity.
3. The method of claim 1 , further comprising:
receiving, via the graphical user interface, additional user input selecting the first icon; and
providing display of detailed information corresponding to the first testing activity on the graphical user interface, in response to the additional user input.
4. The method of claim 1 , further comprising:
receiving user input selecting a report; and
generating a report corresponding to the first testing activity and the second testing activity.
5. The method of claim 1 ,
wherein
generating the graphical model includes parsing the test case data to correlate test case elements with graphical elements to be included in the graphical model.
6. The method of claim 1 , wherein:
the first connector represents the first flow path in connection with a first test condition; and
the graphical model further includes:
a third icon representing a third testing activity of a third node in the plurality of nodes, and
a second connector coupling at least the first icon and the third icon, representing a second flow path, in connection with a second alternative test condition, from the first testing activity to the third test activity.
7. The method of claim 6 , wherein the first flow path corresponds to a default test flow and the second flow path corresponds to an alternate, test failure flow.
8. The method of claim 1 , further comprising:
executing the modified test case data to perform a modified version of the particular test; and
providing a graphical representation of results of the modified version of the particular test.
9. The method of claim 8 , wherein the graphical representation of the results is presented within the modified graphical model and includes a graphical effect corresponding to the first icon representing execution of at least the first testing activity.
10. The method of claim 1 , wherein each test node in the plurality of test nodes is one of a plurality of node types and represented, within the graphical representation, by a corresponding icon with an appearance based on the node type of the represented test node.
11. The method of claim 1 , wherein the graphical model is generated based at least in part on at least one predefined viewing preference corresponding to a particular user.
12. A system comprising:
a processor;
at least one memory configured to store data including program instructions executable by the processor; and
a graphical testing module configured to:
retrieve test case data defining a particular test including:
a plurality of test nodes, each node including logic for performing one or more respective testing activities on one or more software entities; and
a particular test flow for performing testing activities corresponding to one or more of the plurality of test nodes;
dynamically generate a graphical model of the particular test for display on a graphical user interface based on the test case data, the graphical model including at least:
a first icon, wherein the first icon represents a first testing activity of a first node in the plurality of nodes;
a second icon, wherein the second icon represents a second testing activity of a second node in the plurality of nodes; and
a connector coupling at least the first icon and the second icon, representing a first flow path of the particular test from the first testing activity to the second testing activity;
receive, via the graphical user interface, user input specifying a modification of the displayed graphical model;
modify the test case data based, at least in part, on the modification of the graphical model; and
update display of the graphical model based at least in part on the user input.
13. The system of claim 12 , wherein
the user input modifying the graphical model comprises user input adding a new icon to the graphical model, wherein the new icon represents a third testing activity; and
the program instructions are executable to update the test case to include a third test node configured to perform the third testing activity.
14. The system of claim 12 , wherein the program instructions are executable by the processor to:
receive additional user input selecting the first icon; and
cause display of detailed information corresponding to the first testing activity on the graphical user interface, in response to the additional user input.
15. The system of claim 12 , wherein the program instructions are executable by the processor to:
receive user input selecting a report; and
generate a report corresponding to the first testing activity and the second testing activity.
16. The system of claim 12 , wherein
generation of the graphical model includes parsing the test case data to correlate test case elements with graphical elements to be included in the graphical model.
17. A non-transitory, computer readable medium comprising program instructions executable by at least one processor to:
retrieve test case data defining a particular test including:
a plurality of test nodes, each node including logic for performing one or more respective testing activities on one or more software entities; and
a particular test flow for performing testing activities corresponding to one or more of the plurality of test nodes;
dynamically generate a graphical model of the particular test for display on a graphical user interface based on the test case data, the graphical model including at least:
a first icon, wherein the first icon represents a first testing activity of a first node in the plurality of nodes;
a second icon, wherein the second icon represents a second testing activity of a second node in the plurality of nodes; and
a connector coupling at least the first icon and the second icon, representing a first flow path of the particular test from the first testing activity to the second testing activity;
receive, via the graphical user interface, user input specifying a modification of the displayed graphical model;
modify the test case data based, at least in part, on the modification of the graphical model; and
update display of the graphical model based at least in part on the user input.
18. The system of claim 17 , wherein
the user input modifying the graphical model comprises user input adding a new icon to the graphical model, wherein the new icon represents a third testing activity; and
the program instructions are executable to update the test case to include a third test node configured to perform the third testing activity.
19. The system of claim 17 , wherein the program instructions are executable to:
receive, via the graphical user interface, additional user input selecting the first icon; and
display detailed information corresponding to the first testing activity on the graphical user interface, in response to the additional user input.
20. The system of claim 17 , wherein the program instructions are executable to:
receive user input selecting a report; and
generate a report corresponding to the first testing activity and the second testing activity.
21. The system of claim 17 , wherein
generation of the graphical model includes parsing the test case data to correlate test case elements with graphical elements to be included in the graphical model.
22. A method comprising:
retrieving, from a memory device, test case data defining a particular test including:
a plurality of test nodes, each node including logic for performing one or more respective testing activities on one or more software entities; and
a particular test flow for performing testing activities corresponding to one or more of the plurality of test nodes;
dynamically generating a graphical model of the particular test for display on a graphical user interface based on the test case data, the graphical model including at least:
a first icon, wherein the first icon represents a first testing activity of a first node in the plurality of nodes;
a second icon, wherein the second icon represents a second testing activity of a second node in the plurality of nodes;
a third icon, wherein the third icon represent a third testing activity of a third node in the plurality of nodes;
a first connector coupling at least the first icon and the second icon, representing a first flow path, in connection with a first test condition, from the first testing activity to the second testing activity; and
a second connector coupling at least the first icon and the second icon, representing a second flow path, in connection with a second alternative test condition, from the first testing activity to the third testing activity;
receiving, via the graphical user interface, user input specifying a modification of the displayed graphical model;
modifying the test case data based at least in part on the modification of the graphical model; and
updating display of the graphical model based at least in part on the user input.