Methods and systems for synchronizing behavior-driven development (BDD) specifications and results to a single point of truth while treating each scenario in the script as a separate test

A system comprising:

• a processor;
• and
• a memory coupled with and readable by the processor and storing therein a set of instructions which, when executed by the processor, causes the processor to manage a software application lifecycle by:
• receiving a Behavior Driven Development (BDD) specification for an application, the BDD specification comprising an executable script defining a plurality of features for the application and a plurality of scenarios, each scenario representing a test for one or more features of the plurality of features of the application, and each feature comprising one or more user stories;
• creating a test entity for and corresponding to each scenario of the plurality of scenarios in the BDD specification;
• marking each scenario of the plurality of scenarios in the BDD specification with a test IDentifier (ID), the test ID linking the created test entity to the corresponding scenario of the plurality of scenarios in the BDD executable script;
• receiving results of execution of one or more scenarios of the plurality of scenarios;
• reporting the received results of the execution of the one or more scenarios of the plurality of scenarios on a per-feature and per-scenario basis, wherein reporting the received execution results comprises marking each scenario within the executable script of the BDD specification to indicate an action related to each scenario of the executable script and an automation status of each scenario of the executable script based on the received results of execution of the one or more scenarios, the automation status of each scenario indicating whether the scenario was executed automatically or manually;
• and
• synchronizing the received results of execution of the plurality of scenarios with the BDD specification.

A non-transitory, computer-readable medium comprising a set of instructions stored therein which, when executed by a processor, causes the processor to manage a software application lifecycle by:

• receiving a Behavior Driven Development (BDD) specification for an application, the BDD specification comprising an executable script defining a plurality of features for the application and a plurality of scenarios, each scenario representing a test for one or more features of the plurality of features of the application, and each feature comprising one or more user stories;
• creating a test entity for and corresponding to each scenario of the plurality of scenarios in the BDD specification;
• marking each scenario of the plurality of scenarios in the BDD specification with a test IDentifier (ID), the test ID linking the created test entity to the corresponding scenario of the plurality of scenarios in the BDD executable script;
• receiving results of execution of one or more scenarios of the plurality of scenarios;
• reporting the received results of the execution of the one or more scenarios of the plurality of scenarios on a per-feature and per-scenario basis, wherein reporting the received execution results comprises marking each scenario within the executable script of the BDD specification to indicate an action related to each scenario of the executable script and an automation status of each scenario of the executable script based on the received results of execution of the one or more scenarios, the automation status of each scenario indicating whether the scenario was executed automatically or manually;
• and
• synchronizing the received results of execution of the plurality of scenarios with the BDD specification.