Rename unittest_file item to unittest

- constants.py: TYPE_UNITTEST_FILE → TYPE_UNITTEST, cmd "unittest_file" → "unittest"
- All Python files updated: test_item_unittest.py, test_set.py, test_init.py,
  terminal.py, report_export_txt.py, test_tree_item.py
- All .tum files updated (examples, validation, doc)
- Sphinx doc: unittest_file_test_item.rst → unittest_test_item.rst,
  all references updated

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

doc/manual/sphinx/source/other_features.rst

@@ -75,7 +75,7 @@ a tooltip on the test row.
         name: Test example
         steps:
 
-            - unittest_file:
+            - unittest:
                 name: unittest item
                 doc: |
                     The purpose of this unittest test item is to demonstrate
@@ -93,4 +93,4 @@ See illustration in :numref:`Figure %s<doc-illustration>`.
 Unittest
 ^^^^^^^^^
 
-For ``unittest_file`` type test items, the python docstring of the test method is used as documentation.
+For ``unittest`` type test items, the python docstring of the test method is used as documentation.

doc/manual/sphinx/source/test_items/group_test_item.rst

@@ -10,7 +10,7 @@ This element is of the following form:
         name: Group Item
         condition: <| "$(OS)" == "Linux" |>
         steps:
-            - unittest_file:
+            - unittest:
                 test_file: test_prod_alpha_13.py
                 test_method:
                     ...

doc/manual/sphinx/source/test_items/items_common_attributes.rst

@@ -33,7 +33,7 @@ if not provided is given in the table as well.
     |                       |                   | It depends on the test item to take it                |
     |                       |                   | into account or not.                                  |
     |                       |                   | For example it makes sense to use it                  |
-    |                       |                   | for ``unittest_file`` test type                       |
+    |                       |                   | for ``unittest`` test type                       |
     |                       |                   | because it  can contain many sub-tests,               |
     |                       |                   | but not for sleep test type.                          |
     |                       |                   | In cycles, it means that the child                    |

doc/manual/sphinx/source/test_items/loop_test_item.rst

@@ -12,7 +12,7 @@ This element is of the following form:
         name: Cycle Temperature
         iterator: 10
         steps:
-            - unittest_file:
+            - unittest:
                 test_file: test_prod_rio6_8093.py
             - py_func:
                 name: function test item

doc/manual/sphinx/source/test_items/unittest_test_item.rst

@@ -1,15 +1,15 @@
-**unittest_file** test item
+**unittest** test item
 ============================================================
 
-unittest_file test item allows the execution of unittest test script which
+unittest test item allows the execution of unittest test script which
 is part of python standard libraries.
 
 The tum file prototype is as followed:
 
 .. code-block:: yaml
-    :caption: ``unittest_file`` test item usage example
+    :caption: ``unittest`` test item usage example
 
-    - unittest_file:
+    - unittest:
         name: unitTest test item
         test_file: unitTestScript.py
         test_method:
@@ -23,7 +23,7 @@ Beside common test items attributes, unittest test item has specific attribute,
 
 * ``test_file``: it is the name (and eventually path) of the unittest file
   to be processed.
-* ``test_method``: it is an optional unittest_file test sub-item. If one or more
+* ``test_method``: it is an optional unittest test sub-item. If one or more
   elements are present, the unittest python script file is parsed and only
   the corresponding methods are included in the test tree. Otherwise, all
   the test methods are included in the test tree.
@@ -78,4 +78,4 @@ Here is an example how to use the console module from python ``unittest``.
 
         @classmethod
         def tearDownClass(cls):
-            cls.consA0.close()
+            cls.consA0.close()

doc/manual/sphinx/source/tum_syntax.rst

@@ -259,7 +259,7 @@ step list attributes.
    test_items/report_test_item.rst
    test_items/run_test_item.rst
    test_items/sleep_test_item.rst
-   test_items/unittest_file_test_item.rst
+   test_items/unittest_test_item.rst