Blog

in this chapter, we will discuss Behave Debugging. Behave scripts can be debugged by dry running the test steps. The dry run helps to go over all the test steps without actually running it. It helps to determine the un-defined steps in the step definition file.

It verifies if there are any missing import statements, syntax errors, and so on. All these issues get detected in a quick time by the dry run. If we are doing mass updates or any configuration changes, dry running helps to detect any errors in a short time.

If we would have to run an entire suite for Behave debugging, that would be time-consuming. In Behave, we can do a debug by a dry run with the help of the below-mentioned command −

behave --no-capture --dry-run

You will get the screen as shown below −

The output shows 3 untested which shows the count of the test steps.

Let us dry run feature files having unimplemented steps, as shown below −

The output clearly defines the un-defined steps in the step definition file obtained by the dry run.

Next Topic – Click Here