You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Set variable ``VAR`` in all tests or optionally only in test ``TEST`` to ``VAL``.
486
486
487
+
``TEST`` can have the form ``[TEST.][FIXT.]*``, in which case ``VAR`` will be set in fixture ``FIXT`` of ``TEST``.
488
+
Note that this syntax is recursive on fixtures, so that a variable can be set in a fixture arbitrarily deep.
489
+
``TEST`` prefix refers to the test class name, *not* the test name, but ``FIXT`` refers to the fixture name *inside* the referenced test.
490
+
487
491
Multiple variables can be set at the same time by passing this option multiple times.
488
492
This option *cannot* change arbitrary test attributes, but only test variables declared with the :attr:`~reframe.core.pipeline.RegressionMixin.variable` built-in.
489
493
If an attempt is made to change an inexistent variable or a test parameter, a warning will be issued.
Conversions to arbitrary objects are also supported.
512
516
See :class:`~reframe.utility.typecheck.ConvertibleType` for more details.
513
517
514
-
The optional ``TEST.`` prefix refers to the test class name, *not* the test name.
515
-
516
518
Variable assignments passed from the command line happen *before* the test is instantiated and is the exact equivalent of assigning a new value to the variable *at the end* of the test class body.
517
519
This has a number of implications that users of this feature should be aware of:
0 commit comments