python func validation ok.
This commit is contained in:
@@ -64,6 +64,9 @@ In the example above, the global variable ``$(lfn_activity)``
|
||||
would be created at the end of the item execution. It would contain the resulting
|
||||
value of the funcToBeExecuted python function.
|
||||
|
||||
The ``lua_func`` will always result ``PASS``, except if the called function raises
|
||||
and exception or if the ``expected_result`` attribute is used.
|
||||
|
||||
**Lua Interpreter environment setup**
|
||||
|
||||
Some global variables have an impact on the ``lua_func`` test item behavior:
|
||||
|
||||
@@ -6,9 +6,9 @@
|
||||
The ``py_func`` test item is used to execute custom python scripts with the given
|
||||
input parameters.
|
||||
|
||||
There are two modes for executing a ``py_func`` item. The class mode and the function mode.
|
||||
There are two modes for executing a ``py_func`` item. The *class* mode and the *function* mode.
|
||||
|
||||
class py_func item
|
||||
class ``py_func`` item
|
||||
-------------------------
|
||||
|
||||
This is the normal way of calling some custom python code.
|
||||
@@ -80,7 +80,8 @@ There is no possibility to access the report features in that mode.
|
||||
|
||||
**Attributes**
|
||||
|
||||
Beside common test items attributes, py_func item has specific attribute, some of which being mandatory.
|
||||
Beside common test items attributes, ``py_func`` item has specific attribute,
|
||||
some of which being mandatory.
|
||||
|
||||
* ``file``: the script file name that contains the function to be executed.
|
||||
Only python script format is supported.
|
||||
@@ -107,6 +108,9 @@ In the example above, the global variable ``$(pfn_function test item)``
|
||||
would be created at the end of the item execution. It would contain the resulting
|
||||
value of the funcToBeExecuted python function.
|
||||
|
||||
The ``py_func`` will always result ``PASS``, except if the called function raises
|
||||
and exception or if the ``expected_result`` attribute is used.
|
||||
|
||||
**Python Interpreter environment setup**
|
||||
|
||||
Some global variables have an impact on the ``py_func`` test item behavior:
|
||||
|
||||
Reference in New Issue
Block a user