baldertest 0.1.0b14__py3-none-any.whl → 0.1.2__py3-none-any.whl

_balder/_version.py

@@ -1,7 +1,14 @@
 # file generated by setuptools-scm
 # don't change, don't track in version control
 
-__all__ = ["__version__", "__version_tuple__", "version", "version_tuple"]
+__all__ = [
+    "__version__",
+    "__version_tuple__",
+    "version",
+    "version_tuple",
+    "__commit_id__",
+    "commit_id",
+]
 
 TYPE_CHECKING = False
 if TYPE_CHECKING:
@@ -9,13 +16,19 @@ if TYPE_CHECKING:
     from typing import Union
 
     VERSION_TUPLE = Tuple[Union[int, str], ...]
+    COMMIT_ID = Union[str, None]
 else:
     VERSION_TUPLE = object
+    COMMIT_ID = object
 
 version: str
 __version__: str
 __version_tuple__: VERSION_TUPLE
 version_tuple: VERSION_TUPLE
+commit_id: COMMIT_ID
+__commit_id__: COMMIT_ID
 
-__version__ = version = '0.1.0b14'
-__version_tuple__ = version_tuple = (0, 1, 0, 'b14')
+__version__ = version = '0.1.2'
+__version_tuple__ = version_tuple = (0, 1, 2)
+
+__commit_id__ = commit_id = None

_balder/executor/executor_tree.py

@@ -62,9 +62,10 @@ class ExecutorTree(BasicExecutableExecutor):
             self.update_inner_feature_reference_in_all_setups()
 
     def _body_execution(self, show_discarded):
-        for cur_setup_executor in self.get_setup_executors():
+        for cur_setup_executor in self.get_setup_executors(return_discarded=show_discarded):
             prev_mark = cur_setup_executor.prev_mark
-            if cur_setup_executor.has_runnable_tests(show_discarded) or cur_setup_executor.has_skipped_tests():
+            if cur_setup_executor.has_runnable_tests(consider_discarded_too=show_discarded) \
+                    or cur_setup_executor.has_skipped_tests():
                 cur_setup_executor.execute(show_discarded=show_discarded)
             elif prev_mark == PreviousExecutorMark.SKIP:
                 cur_setup_executor.set_result_for_whole_branch(ResultState.SKIP)
@@ -78,17 +79,30 @@ class ExecutorTree(BasicExecutableExecutor):
 
     # ---------------------------------- METHODS -----------------------------------------------------------------------
 
-    def get_setup_executors(self) -> List[SetupExecutor]:
-        """returns all setup executors of this tree"""
-        return self._setup_executors
+    def get_setup_executors(self, return_discarded=False) -> List[SetupExecutor]:
+        """
+        returns all setup executors of this tree
 
-    def get_all_scenario_executors(self) -> List[ScenarioExecutor]:
+        :param return_discarded: True if the method should return discarded variations too
+
+        :return: a list of relevant :class:`SetupExecutor`
+        """
+        if return_discarded:
+            return self._setup_executors
+
+        return [
+            cur_setup_executor
+            for cur_setup_executor in self._setup_executors
+            if len(cur_setup_executor.get_scenario_executors(return_discarded=False)) > 0
+        ]
+
+    def get_all_scenario_executors(self, return_discarded=False) -> List[ScenarioExecutor]:
         """
         returns a list with all scenario executors
         """
         all_scenario_executor = []
-        for cur_setup_executor in self.get_setup_executors():
-            all_scenario_executor += cur_setup_executor.get_scenario_executors()
+        for cur_setup_executor in self.get_setup_executors(return_discarded=return_discarded):
+            all_scenario_executor += cur_setup_executor.get_scenario_executors(return_discarded=return_discarded)
         return all_scenario_executor
 
     def get_all_variation_executors(self, return_discarded=False) -> List[VariationExecutor]:
