Pybot parameter explanation

Pybot parameter explanation
1.-m–metadata Name:value Sets the metadata for the topmost test suite (mainly in the test report)
-a) Example:–metadata version:1.2
2.-g–gettag Tag * gives all executed test case settings given the tag
3.-t–test Name * Run according to the name of the test case or full selection.
-a) The name is case-insensitive and space-sensitive, and can be used to match all of them. Matches any character
-B) if using * and. Run, there is a problem in the console, please review the –escape and –argumentfile parameters
4.-s–suite Name * Runs the test suite based on the selected case name, only if the test scenario is in the corresponding test suite and conforms to the filtering criteria for use with –test,–include or –exclude, the name parameter and the –test NA The Me parameter standard is similar. You can also use the "." Symbol as the delimiter for the parent node name:
-a) For example:-S X.Y Select the parent node is the Y test suite for X.
5.-i–include Tag * Choose to run the test case according to the tag name given. The name parameter is similar to the –test parameter. The tag is case-insensitive and whitespace-sensitive, and it can use "*" and "?" as a wildcard character. Tags and patterns can be connected with and, OR and not keywords:
-a) Example: –include foo–include bar*
-b) –include fooandbar*
6.-e–exclude Tag * Does not run the case with these given labels. The rest of the rules are the same as –include
7.-r–rerunfailed Output Select the failed case to re-execute from the previously failed output file.
-a) Selecting the same case requires separate use of the –test parameter separately
8.–runfailed output (RF 2.8.4 version has been replaced by –rerunfailed)
9.-c–critical Tag * Case given tag is considered important. If no important tags are set, then all cases are considered important. Tag can give a pattern such as –include
-n–noncritical Tag * was given a case of tag that was considered unimportant even though he was set up with the critical tag. Tags can be expressed in patterns such as: –include test*
-v–variable Name:value * Set variables in the test data. Only scalar variables are supported, and variable names do not need to take '. ' Refer to the –escape parameter to set more versatile variables using special characters and –variablefile parameters, as well as using the list variable. −a) such as:–variablestr:hello=> {} '. Please refer to the –escape parameter to use special characters and –variablefile parameters to set more versatile variables, you can also use the list variable. -a) For example: –variable Str:hello = {str}= ' Hello '
-B)-v str:hello_world-e space:_ = str=′helloworld′−c) −vx:−vy:42=> {str}= ' Hello World '-c)-V x:-v y:42 =>{x }= ', ${y}= ' 42 '
The path of the-v–variablefile path * variable file:
-a) sample file:
I.
-B) is equivalent to:
I.
-d–outputdir dir stores the path to the output file. The default directory is the directory where the test case is executed, and the directory given is also relative to the case execution, unless the directory being set is an absolute path.
-o–output file XML output files, given the path, and –log, –report, –xunit, And–debugfile, similar, –outputdir-based directories, unless given an absolute path. Other output files are generated based on the XML output file after the case is executed. The XML output file can also provide data for future robot tools. You can give the NONE string to prohibit this function, and also prohibit the log (log) and report function.
The.-l–log file HTML log files. Can be given the NONE prohibit output, the default output log.html
-a) Example: –log mylog.html
-B)-L NONE
-r–report file HTML report files. You can give the NONE prohibit output, the default output: Report.html. Similar to the –log parameter.
-x–xunit file Xunite compatibility test files. It will not be created unless specifically stated otherwise.
-a) –unitfile file (obsolete with –xunit substitution)
-b) –xunitskipnoncritical marked non-critical cases are skipped in the XUnit output results.
The debug files during the-b–debugfile file run are not created unless specifically stated.
-t–timestampoutputs when using this parameter, the timestamp format ' YYYYMMDD-HHMMSS ' will be applied between the base name and extension of all output file names.
-a) For example:-t-o ouputxml-r report.html-l None
-B) Create files: Ouput-20161023-121011.xml and Report-20161023-121012.xml
-c) –splitlog split log file into small file, open with browser more clearly
-D) The title of the –logtitle title generation log. The default title is the name of the test suite. Underscores in all test headings are converted to spaces.
-e) –reportbackgroud the background setting of the colors test report.
--I. ' all_passed:critical_passed:failed ' or ' passed:failed ' color and code are all possible.
---1. Example: –reportbackgroud green:yellow:red
---2. –reportbackgroud #00E: #E00
-l–loglevel level to set the log levels. Available levels: Trace,debug,info (Default Level). Warn,none (no loging). Use syntax: Loglevel:default
-a) Example: –loglevel DEBUG
-b) –loglevel Debug:info
21.–suitestatleve level shows how many layers are displayed in the logs and test reports. All layers are displayed by default.
-a) Example: –suitestatlevel 3
22.–tagstatinclude tag * Only displays matching tags in the test suite statistics and test details in logs and reports. Tag is displayed by default in all test cases. The given tag can be written as a simple pattern (refer to the –test example)
23.–tagstatexclude tag * does not display matching tags in log and test reports that are based on test suite statistics and test details. This option cannot be used with –tagstatinclude, similar to –exclude and –include.
24.–tagstatcombine Tags:name * Create comprehensive statistics based on tags, which are added to the details of the test case by tag and matching. If the option name is not given, the comprehensive statistics name is obtained from the specified tags. Tags will be used in conjunction with the rules given by –include.
-a) Example: –tagstatcombine requrement-*
-b)-tagstatcombine Tag1andtag2:my_name
25.–tagdoc Pattern:doc * Add a document description for the qualifying tag. The document is displayed in the test details and is also displayed in the ' Statistics by Tag ' as a tooltip. The pattern can contain * matches all, and '? ' matches any single character. The document can contain formatting, similar to the –doc option.
-a) Example: –tagdoc mytag:my_documentation
-b) –tagdoc regression:*see*_http://info.html
-c) –tagdoc Owner-*:original_author
26.–tagstatlink Pattern:link:title * Add additional connection addresses by tag statistics. Pattern can contain * matches all and? matches any character. String wildcard expressions can be applied in joins and headings using the%N syntax. N is a match from the beginning of the first few. The underline in the caption is automatically converted to a space.
-a) Example: –tagstatlink mytag:http://my.domain:link
-b) –tagstatlink Bug-*:http:/tracker/id=%1:bug_tracker
27.–removekeywords all|passed|for|wuks|name: * Removes the keyword data from the generated log file. The key is not removed if it contains a warning unless the option parameter is all.
-a) All: Remove data from all keywords
-B) Passed: Remove the keyword data from the successful test cases and suites.
-c) For: Removes the keyword data from the successful iteration of the For loop.
-D) Wuks: Remove all the keywords that processed the last failure, contained in ' BuiltIn. Wait Until Keyword succeds '
-e) Name:: Removes data from keywords that match the matching pattern. The pattern is fully matched for the keyword.
-I. For example: ' Mylib. Keyword ', ' resource. Secdon Keyword '
-f) Case, space, underline not sensitive, can contain * and? As a wildcard character.
-i. Example: –removekeywords name:Lib.HugeKw
-II. –removekeywords name:myresource.*
28.–flattenkeywords for|foritem|name: * flattens matching keywords in the generated log file. Matching keywords get all logs messages from their child keywords and children is discarded otherwise.
-a) For:flatten for loops fully
-B) foritem:flatten individual for loop iterations
-c) Name:: Flatten matched keywords using same matching rules as with
--I. ' –removekeywords name: '
29.–listener class * One for monitoring test execution. Get an example of a notification when a test case starts and ends. The parameters of the listener class can be followed by the class name, with ': ' As the delimiter.
-a) Example: –listener MyListenerClass:arg1:arg2
30.–warnonskippedfiles If this option is used, the skipped test data file produces a visible warning message in the console and log files. The default skipped files only produce a basic system log information for the information.
31.–NOSTATUSRC set the return code to 0 regardless of the failure in the test case. The error code returns normally.
32.–runemptysuite also executes if the top-level test suite is empty. This scenario is useful if there are no matching test cases when used with –include/–exclude.
33.–dryrun validates the test data and executes the test so that the test library keyword is not executed.
34.–exitonfailure any critical basic case failed to stop the test.
35.–exitonerror stop testing when any errors occur
36.–skipteardownonexit If the test execution is paused, skip teardown exit.
37.–randomize All|suites|tests|none executed randomly.
-a) All: random execution of test suites and test cases.
-B) Suites: Random Execution test suite
-c) Tests: Random Execution of test cases.
-D) None: No random execution, default.
-e) Use the syntax ' value:seed ' to give a user random seed, which must be an integer.
--I.–randomize All
--II. –randomize tesets:1234
38.–runmode mode * 2.8 has been deprecated, please use separate: –dryrun,–exitonfailure,–skipteardownonexit, or –randomize option instead.
The output width of the-w–monitorwidth chars monitor. Default is 78
-c–monitorcolors auto|on|ansi|off use color output in the console.
-a) Auto: Use color output when output is not redirected.
-B) On: Always use color.
-c) ANSI: like on parameters, but use ANSI colors in Windows.
-d) off: Forbidden Color
-e) Note that Jpython does not display colors in Windows.
-k–monitormarkers auto|on|off when top layer keyword at the end of the test case, the console displays '. ' Success or ' F ' failure. And the use of the –monitorcolors parameter has been.
-p–pythonpath Path * Add additional paths (Directories,zips,jars) to search the test library when they are imported. Multiple paths can be separated by:.
-a) Example: –pythonpath libs/
-B) –pythonpath/opt/testlibs:mylibs.zip:yourlib
-c)-e star:star-p lib/star.jra-p Mylib.jar
-e–escape What:with * The problem transfer character in the console.
-a) What represents the name of the transferred character, with the character to be transferred into
-b) The transfer character needs to be carefully selected and used.
-c) Amp <&>,apos< ' >,at<@>,bslash<>,colon<:>,comma<,>,curly1<{> Curly2<}>,dollar