Data Functionality

In this section you will learn more about

How to work with data in BDD tab
Know more about Centralized Data Storage

How to work with Data in BDD tab

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 dataset in My Data :

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.

Know more about Centralized Data Storage

Centralized Data Storage
Understanding Data Sharing in Gherkin Files

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>
    |username|password|
    |Alexis| 123123|
  When the user tries to log in with the correct credentials
  Then the user should be successfully logged in

Or in the “view”

In this scenario, in the “View”, the "username" and "password" data are linked to our 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.

When a user imports a file containing a dataset or example into Conformiq Visualizer, if multiple data entries share the same column name, they will be considered as one data entry (The latest is the truth). To maintain distinct data entries, ensure that each has a unique column title or includes additional columns to differentiate them

Conclusion
By having a single source of truth for your data and spreading it across various Gherkin files, you make your application's behavior-driven development more efficient and manageable. It's a smart way to ensure that all parts of your application are singing the same tune, using the same, up-to-date information.