Skip to content
This repository has been archived by the owner on Jul 18, 2023. It is now read-only.

Create new job for running migration tests - tests/foreman/cli/test_import.py #80

Closed
sthirugn opened this issue Nov 25, 2015 · 8 comments

Comments

@sthirugn
Copy link
Contributor

No description provided.

@elyezer
Copy link
Contributor

elyezer commented Nov 26, 2015

They are already been running on the CLI job. Is a separated job needed?

@omaciel
Copy link
Member

omaciel commented Nov 26, 2015

@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?

@elyezer
Copy link
Contributor

elyezer commented Nov 26, 2015

@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"

@omaciel
Copy link
Member

omaciel commented Nov 27, 2015

@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 cli/test_import.py are 'special' because they are testing the migration process from Satellite 5 to Satellite 6. I think that it is important to see these tests explicitly apart from all other tests, as a way for us to see any red flags related to the feature being tested. I wonder if @cswiii thinks this is important or not...

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 ?

@sghai
Copy link
Contributor

sghai commented Nov 27, 2015

+1
Its absolutely make sense to use ISO jobs just for install. + monitor the overall health after install by checking all services along with hammer ping.

@sthirugn
Copy link
Contributor Author

I vote for ISO jobs install + smoke or tier1 test.

@elyezer
Copy link
Contributor

elyezer commented Dec 2, 2015

Created #86 to handle the ISO job update.

@kbidarkar
Copy link
Collaborator

I feel we can close this issue as we have the same issue opened #266
Anyways will link up the discussion on this issue in #266.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants