Feature file validation tool

Patent metadata

Field	Value
Publication number	US-10055330-B2
Application number	US-201615363370-A
Country	US
Kind code	B2
Filing date	Nov 29, 2016
Priority date	Nov 29, 2016
Publication date	Aug 21, 2018
Grant date	Aug 21, 2018

Abstract

A feature file validation tool generates a first test case details file by transforming a test case file to include field names and field values. The feature file includes a plurality of tests, each including a plurality of steps. The feature file validation tool determines whether each of the plurality of steps is valid by comparing each of the plurality of steps to a step definition file. The feature file validation tool applies computer language rules to determine that the first test case details file conforms to the first computer language. The feature file validation tool generates a second test case details file by transforming the first test case details file into a different file format. The feature file validation tool links the two test case detail files using test identifications.

First claim

What is claimed is:

1. A feature file validation tool stored on a hardware memory comprising:
a retrieval engine configured to:
receive a request to configure a test case file, the test case file comprising a plurality of tests and each test comprising a plurality of steps, wherein each test determines whether a functionality of a software application is operating properly; and
retrieve the test case file in response to the request;

a configuration engine configured to:
receive a plurality of field names, the plurality of field names comprising an application field name and a project field name;
receive a field value for each of the plurality of field names, wherein:
the field value for the application field name indicates the software application; and
the field value for the project field name indicates a software development project; and

generate a first test case details file in a first computer language by including the received field names and the received field value for each of the plurality of field names in the test case file, the first test case details file comprising:
the plurality of tests;
the plurality of field names; and
the field value for each of the plurality of field names;

a validation engine configured to:
determine whether each of the plurality of steps of the plurality of tests is valid by comparing each of the plurality of steps to a step definition file, the step definition file comprising a catalog of predetermined valid steps; and
apply computer language rules to determine that the first test case details file conforms to the first computer language;

a transformation engine configured to generate a second test case details file by transforming the first test case details file from a first file format to a second file format, wherein the second test case details file comprises the plurality of tests, the plurality of field names, and the field value for each of the plurality of field names; and
a synchronization engine configured to:
generate a test identifier for each of the plurality of steps in the second test case details file; and
transform the first test case details file to include the test identifier for each of the plurality of steps.

2. The feature file validation tool of claim 1 , wherein the first file format is an Extensible Markup Language format and the second file format is an EXCEL format.

3. The feature file validation tool of claim 1 , wherein the first computer language is a Gherkin computer language.

4. The feature file validation tool of claim 1 , wherein the validation engine generates a warning message upon at least one of a determination that one or more of the plurality of steps of the plurality of tests is not valid and a determination that the first test case details file does not conform to the first computer language.

5. The feature file validation tool of claim 1 , wherein:
the retrieval engine is further configured to retrieve a plurality of test case files;
the generation engine is further configured to generate a test case details file for each of the plurality of test case files; and
the second test case details file comprises each of the plurality of test case files.

6. The feature file validation tool of claim 1 , wherein the configuration engine receives the plurality of field names and the field value for each of the plurality of field names from a graphical user interface.

7. A method comprising:
receiving a request to configure a test case file, the test case file comprising a plurality of tests and each test comprising a plurality of steps, wherein each test determines whether a functionality of a software application is operating properly;
retrieving the test case file in response to the request;
receiving a plurality of field names, the plurality of field names comprising an application field name and a project field name;
receiving a field value for each of the plurality of field names, wherein;
the field value for the application field name indicates the software application; and
the field value for the project field name indicates a software development project;

generating a first test case details file in a first computer language by including the received field names and the received field value for each of the plurality of field names in the test case file, the first test case details file comprising:
the plurality of tests;
the plurality of field names; and
the field value for each of the plurality of field names;

determining whether each of the plurality of steps of the plurality of tests is valid by comparing each of the plurality of steps to a step definition file, the step definition file comprising a catalog of predetermined valid steps;
applying computer language rules to determine that the first test case details file conforms to the first computer language;
generating a second test case details file by transforming the first test case details file from a first file format to a second file format, wherein the second test case details file comprises the plurality of tests, the plurality of field names, and the field value for each of the plurality of field names;
generating a test identifier for each of the plurality of steps in the second test case details file; and
transforming the first test case details file to include the test identifier for each of the plurality of steps.

8. The method claim 7 , wherein the first file format is an Extensible Markup Language format and the second file format is an EXCEL format.

9. The method claim 7 , wherein the first computer language is a Gherkin computer language.

10. The method claim 7 , further comprising generating a warning message upon at least one of a determination that one or more of the plurality of steps of the plurality of tests is not valid and a determination that the first test case details file does not conform to the first computer language.

11. The method claim 7 , further comprising:
retrieving a plurality of test case files;
generating a test case details file for each of the plurality of test case files; and
the second test case details file comprises each of the plurality of test case files.

12. The method claim 7 , further comprising receiving the plurality of field names and the field value for each of the plurality of field names from a graphical user interface.

13. A non-transitory computer-readable medium comprising software, the software when executed by one or more processing units configured to:
receive a request to configure a test case file, the test case file comprising a plurality of tests and each test comprising a plurality of steps, wherein each test determines whether a functionality of a software application is operating properly;
retrieve the test case file in response to the request;
receive a plurality of field names, the plurality of field names comprising an application field name and a project field name;
receive a field value for each of the plurality of field names, wherein:
the field value for the application field name indicates the software application; and
the field value for the project field name indicates a software development project;

generate a first test case details file in a first computer language by including the received field names and the received field value for each of the plurality of field names in the test case file, the first test case details file comprising:
the plurality of tests;
the plurality of field names; and
the field value for each of the plurality of field names;

determine whether each of the plurality of steps of the plurality of tests is valid by comparing each of the pl

Assignees

• Bank Of America

Inventors

• Sharma Ramesh

Classifications

• G06F11/3684 Primary

  for test design, e.g. generating new test cases · CPC title

• G06F11/3616 Primary

  using software metrics · CPC title