Behave – Command Line

Behave - Command Line

We have discussed Behave Command Line Arguments. This command-line use for behaving python feature files that are identical to a pattern.

Behave command Line Arguments

Let us discuss some of the command line arguments −

  • –c, –no-color

Impair the usage of the ANSI color escapes.

  • –color –

Utilize the ANSI color escapes. This is an in-built characteristic and can overrule a setting in the configuration file.

  • –d, –dry-run

Summons the formatter without running the steps.

  • -D, –define

Declares the customized information for the config. user-data dictionary.

  • –e, –exclude Pattern

Exclude feature files that are identical to a pattern of regular expression from the execution.

  • –i, –include Pattern

Include feature files that are identical to a pattern of regular expression during the execution.

  • –no-junit

Omit JUnit reports as output.

  • –junit

Add JUnit reports as output. (Irrespective of the -capture/-no-capture options).

  • –f, –format

Define a formatter. If omitted, the in-built formatter is utilized. The –format-help command shall display all the available formats.

  • -steps-catalog

Displays a catalog of all the existing step definitions.

  • –k, –no-skipped

Exclude skipped steps from printing in the console.

  • no-snippets

Exclude snippets from printing in the console for the steps, which are still not implemented.

  • –snippets

This is an in-built characteristic and can overrule a configuration file setting.

  • –m, –no-multiline

Exclude multiple lines tables and strings under steps.

  • –multiline

Include multiple lines tables and strings under steps. This is an in-built characteristic and can overrule a configuration file setting.

  • –n, –name

Include the feature elements, which are identical to the specified name in the run. If the option is provided multiple times, it shall match with all the names.

  • –no-capture

Exclude stdout from capturing.

  • –capture

Include stdout. This is an in-built characteristic and can overrule a configuration file setting.

  • –no-capture-stderr

Exclude stderr from capturing.

  • –capture-stderr

Include stderr. This is an in-built characteristic and can overrule a configuration file setting.

  • –no-logcapture

Exclude log from capturing.

  • –logcapture

Include log capturing the failures. This is an in-built characteristic and can overrule a configuration file setting.

  • –logging-level

Mention the logging level that shall be captured. The default value is INFO.

  • –logging-format

Mention the user-defined format for printing statements. The default value is %(levelname)s:%(name)s:%(message)s.

  • –logging-datefmt

Mention the user-defined date and time format for printing statements.

  • –logging-filter

Mention if the statements are to be filtered or not. All the statements are captured by default.lter out the unnecessary output.

  • –logging-clear-handlers

Remove all the handlers which are used for logging.

  • –no-summary

Exclude summary post the execution.

  • -summary

Include summary post the execution.

  • –o, –outfile

Write the given file instead of using stdout.

  • –q, –quiet

Alias are used for –no-snippets –no-source.

  • –s, –no-source

Exclude printing the file and the line of step definition along with steps.

  • –show-source

Include printing the file and the line of step definition along with the steps. This is an in-built characteristic and can overrule a configuration file setting.

  • –stage

Describes the present stage of the test. The stage name is utilized as the name affix for the environment file, along with the directory for the steps.

  • –stop

Terminate executing tests after encountering the first failure.

  • –t, –tags

Include the features/scenarios having tags, which are identical to TAG_EXPRESSION in the execution.

  • –T, –no-timings

Exclude printing duration of execution for each step.

  • –show-timings

Capture the duration taken by each step to complete in seconds in the console. This is an in-built characteristic and can overrule a configuration file setting.

  • –v, –verbose

Displays the loaded features and files.

  • –w, –wip

Execute the scenarios having the WIP tag. Moreover, we have to use the plain formatter and not record the stdout or log output and terminate post-first failure.

  • –x, –expand

Flatten the table of Scenario Outline in output.

  • –lang

Utilize keywords for a language except for English.

  • –lang-list

Displays all the languages present in –lang.

  • –lang-help

Displays all the translations acquired for a single language.

  • –tags-help

Display help for tag statements.

  • –version

Displays version.

  • junit –directory

This is the directory location where the Junit reports are stored.

  • –show-skipped

Include skipped steps while printing in the console. This is an in-built characteristic and can overrule a configuration file setting.

Next Topic – Click Here

This Post Has 25 Comments

Leave a Reply