-
Notifications
You must be signed in to change notification settings - Fork 45
Create new job for running migration tests - tests/foreman/cli/test_import.py #80
Comments
They are already been running on the CLI job. Is a separated job needed? |
@elyezer we thought that it would be nice to see them separate from the other jobs, as they are specific to the transition tool... got suggestions for how to better visualize them? |
@omaciel jenkins provide the results separated by test module.This is how to see currently. If you are looking for a separate graph then a new job is the way to go. If the second options is adopted then I recommend moving that test module to a separated package and create a target for the transition stuff. Just to be accurate on what we have for the other "subtestsuites" |
@elyezer right, I know that Jenkins provides test results for this module... but it sort of gets lost in the middle of all other modules for CLI and, here's what bothers me a bit, sort of loses a bit of its significance. The tests contained within By the way, I also thought about changing our existing ISO jobs pipeline to only test that one can install from an ISO plus our Tier1 test suite (and therefore eliminating the need for Tier2 and Tier3 and all the RAM that is required to run those tests... the whole point is to make sure that our product can be installed from an ISO, so we may even consider not running Tier1 at all and just check that all services are up and running and then shut the systems down? What do you guys think @SatelliteQE/robottelo-automation ? |
+1 |
I vote for ISO jobs install + smoke or tier1 test. |
Created #86 to handle the ISO job update. |
No description provided.
The text was updated successfully, but these errors were encountered: