Generation of standardized test case information using graph-based methods
Techniques for generation of standardized test case information using graph-based methods are disclosed. In an example method, a computing device receives, from a graphical user interface (GUI), a test case specification, including a graph with a number of nodes, in which at least one pair of nodes are connected by an edge. The computing device receives, from the GUI, a designation of a node as a test case node, preconditions associated with the test case node, and step-expectation maps associated with the test case node. The computing device generates standardized test case information including the test case specification, the preconditions, and the step-expectation maps. The standardized test case information includes a data structure, based on a test case specification standard, that includes a representation of the test case specification and an image of the test case specification. The computing device outputs the standardized test case information.
1 . A method, comprising:
receiving, from a graphical user interface (GUI), a test case specification, comprising a graph comprising a plurality of nodes, wherein at least one pair of nodes are connected by an edge;
receiving, from the GUI, a designation of a first node as a first test case node;
receiving, from the GUI, one or more preconditions associated with the first test case node;
receiving, from the GUI, one or more step-expectation maps associated with the first test case node;
generating standardized test case information comprising the test case specification, the one or more preconditions, and the one or more step-expectation maps, comprising:
generating a representation of the test case specification, comprising a structure portion and a style portion; generating an image of the test case specification; and
generating the standardized test case information, wherein:
the generated standardized test case information includes a data structure including the representation and the image; and
generating the standardized test case information based on a test case specification standard of a test automation service; and
outputting the standardized test case information.
2 . The method of claim 1 , wherein the plurality of nodes comprises
at least one top-level node, comprising
at least one section node, comprising
at least one test case node, each test case node comprising one or more associated preconditions and one or more associated step-expectation maps.
3 . The method of claim 1 , wherein:
each step-expectation map comprises:
at least one step description; and
at least one expectation description, each expectation description mapped to at least one step description; and
each precondition comprises at least one precondition description.
4 . The method of claim 1 , wherein the first test case node further comprises an associated reference descriptor.
5 . The method of claim 1 , wherein the standardized test case information is output to the test automation service to cause generation of a test case outline, wherein the test case outline is characterized by at least the one or more preconditions associated with the first test case node and the one or more step-expectation maps associated with the first test case node.
6 . The method of claim 5 , wherein the standardized test case information is output to the test automation service to further cause generation of executable instructions corresponding to the one or more preconditions associated with the first test case node and the one or more step-expectation maps associated with the first test case node, wherein the test case outline comprises the executable instructions.
7 . The method of claim 1 , wherein at least one node of the plurality of nodes comprises a tag, wherein the tag comprises textual information.
8 . The method of claim 7 , wherein generating the standardized test case information is based on the tag, the tag corresponding to a constraint on the test case specification.
9 . The method of claim 7 , wherein the tag is selected from a plurality of predefined tags.
10 . The method of claim 7 , further comprising receiving, from the GUI, an indication of a custom tag textual information, wherein the tag is based on the custom tag textual information.
11 . The method of claim 1 , wherein the data structure is based on JavaScript Object Notation (JSON).
12 . The method of claim 1 , wherein the graphical user interface (GUI) is based on the KityMinder Core open source project.
13 . The method of claim 1 , wherein the graphical user interface (GUI) is based on the AgileTC open source project.
14 . The method of claim 1 , wherein the standardized test case information is based on the OpenAPI specification.
15 . A non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations including:
receiving, from a graphical user interface (GUI), a test case specification, comprising a graph comprising a plurality of nodes, wherein at least one pair of nodes are connected by an edge; receiving, from the GUI, a designation of a first node as a first test case node;
receiving, from the GUI, one or more preconditions associated with the first test case node;
receiving, from the GUI, one or more step-expectation maps associated with the first test case node;
generating standardized test case information comprising the test case specification, the one or more preconditions, and the one or more step-expectation maps, comprising:
generating a representation of the test case specification, comprising a structure portion and a style portion;
generating an image of the test case specification; and
generating the standardized test case information, wherein:
the generated standardized test case information includes a data structure including the representation and the image; and
generating the standardized test case information based on a test case specification standard of a test automation service; and
outputting the standardized test case information.
16 . The non-transitory computer-readable medium of claim 15 , wherein the plurality of nodes comprises
at least one top-level node, comprising:
at least one section node, comprising one or more test case nodes; and
at least one test case node, wherein each test case node comprises one or more associated preconditions and one or more associated step-expectation maps.
17 . The non-transitory computer-readable medium of claim 15 , wherein at least one node of the plurality of nodes comprises a tag, wherein the tag is a label that characterizes the node.
18 . A system comprising:
one or more processors; and
one or more computer-readable storage media storing instructions which, when executed by the one or more processors, cause the one or more processors to perform operations including:
receiving, from a graphical user interface (GUI), a test case specification, comprising a graph comprising a plurality of nodes, wherein at least one pair of nodes are connected by an edge;
receiving, from the GUI, a designation of a first node as a first test case node; receiving, from the GUI, one or more preconditions associated with the first test case node;
receiving, from the GUI, one or more step-expectation maps associated with the first test case node;
generating standardized test case information comprising the test case specification, the one or more preconditions, and the one or more step-expectation maps, comprising:
generating a representation of the test case specification, comprising a structure portion and a style portion;
generating an image of the test case specification; and
generating the standardized test case information, wherein:
the generated standardized test case information includes a data structure including the representation and the image; and
generating the standardized test case information based on a test case specification standard of a test automation service; and
outputting the standardized test case information.
19 . The system of claim 18 , wherein the plurality of nodes comprises
at least one top-level node, comprising
at least one section node, comprising
at least one test case node, each test case node comprising:
one or more tags;
one or more associated preconditions; and
one or more associated step-expectation maps, wherein:
each step-expectation map comprises:
at least one step description; and
at least one expectation description, each expectation description mapped to at least one step description; and
each precondition comprises at least one precondition description.
20 . The system of claim 19 , wherein:
each tag is a label that characterizes the test case node; and
the one or more tags include a case type tag or a case priority tag.