action #109789
Updated by szarate about 2 years ago
n order to understand better what parts of the Operating System are we testing, we need to know what packages are being installed during the lifecycle of a job. This will allow a PO, a QE Engineer, PM, or Release Manager to make a more informed decision when it comes to an ECO, or a feature, by allowing us to answer: - Are we testing this? - What version is currently available? - What tests are using this?. Since we have two places where packages are handled, one being the zypper log, and another being calls to zypper_call. While this doesn't guarantee that we know for sure - Task: write a package is being directly tested, we do know that a package will be at least indirectly tested if it's being pulled as a dependency. Later, we will look into putting that data to use, in a document database (likely) ## Acceptance criteria 1. Write a hook in zypper_call to log in a variable: test_module and package installed or removed (and exports it, in a json, yaml or similar format, easy to parse by machine) 2. - Task: Write test module that exports the zypper log (Packages installed + packages removed) at the end of the test 3. The package information extractor is test, scheduled in the default scenarios and extra_test_* scenarios on OSD to start in the functional job group