@@ -96,7 +110,7 @@ class ExecutorTree(BasicExecutableExecutor):
         returns a list with all variation executors
         """
         all_variation_executor = []
-        for cur_scenario_executor in self.get_all_scenario_executors():
+        for cur_scenario_executor in self.get_all_scenario_executors(return_discarded=return_discarded):
             all_variation_executor += cur_scenario_executor.get_variation_executors(return_discarded=return_discarded)
         return all_variation_executor
 
@@ -136,9 +150,9 @@ class ExecutorTree(BasicExecutableExecutor):
 
     def cleanup_empty_executor_branches(self, consider_discarded=False):
         to_remove_executor = []
-        for cur_setup_executor in self.get_setup_executors():
+        for cur_setup_executor in self.get_setup_executors(return_discarded=consider_discarded):
             cur_setup_executor.cleanup_empty_executor_branches(consider_discarded=consider_discarded)
-            if len(cur_setup_executor.get_scenario_executors()) == 0:
+            if len(cur_setup_executor.get_scenario_executors(return_discarded=consider_discarded)) == 0:
                 # remove this whole executor because it has no children anymore
                 to_remove_executor.append(cur_setup_executor)
         for cur_setup_executor in to_remove_executor:
@@ -169,7 +183,7 @@ class ExecutorTree(BasicExecutableExecutor):
         print_line(start_text)
         # check if there exists runnable elements
         runnables = [cur_exec.has_runnable_tests(consider_discarded_too=show_discarded)
-                     for cur_exec in self.get_setup_executors()]
+                     for cur_exec in self.get_setup_executors(return_discarded=show_discarded)]
         one_or_more_runnable_setups = None if len(runnables) == 0 else max(runnables)
         if one_or_more_runnable_setups:
             super().execute(show_discarded=show_discarded)
@@ -189,8 +203,8 @@ class ExecutorTree(BasicExecutableExecutor):
     def print_tree(self, show_discarded=False) -> None:
         """this method is an auxiliary method which outputs the entire tree"""
         print("RESOLVING OVERVIEW", end="\n\n")
-        for cur_setup_executor in self.get_setup_executors():
-            for cur_scenario_executor in cur_setup_executor.get_scenario_executors():
+        for cur_setup_executor in self.get_setup_executors(return_discarded=show_discarded):
+            for cur_scenario_executor in cur_setup_executor.get_scenario_executors(return_discarded=show_discarded):
                 for cur_variation_executor in cur_scenario_executor.get_variation_executors(
                         return_discarded=show_discarded):
                     applicable = cur_variation_executor.prev_mark != PreviousExecutorMark.DISCARDED

_balder/executor/scenario_executor.py

@@ -99,7 +99,8 @@ class ScenarioExecutor(BasicExecutableExecutor):
     def _body_execution(self, show_discarded):
         for cur_variation_executor in self.get_variation_executors(return_discarded=show_discarded):
             prev_mark = cur_variation_executor.prev_mark
-            if cur_variation_executor.has_runnable_tests() or cur_variation_executor.has_skipped_tests():
+            if cur_variation_executor.has_runnable_tests(consider_discarded_too=show_discarded) \
+                    or cur_variation_executor.has_skipped_tests():
                 cur_variation_executor.execute(show_discarded=show_discarded)
             elif prev_mark == PreviousExecutorMark.SKIP:
                 cur_variation_executor.set_result_for_whole_branch(ResultState.SKIP)

_balder/executor/setup_executor.py

@@ -79,9 +79,10 @@ class SetupExecutor(BasicExecutableExecutor):
         print(f"SETUP {self.base_setup_class.__class__.__name__}")
 
     def _body_execution(self, show_discarded):
-        for cur_scenario_executor in self.get_scenario_executors():
+        for cur_scenario_executor in self.get_scenario_executors(return_discarded=show_discarded):
             prev_mark = cur_scenario_executor.prev_mark
-            if cur_scenario_executor.has_runnable_tests(show_discarded) or cur_scenario_executor.has_skipped_tests():
+            if cur_scenario_executor.has_runnable_tests(consider_discarded_too=show_discarded) \
+                    or cur_scenario_executor.has_skipped_tests():
                 cur_scenario_executor.execute(show_discarded=show_discarded)
             elif prev_mark == PreviousExecutorMark.SKIP:
                 cur_scenario_executor.set_result_for_whole_branch(ResultState.SKIP)
@@ -123,13 +124,26 @@ class SetupExecutor(BasicExecutableExecutor):
                     # object
                     setattr(cur_feature, cur_ref_feature_name, replacing_candidate)
 
-    def get_scenario_executors(self) -> List[ScenarioExecutor]:
-        """returns a list with all scenario executors that belongs to this setup executor"""
-        return self._scenario_executors
+    def get_scenario_executors(self, return_discarded=False) -> List[ScenarioExecutor]:
+        """
+        returns a list with all scenario executors that belongs to this setup executor
+
+        :param return_discarded: True if the method should return discarded variations too
+
+        :return: a list of relevant :class:`ScenarioExecutor`
+        """
+        if return_discarded:
+            return self._scenario_executors
+
+        return [
+            cur_scenario_executor
+            for cur_scenario_executor in self._scenario_executors
+            if len(cur_scenario_executor.get_variation_executors(return_discarded=False)) > 0
+        ]
 
     def cleanup_empty_executor_branches(self, consider_discarded=False):
         to_remove_executor = []
-        for cur_scenario_executor in self.get_scenario_executors():
+        for cur_scenario_executor in self.get_scenario_executors(return_discarded=consider_discarded):
             cur_scenario_executor.cleanup_empty_executor_branches(consider_discarded=consider_discarded)
             if len(cur_scenario_executor.get_variation_executors(return_discarded=consider_discarded)) == 0:
                 # remove this whole executor because it has no children anymore

_balder/executor/variation_executor.py

@@ -191,6 +191,7 @@ class VariationExecutor(BasicExecutableExecutor):
             # do nothing if this variation can not be applied (is discarded)
             return
 
+        self.restore_vdevice_feature_instances()
         self.restore_original_vdevice_references()
         self.revert_active_vdevice_device_mappings_in_all_features()
         self.revert_scenario_device_feature_instances()
@@ -614,6 +615,8 @@ class VariationExecutor(BasicExecutableExecutor):
     def restore_original_vdevice_references(self):
         """
         This method restores all previously exchanged :class:`VDevice` references to the original ones.
+
+        This method is the cleanup method for :meth:`VariationExecutor.exchange_unmapped_vdevice_references`.
         """
         all_devices = NormalScenarioSetupController.get_for(
             self.cur_scenario_class.__class__).get_all_abs_inner_device_classes()
@@ -633,10 +636,10 @@ class VariationExecutor(BasicExecutableExecutor):
         objects, will be replaced with the related feature instances of the mapped device object.
 
         .. note::
-            Note that this method expects that the true defined scenario features are already replaced with the real
-            setup features. In addition to that, the method expects, that the vDevice-Device mapping of every feature
-            was set to the resolved setup device! So the method requires that the method
-            `update_scenario_device_feature_instances()` was called before.
+            Note that this method expects that the defined scenario features instances are already replaced with the
+            current active setup features. In addition to that, the method expects, that the vDevice-Device mapping of
+            every feature was set to the resolved setup device! This means, the method
+            `update_scenario_device_feature_instances()` needs to be called before.
         """
         for scenario_device, _ in self._base_device_mapping.items():
             # these features are subclasses of the real defined one (because they are already the replaced ones)
@@ -662,6 +665,31 @@ class VariationExecutor(BasicExecutableExecutor):
                         # object
                         setattr(cur_vdevice, cur_vdevice_attr_name, replacing_candidate)
 
