v-and-v/testium
2
0
Fork 0
Code Issues 5 Pull Requests 1 Actions Packages Projects Releases 7 Wiki Activity

processes management refundation.

Browse Source 
Evaluation removed from conditions, let and exit_conditional
This commit is contained in:
Foué
2026-01-25 15:03:52 +01:00
parent 929e75215b
commit 60636b4fd2
45 changed files with 863 additions and 752 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/manual/sphinx/source/test_items/group_test_item.rst
View File

@@ -8,10 +8,10 @@ This element is of the following form:
- group:
name: Group Item
condition: "'$(OS)' == 'Linux'"
condition: $| "$(OS)" == "Linux" |
steps:
- unittest_file:
test_file: test_prod_rio6_8093.py
test_file: test_prod_alpha_13.py
test_method:
...
- sleep:
@@ -23,4 +23,4 @@ Attributes
--------------------
* The ``steps`` list describes the sequence executed in the group.
It is a list of any of the testium test items,
It is a list of any of the `testium` test items,

9
doc/manual/sphinx/source/test_items/items_common_attributes.rst
View File

@@ -72,9 +72,9 @@ if not provided is given in the table as well.
|``report`` | / | This attribute defines values (a dictionary) which |
| | | will be added in the ``data`` field of the report. |
+-----------------------+-------------------+-------------------------------------------------------+
| ``condition`` | / | The test item is not executed if its |
| | | ``condition`` attribute content is |
| | | evaluated as ``False``. |
| ``condition`` | / | The test item is executed if its |
| | | ``condition`` attribute content is a boolean |
| | | ``True``. |
| | | see :ref:`Conditional |
| | | execution<sec_conditional_execution>`. |
+-----------------------+-------------------+-------------------------------------------------------+
@@ -133,7 +133,8 @@ or in configuration file (see :ref:`config files<sec_configuration_files>`) as a
Conditional execution
-----------------------------------------------
The ``condition`` attribute content is evaluated as a python string.
The ``condition`` attribute content must be a boolean value (if not ``True``, the condition is considered
not met).
.. _sec_process_result:

9
doc/manual/sphinx/source/test_items/let_test_item.rst
View File

@@ -11,15 +11,12 @@ This element is of the following form:
values:
key1: value1
key2: value2
eval:
key3: $(variable)[$(loop_index)]
key3: $| $(variable)[$(loop_index)] |
The ``let`` element is used to set values in the global directory.
Attributes
----------------
* The values list gives the {<key>, <value>} couples to set in the
global directory,
* The eval list gives the strings to evaluate prior to its storage into
the <key> of global directory.
* The ``values`` list gives the {<key>, <value>} couples to set in the
global directory,

6
doc/manual/sphinx/source/test_items/loop_test_item.rst
View File

@@ -39,12 +39,12 @@ Below are described loop test item specific attributes.
* ``Iterator``: giving the number of loop iteration (see dedicated chapter below).
* ``steps``: describes the sequence executed at each cycle; it is
a list of any of the testium test items.
* ``exit_condition``: allows to exit the loop. If False is returned, loop continues
else, it breaks. exit_condition attributes are:
* ``exit_condition``: allows to exit the loop. If True is returned loop continues
otherwise it breaks. exit_condition attributes are:
* ``time``: the loop stops after the time (in minutes) is elapsed (optional)
* ``value``: the loop stops when the content of the value attribute is
evaluated as True (optional)
True (optional)
* ``file``: the loop the script file name that contains a function to be
executed on each loop. Only python script format is supported (optional
if another exit_condition attribute is defined)

6
doc/manual/sphinx/source/test_items/py_func_test_item.rst
View File

@@ -110,13 +110,13 @@ value of the funcToBeExecuted python function.
**Python Interpreter environment setup**
Some global variables have an impact on the ``py_func`` test item behavior:
* ``python_path``: This optional global variable can be used to define
* ``python_bin``: This optional global variable can be used to define
the python executable path. If not defined, the python interpreter is
searched in at the default places in the system.
* ``python_env``: This global variable can be used to define
environment variables for the lua script execution environment.
Only `PATH`, `LUA_PATH`, and `LUA_CPATH` are supported.
Only `PATH` and `PYTHONPATH` are supported.
.. code-block:: yaml
:caption: example of configuration file: param.yaml

4
doc/manual/sphinx/source/test_items/run_test_item.rst
View File

@@ -9,7 +9,7 @@ This test item executes a new instance of testium.
- run:
name: Execute TUM
tum_fime: example_cycle.tum
python_path: python3
python_bin: python3
testium_path: /home/francois/projets/testium-new-report/testium.pyw
log_file: $(home)/reports/test.log
report_file: $(home)/reports/test.rep
@@ -21,7 +21,7 @@ run test item has the following specific attributes:
* ``tum_fime``: mandatory the path of the file to execute, it can be relative to current execution folder,
* ``param_file`` (optional) the path of the parameter file to use, otherwise default parameter file is used.
* ``python_path`` (optional) the path of a specific python to run your scripts,
* ``python_bin`` (optional) the path of a specific python to run your scripts,
* ``testium_path`` (optional) the path of a specific testium to run your scripts,
* ``log_file`` (optional) the path of log file to register, if not provided a file is created with timestamp at the location of TUM file.
* ``report_file`` (optional), the path of report file to create