BDD Quality Analyzer

TABLE OF CONTENTS

1. Overview

2. How it Works

3. How to Check Quality of BDD Steps

1. Overview

This article provides an detailed information about how to check the quality of BDD steps.

2. How it Works

• Select the feature file from test cases and click on scenario quality analysis
• A report will be generated on the quality of BDD steps.

3. How to Check Quality of BDD Steps

To check the quality of a BDD Steps, start by creating a new project. To know more about how to create a project access Creating a Project. After the project is created, add nodes to the canvas as required. Clicking on a node will open its configuration and you can add features and controls as required. To know more about profiling access Profile a Web Application, generate the Test cases after profiling. Feature File is used as the input for checking the quality of BDD Steps.

Navigate to Test Cases and click on more icon(3 dots) besides a generated test case, click on Scenario Quality Analysis. You can select a Feature File and evaluate the quality and you can also use multiple feature files together to evaluate the quality, The analysis checks whether the BDD steps are in the correct order, if validations are used appropriately, and whether example tables are included where necessary.

A report will open, displaying a summary with numbers and percentages of test cases categorized as Well Defined, Needs Work, or Requires Revision based on the Given-When-Then (GWT) steps. The summary also includes a pie chart for visual representation. This report can be downloaded for further analysis.

A Detailed Suggestions table is also provided, which includes the Scenario Name, Test ID, Category (indicating whether the issue is Major or Minor), and specific suggestions for improvement. Each suggestion is represented by a number from 1 to 9, with each number corresponding to a unique recommendation and it shows based on the number of test cases.

Note: The below points lists all unique suggestions, numbered 1-9 for reference. This will change based on the size of BDD steps and test cases. The suggestion numbers are unique for each report. The Index for suggestions with number will be available in the report.

Suggestions:-

• -No steps defined in the scenario block
• -No 'Then' step found
• -Assertions are insufficient. Consider adding validation steps to verify expected outcomes.
• -The first step should start with 'Given' to set the initial context.
• -Invalid GWT keyword detected: But
• -Invalid GWT keyword detected: Background
• -Step order is inconsistent. Use the standard 'GWT' format for clarity and consistency.
• -Example table is missing.
• -Examples table is missing required fields.
• -UI element names are ambiguous. Use clearer, more descriptive naming.