Requirements to test system and method
A requirements to test (R2T) system is implemented, which provides an automated system by which a user interface (UI)-test automation script package is generated and the generated test scripts therein are executed against software. A visualized workflow is translated into some machine-consumable formatted file. The translated workflow is utilized by an artificial intelligence driven automated R2T engine to discover paths through the workflow, a series of executable steps for the paths that detail how the software will be used, and ultimately test scripts that are generated using pre-defined validation templates. An automation platform executes the test scripts through the software associated with the workflow, which automatically captures evidence of the executed test scripts to fulfill computer system validation requirements. The R2T system provides an automated solution for test script creation and system validation to expedite the validation process and thereby streamline a software's time to market.
1. A Requirements to Test method of producing, by a computing device, User Interface (UI)-Test Automation scripts, without relying on human intent and personal knowledge, to automatically test and validate software, the method comprising steps of:
on the computing device, without relying on human intent and personal knowledge:
translating a workflow of a client's system into a standardized machine-executable formatted file, the workflow comprising a process flow, definitions, forms, and behavior of the client's system;
discovering unique paths within the translated workflow of the client's system, wherein the discovered unique paths include different trajectories from a beginning point to an ending point through the workflow of the client's system;
generating use scenarios each including a plurality of executable steps by applying one or more solution models to each of the unique paths;
applying validation templates to the plurality of executable steps of each of the use scenarios to ensure that the plurality of executable steps satisfies requirements for validation; and
generating a plurality of UI-test automation scripts to perform validation of the client's system defined by the workflow.
2. The method of claim 1 , wherein the unique paths are discovered using artificial intelligence and at least one machine learning processes.
3. The method of claim 1 , wherein the machine-executable formatted file is rendered in the extensible markup language (XML).
4. The method of claim 1 , wherein the UI-test automation scripts are configurable for automated execution.
5. The method of claim 4 , further comprising the step of loading UI-test automation scripts into an automation platform to individually execute each test script through the software.
6. The method of claim 5 , further comprising the step of generating evidence of actual and expected results for each executed UI-test automation script.
7. The method of claim 6 , wherein the evidence includes screenshots.
8. The method of claim 7 , wherein the screenshots visually highlights comparisons between the actual and expected results.
9. The method of claim 6 , wherein the evidence includes a video recording of one or more of the executed UI-test automation scripts.
10. The method of claim 6 , wherein the evidence includes a traceability matrix mapping requirement to the executed UI-test automation scripts.
11. The method of claim 1 , wherein the validation templates are pre-defined.
12. A Requirements to Test system to produce User Interface (UI)-Test Automation scripts, without relying on human intent and personal knowledge to automatically test, and validate software, the system comprising:
a computer having a processor configured, without relying on human intent and personal knowledge, to:
translate a workflow of a client's system into a standardized machine-executable formatted file, the workflow comprising a process flow, definitions, forms, and behavior of the client's system;
discover unique paths within the translated workflow of the client's system, wherein the discovered unique paths include different trajectories from a beginning point to an ending point through the workflow of the client's system;
generate use scenarios each including a plurality of executable steps by applying one or more solution models to each of the unique paths;
apply validation templates to the plurality of executable steps of each of the use scenarios to ensure that the plurality of executable steps satisfies requirements for validation;
generate a plurality of UI-test automation scripts to perform validation of the client's system defined by the workflow.
13. The system of claim 12 , wherein each of the plurality of UI-test automation scripts is configured to test a different operation associated with the client's system defined by the workflow.
14. The system of claim 13 , wherein each test script is associated with and configured to test a function of the validation templates.
15. The system of claim 12 , wherein to translate the workflow, the processor is further configured to
associate a task to each operation in the workflow,
set a structure for team members and associated roles,
describe a list of data elements to be entered for each associated task, and policy descriptions that define conditional execution of a respective workflow.
16. The system of claim 12 , wherein the plurality of UI-test automation scripts emulate user interaction operations with the client's system, navigation, data entry, clicks, and selections.
17. A non-transitory computer-readable memory device storing instructions which, when executed by a computing device, cause the computing device to perform a Requirements to Test method to produce User Interface (UI)-Test Automation scripts without relying on human intent and personal knowledge to automatically test and validate software, the method comprising steps of:
on the computing device, without relying on human intent and personal knowledge:
translating a workflow of a client's system into a standardized machine-executable formatted file, the workflow comprising a process flow, definitions, forms, and behavior of the client's system;
discovering unique paths within the translated workflow of the client's system, wherein the discovered unique paths include different trajectories from a beginning point to an ending point through the workflow of the client's system;
generating use scenarios each including a plurality of executable steps by applying one or more solution models to each of the unique paths;
applying validation templates to the plurality of executable steps of each of the use scenarios to ensure that the plurality of executable steps satisfies requirements for validation; and
generating a plurality of UI-test automation scripts to perform validation of the client's system defined by the workflow.
18. The non-transitory computer-readable memory devices of claim 17 , further comprising the step of generating a traceability matrix that maps requirements to the UI-Test Automation scripts.
19. The non-transitory computer-readable memory devices of claim 17 , wherein the UI-test Automation scripts are generated by applying pre-defined validation scripts to the executable steps.
20. The non-transitory computer-readable memory devices of claim 19 , wherein the pre-set validation scripts test for operational qualification and performance qualification of the client's system.