-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kola: Add a filter to run tests based on offering #158
kola: Add a filter to run tests based on offering #158
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested with bin/kola list --filter --offering pro --platform qemu
after adding some annotations to tests
I've updated tests with the Offering param so that it is easier and cleaner in jenkins to just pass the parameter |
kola/tests/coretest/core.go
Outdated
@@ -72,7 +72,8 @@ func init() { | |||
"Useradd": TestUseradd, | |||
"MachineID": TestMachineID, | |||
}, | |||
Distros: []string{"cl"}, | |||
Distros: []string{"cl"}, | |||
Offerings: []string{"basic", "pro"}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit confused here, do we really need to specify this field for each and every test? We don't do this for Architectures or Channels... Why do we need to do it for Offerings?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated Offerings
similar to how Architectures
and Channels
are. I was thinking for a future case, where we have more offers, and miscalculated. Sorry for the confusion.
d4a6f97
to
8d0bc58
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
With the introduction of the Pro offering, it is not possible to test Pro specific features or test just for Pro without them runing on the basic offering as well. This changes introduces a new flag that helps building a clear distinction between Pro and the nornal offering. Signed-off-by: Sayan Chowdhury <[email protected]>
Signed-off-by: Sayan Chowdhury <[email protected]>
8d0bc58
to
a87b7cc
Compare
kola: Add a filter to run tests based on offering
With the introduction of the Pro offering, it is not possible to
test Pro specific features or test just for Pro without them runing
on the basic offering as well. This changes introduces a new flag
that helps building a clear distinction between Pro and the nornal
offering.
The
excludeOffering
maybe does not make sense now with two offeringbut kept it for future feasibility.
Signed-off-by: Sayan Chowdhury [email protected]
How to use
Testing done
Not done yet.