Execute Program

The module is able to execute programs. Like the Automic Job Messenger with the parameter CMD the module is able to decrypt passwords that are part of the commandline. The difference is that this module uses the same exit code as the program that has been execute.

Designation

Name

ta.Execute

Aliases

ta.CucumberExecute

Configuration

Optionen

Source (source)

Defines the type of source where to find the Cucumber definitionMögliche Werte: File (file), Object (object)

Cucumber Definition (Object) (cucumber-object)

The given object contains the Cucumber definition in the text documentation

Cucumber Definition (File) (cucumber-file)

The given file contains the Cucumber definition

Tags (tags)

If given scenarios must of at least one of the given tags to be executed

Exclude Tags (exclude-tags)

If given scenarios will be excluded if at least one its tag matches one of the list

Custom Attributes (custom-attributes)

A list of custom b4A expression attributes. Each entry is defined as a key-value pair in the format key=value.

Ausgabe

Object for structured documentation (structured-docu)

If given the information are stored in the structured documentation of the object

Connection (structured-docu-connection)

if given the object for the structured documentation is used in the given connectionMögliche Werte: <TabItem b4A Verbindungen>

Name of structured documentation (structured-docu-name)

Defines the name of the tab of the structured documentation that should be used. If empty the first one is chosen.

empty structured documentation first (structured-docu-reset)

if set the structured documentation of the object is emptied first

XML Variable (xml-variable)

name of the XML variable object used to store the information

Key (xml-variable-key)

key in the XML variable object to use

XML Variable Source Connection (xml-variable-source)

If given it defines an alternative b4A connection where to find the variable objectMögliche Werte: <TabItem b4A Verbindungen>

Description

The test results can either be written to the structured documentation of an object or to an XML variable. If the latter is not specified and the test specification is read from a documentation object, the following rule applies: The results are either written to the explicitly specified object (option Object for structured documentation) or the object from which the test specification is read is used.

Output format XML-Vatriable

The report on the test execution looks like the XML document in the following example.

<?xml version="1.0" encoding="UTF-8"?>
<best4Automic>
    <ta>
        <feature status="Success">
            <scenario status="Success">
                <description/>
                <given status="Success">
                    <step status="Success">
                        <description>Workflow B4A.BASE.JOBP@IF.RUN</description>
                        <details><![CDATA[Workflow B4A.BASE.JOBP@IF.RUN exists]]></details>
                    </step>
                </given>
                <when status="Success">
                    <step status="Success">
                        <description>Execute B4A.BASE.JOBP@IF.RUN</description>
                        <details><![CDATA[The object B4A.BASE.JOBP@IF.RUN was successfully activated with the run ID 1710095]]></details>
                    </step>
                </when>
                <then status="Success">
                    <step status="Success">
                        <description>Task status of B4A.BASE.JOBP@IF.RUN is</description>
                        <details><![CDATA[Status code 1900 of the task B4A.BASE.JOBS@UNIX.RUN(2) matches the status ENDED_OK]]></details>
                    </step>
                </then>
            </scenario>
        </feature>
    </ta>
</best4Automic>

A structure as in the previous example is created in the XML document for each scenario.

Example XPath to find all failed scenarios

/best4Automic/ta/feature/scenario[status="Failure"]