+    def restore_vdevice_feature_instances(self):
+        """
+        This method restores all previously exchanged :class:`VDevice` feature references to the original ones.
+
+        This method is the cleanup method for :meth:`VariationExecutor.update_vdevice_referenced_feature_instances`.
+
+        .. note::
+            Note that this method expects that the defined scenario features are still replaced with the active
+            setup features. In addition to that, the method expects, that the vDevice-Device mapping of every feature
+            is still set!
+
+        """
+        for scenario_device, _ in self._base_device_mapping.items():
+            # these features are subclasses of the real defined one (because they are already the replaced ones)
+            all_device_features = DeviceController.get_for(scenario_device).get_all_instantiated_feature_objects()
+            for _, cur_feature in all_device_features.items():
+                # now get the related vDevice class and update its attributes
+                cur_vdevice, cur_device = cur_feature.active_vdevice_device_mapping
+                if cur_vdevice is not None and cur_device is not None:
+                    cur_vdevice_controller = VDeviceController.get_for(cur_vdevice)
+                    original_features_of_cur_vdev = cur_vdevice_controller.get_original_instanced_feature_objects()
+
+                    for cur_vdev_attr_name, cur_vdev_orig_feature in original_features_of_cur_vdev.items():
+                        setattr(cur_vdevice, cur_vdev_attr_name, cur_vdev_orig_feature)
+
     def verify_applicability(self) -> None:
         """
         This method verifies if this variation is executable. First the method checks if all defined

_balder/solver.py

@@ -219,9 +219,6 @@ class Solver:
                 variation_executor = VariationExecutor(device_mapping=cur_device_mapping, parent=scenario_executor)
                 variation_executor.verify_applicability()
 
-                if not variation_executor.can_be_applied():
-                    continue
-
                 scenario_executor.add_variation_executor(variation_executor)
 
                 for cur_testcase in scenario_executor.base_scenario_controller.get_all_test_methods():

baldertest-0.1.2.dist-info/METADATA

@@ -0,0 +1,360 @@
+Metadata-Version: 2.4
+Name: baldertest
+Version: 0.1.2
+Summary: balder: reusable scenario based test framework
+Home-page: https://docs.balder.dev
+Author: Max Stahlschmidt and others
+License: MIT
+Project-URL: Source, https://github.com/balder-dev/balder
+Project-URL: Tracker, https://github.com/balder-dev/balder/issues
+Keywords: test,systemtest,reusable,scenario
+Platform: unix
+Platform: linux
+Platform: osx
+Platform: cygwin
+Platform: win32
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Operating System :: MacOS :: MacOS X
+Classifier: Operating System :: Microsoft :: Windows
+Classifier: Operating System :: POSIX
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Software Development :: Libraries
+Classifier: Topic :: Software Development :: Testing
+Classifier: Topic :: Utilities
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+
+<div align="center">
+  <img style="margin: 20px;max-width: 68%" src="https://docs.balder.dev/en/latest/_static/balder_w_boarder.png" alt="Balder logo">
+</div>
+
+Balder is a flexible Python test system that allows you to reuse test code written once for different but similar 
+platforms, devices, or applications. It enables you to install ready-to-use test cases and provides various test 
+development features that help you test your software or devices much faster.
+
+You can use shared test code by installing an [existing BalderHub project](https://hub.balder.dev), or you can create 
+your own. This makes test development for your project much faster, since it is oftentimes enough to install a BalderHub
+project and only provide the user-specific code.
+
+Be part of the progress and share your tests with others, your company, or the whole world.
+
+# Installation
+
+You can install the latest release with pip:
+
+```
+python -m pip install baldertest
+```
+
+# Run Balder
+
+After you've installed it, you can run Balder inside a Balder environment with the following command:
+
+```
+balder
+```
+
+You can also provide a specific path to the balder environment directory by using this console argument:
+
+```
+balder --working-dir /path/to/working/dir
+```
+
+# How does it work?
+
+Balder allows you to reuse previously written test code by dividing it into the components that **are needed** for a 
+test (`Scenario`) and the components that **you have** (`Setup`).
+
+You can define a test within a method of a `Scenario` class. This is often an abstract layer, where you only describe 
+the general business logic without providing any specific implementation details.
+
+These specific implementation details are provided in the `Setup` classes. They describe exactly **what you have**. In 
+these classes, you provide an implementation for the abstract elements that were defined earlier in the `Scenario`. 
+
+Balder then automatically searches for matching mappings and runs your tests using them.
+
+## Define the `Scenario` class
+
+Inside `Scenario` or `Setup` classes, you can describe the environment using inner `Device` classes. For example, let's 
+write a test that validates the functionality of a lamp. For that, keep in mind that we want to make this test as 
+flexible as possible. It should be able to run with all kind of things that have a lamp:
+
+```python
+import balder
+from lib.scenario_features import BaseLightFeature
+
+
+class ScenarioLight(balder.Scenario):
+    
+    # The device with its features that are required for this test
+    class LightSpendingDevice(balder.Device):
+        light = BaseLightFeature()
+    
+    def test_check_light(self):
+        self.LightSpendingDevice.light.switch_on()
+        assert self.LightSpendingDevice.light.light_is_on()
+        self.LightSpendingDevice.light.switch_off()
+        assert not self.LightSpendingDevice.light.light_is_on()
+        
+    
+
+```
+
+Here, we have defined that a `LightSpendingDevice` **needs to have** a feature called `BaseLightFeature` so that this 
+scenario can be executed.
+
+We have also added a test case (named with a `test_*()` prefix) called `test_check_light`, which executes the validation
+of a lamp, by switching it on and off and checking its state.
+
+**Note:** The `BaseLightFeature` is an abstract Feature class that defines the abstract methods `switch_on()`, 
+`switch_off()`, and `light_is_on()`.
+
+
+## Define the `Setup` class
+
+The next step is defining a `Setup` class, which describes what we have. For a `Scenario` to match a `Setup`, the 
+features of all scenario devices must be implemented by the mapped setup devices.
+
+For example, if we want to test a car that includes a lamp, we could have a setup like the one shown below:
+
+```python
+import balder
+from lib.setup_features import CarEngineFeature, CarLightFeature
+
+
+class SetupGarage(balder.Setup):
+    
+    class Car(balder.Device):
+        car_engine = CarEngineFeature()
+        car_light = CarLightFeature() # subclass of `lib.scenario_feature.BaseLightFeature`
+        ...
+    
+
+```
+
+When you run Balder in this environment, it will collect the `ScenarioLight` and the `SetupMyCar` classes and try to 
+find mappings between them. Based on the `ScenarioLight`, Balder looks for a device that provides an implementation of 
+the single `BaseLightFeature`. To do this, it scans all available setups. Since the `SetupMyCar.Car` device provides an 
+implementation through the `CarLightFeature`, this device will match.
+
+```shell
++----------------------------------------------------------------------------------------------------------------------+
+| BALDER Testsystem                                                                                                    |
+|  python version 3.10.12 (main, Aug 15 2025, 14:32:43) [GCC 11.4.0] | balder version 0.1.0b14                         |
++----------------------------------------------------------------------------------------------------------------------+
+Collect 1 Setups and 1 Scenarios
+  resolve them to 1 valid variations
+
+================================================== START TESTSESSION ===================================================
+SETUP SetupGarage
+  SCENARIO ScenarioLight
+    VARIATION ScenarioLight.LightSpendingDevice:SetupGarage.Car
+      TEST ScenarioLight.test_check_light [.]
+================================================== FINISH TESTSESSION ==================================================
+TOTAL NOT_RUN: 0 | TOTAL FAILURE: 0 | TOTAL ERROR: 0 | TOTAL SUCCESS: 1 | TOTAL SKIP: 0 | TOTAL COVERED_BY: 0
+```
+
+## Add another Device to the `Setup` class
+
+Now the big advantage of Balder comes into play. We can run our test with all devices that can implement the 
+`BaseLightFeature`, independent of how this will be implemented in detail. **You do not need to rewrite the test**.
+
+So, We have more devices in our garage. So let's add them:
+
+```python
+import balder
+from lib.setup_features import CarEngineFeature, CarLightFeature, PedalFeature, BicycleLightFeature, GateOpenerFeature
+
+
+class SetupGarage(balder.Setup):
+    
+    class Car(balder.Device):
+        car_engine = CarEngineFeature()
+        car_light = CarLightFeature() # subclass of `lib.scenario_feature.BaseLightFeature`
+        ...
+    
+    class Bicycle(balder.Device):
+        pedals = PedalFeature()
+        light = BicycleLightFeature() # another subclass of `lib.scenario_feature.BaseLightFeature`
+        
+    class GarageGate(balder.Device):
+        opener = GateOpenerFeature()
+
+```
+
+If we run Balder now, it will find more mappings because the `Bicycle` device also provides an implementation for the 
+`BaseLightFeature` we are looking for.
+
+```shell
++----------------------------------------------------------------------------------------------------------------------+
+| BALDER Testsystem                                                                                                    |
+|  python version 3.10.12 (main, Aug 15 2025, 14:32:43) [GCC 11.4.0] | balder version 0.1.0b14                         |
++----------------------------------------------------------------------------------------------------------------------+
+Collect 1 Setups and 1 Scenarios
+  resolve them to 2 valid variations
+
+================================================== START TESTSESSION ===================================================
+SETUP SetupGarage
+  SCENARIO ScenarioLight
+    VARIATION ScenarioLight.LightSpendingDevice:SetupGarage.Bicycle
+      TEST ScenarioLight.test_check_light [.]
+    VARIATION ScenarioLight.LightSpendingDevice:SetupGarage.Car
+      TEST ScenarioLight.test_check_light [.]
+================================================== FINISH TESTSESSION ==================================================
+TOTAL NOT_RUN: 0 | TOTAL FAILURE: 0 | TOTAL ERROR: 0 | TOTAL SUCCESS: 2 | TOTAL SKIP: 0 | TOTAL COVERED_BY: 0
+```
+
+Balder handles all of this for you. You only need to describe your environment by defining `Scenario` and `Setup` 
+classes, then provide the specific implementations by creating the features. Balder will automatically search for and 
+apply the mappings between them.
+
+**NOTE:** Balder offers many more elements to design complete device structures, including connections between multiple 
+devices.
+
+You can learn more about that in the 
+[Tutorial Section of the Documentation](https://docs.balder.dev/en/latest/tutorial_guide/index.html).
+
+
+# Example: Use an installable BalderHub package
+
+With Balder, you can create custom test environments or install open-source-available test packages, known as 
+[BalderHub packages](https://hub.balder.dev). For example, if you want to test the login functionality of a website, simply use the 
+ready-to-use scenario `ScenarioSimpleLogin` from the [`balderhub-auth` package](https://hub.balder.dev/projects/auth/en/latest/examples.html), 
+
+
+We want to use [Selenium](https://www.selenium.dev/) to control the browser and of course use html elements, so let's install 
+`balderhub-selenium` and `balderhub-html` right away.
+
+```
+$ pip install balderhub-auth balderhub-selenium balderhub-html
+```
+
+So as mentioned, you don't need to define a scenario and a test yourself; you can simply import it:
+
+```python
+# file `scenario_balderhub.py`
+
+from balderhub.auth.scenarios import ScenarioSimpleLogin
+
+```
+
+According to the [documentation of this BalderHub project](https://hub.balder.dev/projects/auth/en/latest/examples.html), 
+we only need to define the login page by overwriting the ``LoginPage`` feature:
+
+```python
+
+# file `lib/pages.py`
+
+import balderhub.auth.contrib.html.pages
+from balderhub.html.lib.utils import Selector
+from balderhub.url.lib.utils import Url
+import balderhub.html.lib.utils.components as html
+
+
+class LoginPage(balderhub.auth.contrib.html.pages.LoginPage):
+
+    url = Url('https://example.com')
+
+    # Overwrite abstract property
+    @property
+    def input_username(self):
+            return html.inputs.HtmlTextInput.by_selector(self.driver, Selector.by_name('user'))
+
+    # Overwrite abstract property
+    @property
+    def input_password(self):
+        return html.inputs.HtmlPasswordInput.by_selector(self.driver, Selector.by_name('user'))
+
+    # Overwrite abstract property
+    @property
+    def btn_login(self):
+        return html.HtmlButtonElement.by_selector(self.driver, Selector.by_id('submit-button'))
+
+```
+
+And use it in our setup:
+
+```python
+
+
+# file `setups/setup_office.py`
+
+import balder
+import balderhub.auth.lib.scenario_features.role
+from balderhub.selenium.lib.setup_features import SeleniumChromeWebdriverFeature
+
+from lib.pages import LoginPage
+
+class UserConfig(balderhub.auth.lib.scenario_features.role.UserRoleFeature):
+    # provide the credentials for the log in
+        username = 'admin'
+        password = 'secret'
+
+class SetupOffice(balder.Setup):
+
+    class Server(balder.Device):
+        user = UserConfig()
+
+    class Browser(balder.Device):
+        selenium = SeleniumChromeWebdriverFeature()
+        page_login = LoginPage()
+
+    # fixture to prepare selenium - will be executed before the test session runs
+    @balder.fixture('session')
+    def selenium(self):
+        self.Browser.selenium.create()
+        yield
+        self.Browser.selenium.quit()
+```
+
+When you run Balder now, it will execute a complete login test that you didn't write yourself - 
+**it was created by the open-source community**.
+
+```shell
++----------------------------------------------------------------------------------------------------------------------+
+| BALDER Testsystem                                                                                                    |
+|  python version 3.10.12 (main, Aug 15 2025, 14:32:43) [GCC 11.4.0] | balder version 0.1.0b14                         |
++----------------------------------------------------------------------------------------------------------------------+
+Collect 1 Setups and 1 Scenarios
+  resolve them to 1 valid variations
+
+================================================== START TESTSESSION ===================================================
+SETUP SetupOffice
+  SCENARIO ScenarioSimpleLogin
+    VARIATION ScenarioSimpleLogin.Client:SetupOffice.Browser | ScenarioSimpleLogin.System:SetupOffice.Server
+      TEST ScenarioSimpleLogin.test_login [.]
+================================================== FINISH TESTSESSION ==================================================
+TOTAL NOT_RUN: 0 | TOTAL FAILURE: 0 | TOTAL ERROR: 0 | TOTAL SUCCESS: 1 | TOTAL SKIP: 0 | TOTAL COVERED_BY: 0
+```
+
+If you'd like to learn more about it, feel free to dive [into the documentation](https://balder.dev).
+
+# Contribution guidelines
+
+Any help is appreciated. If you want to contribute to balder, take a look into the 
+[contribution guidelines](https://github.com/balder-dev/balder/blob/main/CONTRIBUTING.md).
+
+Are you an expert in your field? Do you enjoy the concept of balder? How about creating your own
+BalderHub project? You can contribute to an existing project or create your own. If you are not sure, a project for 
+your idea already exists or if you want to discuss your ideas with others, feel free to
+[create an issue in the BalderHub main entry project](https://github.com/balder-dev/hub.balder.dev/issues) or
+[start a new discussion](https://github.com/balder-dev/hub.balder.dev/discussions).
+
+# License
+
+Balder is free and Open-Source
+
+Copyright (c) 2022-2025 Max Stahlschmidt and others
+
+Distributed under the terms of the MIT license

{baldertest-0.1.0b14.dist-info → baldertest-0.1.2.dist-info}/RECORD

@@ -1,5 +1,5 @@
 _balder/__init__.py,sha256=Qk4wkVInPlXLFV36Yco5K7PDawJoeeWQVakzj6g5pmA,195
-_balder/_version.py,sha256=g5k4tbPdhrhEa3D2X-tMb0NvEt7IbfLQzEQ3Vp3Tq9w,521
+_balder/_version.py,sha256=Ok5oAXdWgR9aghaFXTafTeDW6sYO3uVe6d2Nket57R4,704
 _balder/balder_plugin.py,sha256=EQzJP1dwwVDydhMLJtAmTCXOczlDuXBJur05lalmK_k,3136
 _balder/balder_session.py,sha256=ezT86gC_VzPQZOQ4r5qQ75IEm6rXZHiIpEqZDczkRsE,16149
 _balder/balder_settings.py,sha256=U96PVep7dGSaTXrMfeZMYf6oCIcEDPEqrBlFcoX476s,582
@@ -31,7 +31,7 @@ _balder/previous_executor_mark.py,sha256=gwpGu7d-kwPzQT8CmaPfuEG6fess2Upf5Q-zX6O
 _balder/routing_path.py,sha256=icIp09sC51sBsNHZPrWzGOtLqrOT5Se_dj0Db7MwtwY,17093
 _balder/scenario.py,sha256=beHkEqb9pnhrMOt1qfgATSBWVfHahw9RsOCT-uxK6TE,954
 _balder/setup.py,sha256=sIyuqhDSCzxtkWXW48jRrLDvGWkZwgpL6NvEKrFM65E,890
-_balder/solver.py,sha256=NbpAdvrGWdJTY6eZmNZFr7YDubyggY0yW64rDB3JkT0,13121
+_balder/solver.py,sha256=eB7pf9224AJAbeF4HlMDHMMy06mmq3C-LiyX4NBlphw,13031
 _balder/testresult.py,sha256=AE_LWCwmR9aR36IHfPARaaqossBahv-P2URCZ8cFAvM,6893
 _balder/unmapped_vdevice.py,sha256=oKr01YVTLViWtZkYz8kx8ccTx-KmwgNrHuQqqD4eLQw,513
 _balder/vdevice.py,sha256=fc2xuMnTuN1RyfWh9mqFgLdSO9yGA75eERobTXUQ9JA,215
@@ -53,13 +53,13 @@ _balder/controllers/vdevice_controller.py,sha256=rWK3oHzXbNlgXf0xbWyssDevx0qQ7Bm
 _balder/executor/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 _balder/executor/basic_executable_executor.py,sha256=RWwc8c4B7qO2BxlUB8dZH9IC64qm_KWh8tGCoBB8v6o,5395
 _balder/executor/basic_executor.py,sha256=6rLSBrTGodlaRVfHV2kpXPjbAqUPEq9-2txCxz_-fXg,9327
-_balder/executor/executor_tree.py,sha256=CfwUDUAgCb_k_haaqX7GC23DB2LLEpkL-NnSCEdufiA,10659
+_balder/executor/executor_tree.py,sha256=ZyZYRyeOjvZEW_BRds9Ujfa3TrNxa_ouAGRsLNoSVwk,11457
 _balder/executor/parametrized_testcase_executor.py,sha256=Wk4XitAVOMGU7pSn7AOyvOsuL9CorcqFJ-iRuVtat1M,2149
-_balder/executor/scenario_executor.py,sha256=tfQ1tKvmhAUgUkAcgJ94hI46hLcXAhIMD-d9qCmJiXg,8152
-_balder/executor/setup_executor.py,sha256=QWMWhfzsssRT_fHOUKjw4gHfC2CaZjhL5NxF1eNl35w,8604
+_balder/executor/scenario_executor.py,sha256=NMx4hJpY5Xtsd4ugrQTdX4bcczgi_aabtlqHIkMfXl8,8211
+_balder/executor/setup_executor.py,sha256=-nLTH0enq7IbWMlXPZF_sY5Mt78aDesMkFpco6qU8uM,9167
 _balder/executor/testcase_executor.py,sha256=Yrifk_8hsm1KKrE6udd84EyBywmWiUN00MlcezMQ7xA,8216
 _balder/executor/unresolved_parametrized_testcase_executor.py,sha256=Pb-LhEFNspb03pYTqTyFvSWPFMoRCjO8OVjjP2rHFMw,7628
-_balder/executor/variation_executor.py,sha256=2VLXmPmRVFi69bkqVkHaz055l5OEPMNer1qSKD3SN9M,51515
+_balder/executor/variation_executor.py,sha256=wdWOIuXqkxsl-wifuEFWYaH_hLuvaYjvotdVPMM2g8I,53252
 _balder/objects/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 _balder/objects/connections/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 _balder/objects/connections/osi_1_physical.py,sha256=74lKWJd6ETEtvNXH0_dmTbkZlStJ_af218pQkUht0aA,2189
@@ -81,9 +81,9 @@ balder/connections.py,sha256=H6rf7UsiVY_FeZLngZXCT9WDw9cQqpiDiPbz_0J4yjM,2331
 balder/devices.py,sha256=zupHtz8yaiEjzR8CrvgZU-RzsDQcZFeN5mObfhtjwSw,173
 balder/exceptions.py,sha256=iaR4P2L7K3LggYSDnjCGLheZEaGgnMilxDQdoYD5KHQ,1954
 balder/parametrization.py,sha256=R8U67f6DEnXdDc9cGOgS8yFTEAfhglv1v9mnAUAExUg,150
-baldertest-0.1.0b14.dist-info/licenses/LICENSE,sha256=Daz9qTpqbiq-klWb2Q9lYOmn3rJ5oIQnbs62sGcqOZ4,1084
-baldertest-0.1.0b14.dist-info/METADATA,sha256=4jKylhMf05-alO4ThYvff56kssjzuh6dWMcobpMAUpE,15806
-baldertest-0.1.0b14.dist-info/WHEEL,sha256=Nw36Djuh_5VDukK0H78QzOX-_FQEo6V37m3nkm96gtU,91
-baldertest-0.1.0b14.dist-info/entry_points.txt,sha256=hzqu_nrMKTCi5IJqzS1fhIXWEiL7mTGZ-kgj2lUYlRU,65
-baldertest-0.1.0b14.dist-info/top_level.txt,sha256=RUkIBkNLqHMemx2C9aEpoS65dpqb6_jU-oagIPxGQEA,15
-baldertest-0.1.0b14.dist-info/RECORD,,
+baldertest-0.1.2.dist-info/licenses/LICENSE,sha256=kNB2-kpqR9c3rEyXsMaQiqb1jiLZ5j6R6TSda63dcJY,1089
+baldertest-0.1.2.dist-info/METADATA,sha256=OI7I2-tt0pTFpfxF95nOODxncv8y0XAXv61JWuJV0Eo,14730
+baldertest-0.1.2.dist-info/WHEEL,sha256=wUyA8OaulRlbfwMtmQsvNngGrxQHAvkKcvRmdizlJi0,92
+baldertest-0.1.2.dist-info/entry_points.txt,sha256=hzqu_nrMKTCi5IJqzS1fhIXWEiL7mTGZ-kgj2lUYlRU,65
+baldertest-0.1.2.dist-info/top_level.txt,sha256=RUkIBkNLqHMemx2C9aEpoS65dpqb6_jU-oagIPxGQEA,15
+baldertest-0.1.2.dist-info/RECORD,,

{baldertest-0.1.0b14.dist-info → baldertest-0.1.2.dist-info}/WHEEL

@@ -1,5 +1,5 @@
 Wheel-Version: 1.0
-Generator: setuptools (80.7.1)
+Generator: setuptools (80.10.2)
 Root-Is-Purelib: true
 Tag: py3-none-any
 

{baldertest-0.1.0b14.dist-info → baldertest-0.1.2.dist-info}/licenses/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2022 Max Stahlschmidt and others
+Copyright (c) 2022-2025 Max Stahlschmidt and others
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

baldertest-0.1.0b14.dist-info/METADATA

@@ -1,389 +0,0 @@
-Metadata-Version: 2.4
-Name: baldertest
-Version: 0.1.0b14
-Summary: balder: reusable scenario based test framework
-Home-page: https://docs.balder.dev
-Author: Max Stahlschmidt and others
-License: MIT
-Project-URL: Source, https://github.com/balder-dev/balder
-Project-URL: Tracker, https://github.com/balder-dev/balder/issues
-Keywords: test,systemtest,reusable,scenario
-Platform: unix
-Platform: linux
-Platform: osx
-Platform: cygwin
-Platform: win32
-Classifier: License :: OSI Approved :: MIT License
-Classifier: Operating System :: MacOS :: MacOS X
-Classifier: Operating System :: Microsoft :: Windows
-Classifier: Operating System :: POSIX
-Classifier: Intended Audience :: Developers
-Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3 :: Only
-Classifier: Programming Language :: Python :: 3.9
-Classifier: Programming Language :: Python :: 3.10
-Classifier: Topic :: Software Development :: Libraries
-Classifier: Topic :: Software Development :: Testing
-Classifier: Topic :: Utilities
-Requires-Python: >=3.9
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Dynamic: license-file
-
-
-<div align="center">
-  <img style="margin: 20px;max-width: 68%" src="https://docs.balder.dev/en/latest/_static/balder_w_boarder.png" alt="Balder logo">
-</div>
-
-Balder is a very powerful, universal and flexible python test system that allows you to reuse a once written testcode as 
-efficiently as possible for different but similar platforms/devices/applications. Balder's goal is
-being a platform for combining the single steps of defining, developing and documenting the entire test 
-process while using test scenarios which can be reused across different projects.
-
-You can share your own testcode by creating a new BalderHub project, or you use an 
-[existing BalderHub project](https://hub.balder.dev), by simply installing and using it. This makes the test development 
-for your project much faster, since it is often times enough to only provide the user-specific code.
-
-Be part of the progress and share your tests with others, your company or the whole world.
-
-# Installation
-
-You can install the latest release with pip:
-
-```
-python -m pip install baldertest
-```
-
-# Run Balder
-
-After you've installed it, you can run Balder inside a Balder environment with the following command:
-
-```
-balder
-```
-
-You can also provide a specific path to the balder environment directory by using this console argument:
-
-```
-balder --working-dir /path/to/working/dir
-```
-
-# How does it work?
-
-Balder allows you to reuse previously written test code by dividing it into the components that **are needed** for a 
-test (`Scenario`) and the components that **we have** (`Setup`).
-
-`Scenario` classes define a test. Only describe the most important aspects **you need** for the execution of the 
-corresponding test (method of the scenario class) inside `Scenario` classes. Often it is enough to define abstract 
-methods in the scenario-level features.
-
-In contrast, `Setup` classes describe exactly what **you have**. This is where you define all the devices and their 
-features. Balder will then automatically search for mappings and run your test with them.
-
-## Define the `Scenario` class
-
-Inside `Scenario` or `Setup` classes, inner `Device` classes describe your environment. For example, if you want to test 
-the process of sending a message between two devices, you can create a `Scenario` like shown below:
-
-```python
-import balder
-from .features import SendMessageFeature, RecvMessageFeature
-
-
-class ScenarioMessaging(balder.Scenario):
-    
-    class Sender(balder.Device):
-        send = SendMessageFeature()
-    
-    @balder.connect(Sender, over_connection=balder.Connection())
-    class Receiver(balder.Device):
-        recv = RecvMessageFeature()
-        
-    
-
-```
-
-You have now defined, that the `Sender` device must be able to send messages (has `SendMessageFeature()`), while 
-the `Receiver` device must be able to receive messages (has `RecvMessageFeature()`). Both devices are connected with 
-each other. For this we use the general connection `balder.Connection()`, which allows every type of connection.
-
-You can implement your test, by adding a new method that starts with `test_*()`:
-
-```python
-import balder
-from .features import SendMessageFeature, RecvMessageFeature
-
-
-class ScenarioMessaging(balder.Scenario):
-    
-    class Sender(balder.Device):
-        send = SendMessageFeature()
-    
-    @balder.connect(Sender, over_connection=balder.Connection())
-    class Receiver(balder.Device):
-        recv = RecvMessageFeature()
-        
-    def test_send_msg(self):
-        MESSAGE_TXT = "Hello World"
-        self.Sender.send.send_msg(MESSAGE_TXT)
-        received_msg = self.Receiver.recv.get_last_received_msg()
-        assert received_msg == MESSAGE_TXT
-
-```
-
-## Define the `Setup` class
-
-The next step is defining a `Setup` class, which describes what we have. For a `Scenario` to match a `Setup`, all of 
-your scenario-devices must be able to map to a sub selection of some setup-devices. 
-
-For example, if you want to verify if your DUT is able to receive messages from your computer (both are connected over 
-USB), just create a `Setup` class with the both devices `Computer` and `Dut` and add an implementation (subclasses) of 
-our previously defined feature classes `SendMessageFeature` and `RecvMessageFeature` to them:
-
-```python
-import balder
-from balder import connections as cnns
-from .setup_features import SendUsbMessageFeature, RecvUsbMessageFeature
-
-
-class SetupOverUsb(balder.Setup):
-    
-    class Computer(balder.Device):
-        # non-abstract subclass of `SendMessageFeature`
-        send = SendUsbMessageFeature()
-    
-    @balder.connect(Computer, over_connection=cnns.UsbConnection())
-    class Dut(balder.Device):
-        # non-abstract subclass of `RecvMessageFeature`
-        recv = RecvUsbMessageFeature()
-
-```
-
-With the features `SendUsbMessageFeature` and `RecvUsbMessageFeature`, both devices hold an implementation of our 
-previous scenario-level features `SendMessageFeature` and `RecvMessageFeature`. They are the child classes of our
-scenario-level features and hold the full implementation for sending/receiving data over USB.
-
-As soon as you run Balder, Balder will automatically detect that our scenario `ScenarioMessaging` can be mapped to the 
-`SetupOverUsb`. This will cause Balder to run the test `test_send_msg()` with the implemented setup-level version of 
-the features.
-
-The big advantage of Balder is the reusability. If you want to test if the communication also works in the other 
-direction, just add the features inverted:
-
-```python
-import balder
-from balder import connections as cnns
-from .setup_features import SendUsbMessageFeature, RecvUsbMessageFeature
-
-
-class SetupOverUsb(balder.Setup):
-    
-    class Computer(balder.Device):
-        # non-abstract subclass of `SendMessageFeature`
-        send = SendUsbMessageFeature()
-        # non-abstract subclass of `RecvMessageFeature`
-        recv = RecvUsbMessageFeature()
-    
-    @balder.connect(Computer, over_connection=cnns.UsbConnection())
-    class Dut(balder.Device):
-        # non-abstract subclass of `SendMessageFeature`
-        send = SendUsbMessageFeature()
-        # non-abstract subclass of `RecvMessageFeature`
-        recv = RecvUsbMessageFeature()
-
-```
-
-Balder will now run the test once with the `Computer` being the sender and once with the `Dut` being the Sender, even 
-though you didn't implement anything new.
-
-|             | `ScenarioMessaging.Sender` | `ScenarioMessaging.Sender` |
-|-------------|----------------------------|----------------------------|
-| VARIATION 1 | `SetupOverUsb.Computer`    | `SetupOverUsb.Dut`         |
-| VARIATION 2 | `SetupOverUsb.Dut`         | `SetupOverUsb.Computer`    |
-
-Do you have another device, that should be tested too? Just add it to your setup:
-
-```python
-import balder
-from balder import connections as cnns
-from .setup_features import SendUsbMessageFeature, RecvUsbMessageFeature
-
-
-class SetupOverUsb(balder.Setup):
-    
-    class Computer(balder.Device):
-        # non-abstract subclass of `SendMessageFeature`
-        send = SendUsbMessageFeature()
-        # non-abstract subclass of `RecvMessageFeature`
-        recv = RecvUsbMessageFeature()
-    
-    @balder.connect(Computer, over_connection=cnns.UsbConnection())
-    class Dut(balder.Device):
-        # non-abstract subclass of `SendMessageFeature`
-        send = SendUsbMessageFeature()
-        # non-abstract subclass of `RecvMessageFeature`
-        recv = RecvUsbMessageFeature()
-        
-    @balder.connect(Computer, over_connection=cnns.UsbConnection())
-    class AnotherDut(balder.Device):
-        # non-abstract subclass of `RecvMessageFeature`
-        recv = RecvUsbMessageFeature()
-
-```
-
-Now balder will run our scenario once each with the following mappings:
-
-|             | `ScenarioMessaging.Sender` | `ScenarioMessaging.Sender` |
-|-------------|----------------------------|----------------------------|
-| VARIATION 1 | `SetupOverUsb.Computer`    | `SetupOverUsb.Dut`         |
-| VARIATION 2 | `SetupOverUsb.Dut`         | `SetupOverUsb.Computer`    |
-| VARIATION 3 | `SetupOverUsb.Computer`    | `SetupOverUsb.AnotherDut`  |
-
-If you want to test a `Dut` device that does not use USB for communication, you can also add other feature 
-implementations of ``SendMessageFeature`` and ``RecvMessageFeature`` in your setup devices. For this we just add a new 
-setup:
-
-```python
-import balder
-from balder import connections as cnns
-from .setup_features import SendUsbMessageFeature, RecvUsbMessageFeature, SendBluetoothMessageFeature, RecvBluetoothMessageFeature
-
-
-class SetupOverUsb(balder.Setup):
-    
-    ...
-
-class SetupOverBluetooth(balder.Setup):
-    class Computer(balder.Device):
-        # non-abstract subclass of `SendMessageFeature`
-        send = SendBluetoothMessageFeature()
-    
-    @balder.connect(Computer, over_connection=cnns.BluetoothConnection)
-    class Dut(balder.Device):
-        # non-abstract subclass of `RecvMessageFeature`
-        recv = RecvBluetoothMessageFeature()
-
-```
-
-If you now execute Balder, it will run the scenario with all possible device constellations of the `SetupOverUsb` and 
-the `SetupOverBluetooth`. 
-
-|             | `ScenarioMessaging.Sender`      | `ScenarioMessaging.Sender` |
-|-------------|---------------------------------|----------------------------|
-| VARIATION 1 | `SetupOverUsb.Computer`         | `SetupOverUsb.Dut`         |
-| VARIATION 2 | `SetupOverUsb.Dut`              | `SetupOverUsb.Computer`    |
-| VARIATION 3 | `SetupOverUsb.Computer`         | `SetupOverUsb.AnotherDut`  |
-| VARIATION 4 | `SetupOverBluetooth.Computer`   | `SetupOverBluetooth.Dut`   |
-
-NOTE: *You could also add all of these devices in a shared setup and use one common feature for both protocols, but for this you would need to use VDevices. You can read more about this in [the documentation section about VDevices](https://docs.balder.dev/en/latest/basics/vdevices.html)*
-
-
-# Example: Use an installable BalderHub package
-
-With Balder you can create custom test environments or install open source available test packages, so called 
-[BalderHub packages](https://hub.balder.dev). If you want to test a SNMP client device for example, you can use the 
-[package balderhub-snmpagent](https://github.com/balder-dev/balderhub-snmpagent). Just install it with:
-
-```
-$ pip install balderhub-snmpagent
-```
-
-You only need to provide two things: The configuration of your DUT as subclass of `SnmpSystemConfig` and your 
-environment (the `Setup` class):
-
-```python
-# file `features.py`
-from balderhub.snmpagent.lib import features
-
-class MySnmpSystemConfig(features.SnmpSystemConfig):
-
-    host = "192.168.178.28"
-    sys_descr = "my fancy sysDescr"
-    sys_object_id = "1.3.6.1.4.1.1234.2.3.9.1"
-    read_community = "public"
-    write_community = "public"
-
-```
-
-```python
-# file `setup_example.py`
-import balder
-from balderhub.snmpagent.lib.connections import SnmpConnection
-from balderhub.snmpagent.lib.features import HasSnmpSystemGroupFeature
-from balderhub.snmpagent.lib.setup_features import SendSnmpGetRequestPysnmpFeature, SendSnmpSetRequestPysnmpFeature
-from . import features as setup_features
-
-
-class SetupPrinter(balder.Setup):
-
-    class Printer(balder.Device):
-        _snmp_sys = HasSnmpSystemGroupFeature()
-        config = setup_features.SnmpSystemConfig()
-
-    @balder.connect(Printer, over_connection=SnmpConnection())
-    class HostPc(balder.Device):
-        get_request_snmp = SendSnmpGetRequestPysnmpFeature()
-        set_request_snmp = SendSnmpSetRequestPysnmpFeature()
-
-```
-
-Call Balder in your project:
-
-```
-$ balder
-```
-
-And all existing and matching tests in [balderhub-snmpagent](https://github.com/balder-dev/balderhub-snmpagent) will 
-then be executed for you:
-
-```
-+----------------------------------------------------------------------------------------------------------------------+
-| BALDER Testsystem                                                                                                    |
-|  python version 3.10.6 (main, Mar 10 2023, 10:55:28) [GCC 11.3.0] | balder version 0.1.0b6                           |
-+----------------------------------------------------------------------------------------------------------------------+
-Collect 1 Setups and 3 Scenarios
-  resolve them to 3 mapping candidates
-
-================================================== START TESTSESSION ===================================================
-SETUP SetupPrinter
-  SCENARIO ScenarioMibSysDescr
-    VARIATION ScenarioMibSysDescr.SnmpAgent:SetupPrinter.Printer | ScenarioMibSysDescr.SnmpManager:SetupPrinter.HostPc
-      TEST ScenarioMibSysDescr.test_get_sys_descr [.]
-      TEST ScenarioMibSysDescr.test_get_sys_descr_ascii_check [.]
-      TEST ScenarioMibSysDescr.test_set_sys_descr [.]
-  SCENARIO ScenarioMibSysObjectId
-    VARIATION ScenarioMibSysObjectId.SnmpAgent:SetupPrinter.Printer | ScenarioMibSysObjectId.SnmpManager:SetupPrinter.HostPc
-      TEST ScenarioMibSysObjectId.test_get_sys_object_id [.]
-      TEST ScenarioMibSysObjectId.test_set_sys_object_id [.]
-  SCENARIO ScenarioMibSysUpTime
-    VARIATION ScenarioMibSysUpTime.SnmpAgent:SetupPrinter.Printer | ScenarioMibSysUpTime.SnmpManager:SetupPrinter.HostPc
-      TEST ScenarioMibSysUpTime.test_get_sys_up_time [.]
-      TEST ScenarioMibSysUpTime.test_get_sys_up_time_changed_check [.]
-      TEST ScenarioMibSysUpTime.test_set_sys_up_time [.]
-================================================== FINISH TESTSESSION ==================================================
-TOTAL NOT_RUN: 0 | TOTAL FAILURE: 0 | TOTAL ERROR: 0 | TOTAL SUCCESS: 8 | TOTAL SKIP: 0 | TOTAL COVERED_BY: 0
-```
-
-
-# Contribution guidelines
-
-Any help is appreciated. If you want to contribute to balder, take a look into the 
-[contribution guidelines](https://github.com/balder-dev/balder/blob/main/CONTRIBUTING.md).
-
-Balder is still in its early steps. Unfortunately, this also means that we don't have a broad variety of 
-[BalderHub projects](https://hub.balder.dev) at the moment. 
-
-Are you an expert in your field? Do you enjoy the concept of balder? How about you create your own
-BalderHub project? Take a look into our [Balder GitHub Group](https://github.com/balder-dev) and feel free to share 
-your ideas. You can contribute to an existing project or create your own. If you are not sure, a project for your idea 
-already exists or if you want to discuss your ideas with others, feel free to
-[create an issue in the BalderHub main entry project](https://github.com/balder-dev/hub.balder.dev/issues) or
-[start a new discussion](https://github.com/balder-dev/hub.balder.dev/discussions).
-
-# License
-
-Balder is free and Open-Source
-
-Copyright (c) 2022 Max Stahlschmidt and others
-
-Distributed under the terms of the MIT license