Page Comparison

...

BDD has 4 major features.

1. Code

2. My data

   1. Centralized data storage

3. View

4. ModelCoding/Gherkin Interface

5. View Interface

6. Modeling Interface

Let's deep dive into the 4 features.

Code/Gherkin Interface

• Anchor
  Code Code

  Code - This feature allows users to write testcase scenarios using the Gherkin language.

...

To start writing scenarios user should click on Add New Section.

...

View interface

•   

  Anchor
  View View

  View - This featureprovides a graphical building block approach. The building blocks could be rearranged and moved around to modify testcase scenarios. Upon submission, the changes made in the view feature would also be reflected in the code and diagram features.

...

Users can change the scenario by shuffling steps, deleting them, and updating them by clicking the Submit button.·        Anchordatadata My data is a collection of data where users can either drag and drop the output. The following is an example of how a user can create a data collection in BDD

How to create and how to drag and drop into view feature is shown below:

Step by Step:

·        Click on My data from bottom of the page.

·        Click on view all data set icon.

...

·        Click on the Data set icon from left hand corner of the page to create new data set as shown below.

...

·        User can add how many columns and rows are required and name of the data set.

·        Click on back to Project.

·        User can view created Data set as below in My Data option.

...

How to create and Drag Drop data set in view feature as shown below

...

How to delete row or column in data set

To select columns or rows, the user can simply click on the column or row icon located at the page's righthand corner.

...

To delete the desired column or row, the user can manually select it, one row or column at a time.

...

Imagine your application as a library. In this library, there's a main desk (your centralized data storage) where all the important information is kept. This could be user details, settings, or any other critical data your application needs to function.

Gherkin Files: The Bookshelves
In our library, there are several bookshelves (these are your Gherkin files). Each bookshelf contains books (scenarios) that tell different stories (describe different behaviors of your application). However, all these stories are based on the information available at the main desk.

How It Works
Data Centralization: First, you store all the necessary data in one place in your application. This is like keeping all the key information at the main desk in our library analogy.

Data Utilization in Gherkin Files: Each Gherkin file contains various scenarios written in a simple, human-readable format. These scenarios describe how your application should behave in different situations. However, to make these scenarios realistic and relevant, they need details from your centralized data.

Example Scenario: Let's say one of your Gherkin files is about user login behavior. The scenarios in this file will describe what should happen when a user tries to log in, like:

Scenario: Valid user login
  Given a user exists with a <username> and <password>
  When the user tries to log in with the correct credentials
  Then the user should be successfully logged in

In this scenario, the "username" and "password" would come from your centralized data storage.

Benefits: This approach ensures consistency and ease of maintenance. If you need to change a piece of data, you only update it in one place, and all your Gherkin files will use the updated data. It's like changing a piece of information at the main desk, and all stories in the library automatically update with this new information.

...

Modeling Interface

·