This bug was originally filed in Launchpad as LP: #1754253
Launchpad details
affected_projects = []
assignee = None
assignee_name = None
date_closed = None
date_created = 2018-03-08T06:52:01.404917+00:00
date_fix_committed = None
date_fix_released = None
id = 1754253
importance = medium
is_complete = False
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1754253
milestone = None
owner = d-info-e
owner_name = do3meli
private = False
status = confirmed
submitter = d-info-e
submitter_name = do3meli
tags = []
duplicates = []
Launchpad user do3meli(d-info-e) wrote on 2018-03-08T06:52:01.404917+00:00
most of the integration tests are written for ubuntu and have hardcoded paths, service names or package names that may are different on other OS. it would be good to have the possibility to run integration tests in another os than ubuntu. this would as far as i can tell require a lot of tests to be rewritten. but first, there must be an easy way to get os specific variables for a certain module into the test class. for example how could the SaltConstant class being accessed from within the salt_minion.yaml so we don't have to hardcode paths ect. in the collection scripts?
This bug was originally filed in Launchpad as LP: #1754253
Launchpad details
Launchpad user do3meli(d-info-e) wrote on 2018-03-08T06:52:01.404917+00:00
most of the integration tests are written for ubuntu and have hardcoded paths, service names or package names that may are different on other OS. it would be good to have the possibility to run integration tests in another os than ubuntu. this would as far as i can tell require a lot of tests to be rewritten. but first, there must be an easy way to get os specific variables for a certain module into the test class. for example how could the SaltConstant class being accessed from within the salt_minion.yaml so we don't have to hardcode paths ect. in the collection scripts?