Skip to content
This repository has been archived by the owner on Apr 7, 2022. It is now read-only.

appliance doesn't really work with uncollectif #5215

Open
jkrocil opened this issue Aug 22, 2017 · 3 comments
Open

appliance doesn't really work with uncollectif #5215

jkrocil opened this issue Aug 22, 2017 · 3 comments

Comments

@jkrocil
Copy link
Contributor

jkrocil commented Aug 22, 2017

appliance doesn't really work with uncollectif, because it's a fixture (unlike provider, which is an object directly provided by testgen). My bad. We have to fix this though, if we want to eventually get rid of pulling stuff from various places. Right now, we check appliance version / stream through:

  • appliance_is_downstream from utils.version
  • current_appliance from utils.appliance
  • current_appliance from fixtures.pytest_store.store

All of that is wrong. We need to have appliance available the same way provider is available, if possible.

@jkrocil
Copy link
Contributor Author

jkrocil commented Aug 22, 2017

@mfalesni @psav ^

@mfalesni
Copy link
Contributor

pytest could support some sort of "global parameters" which would get defined on the start of the pytest process before collection. Those then could be static like parameters.

@RonnyPfannschmidt RonnyPfannschmidt removed their assignment Apr 2, 2020
@RonnyPfannschmidt
Copy link
Contributor

i believe this was resolvable using the application plugin object which also provides the application fixture

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

No branches or pull requests

3 participants