-
Notifications
You must be signed in to change notification settings - Fork 210
e2e: make running subsets of e2e tests more organized #1512
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
Changes from all commits
9ccdbf3
016a57a
5513302
5347665
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -39,7 +39,7 @@ const ( | |
) | ||
|
||
func init() { | ||
ginkgo.Describe("DLB plugin", describe) | ||
ginkgo.Describe("DLB plugin [Device:dlb]", describe) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't have a good suggestion but it looks that now these node descriptions have a lot of repeating words. Since each description is modified by this PR, I was wondering if it made sense to reword them a bit. How does the output look for a device when all tests are run? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Well, I also thought about this matter, and have been thinking for a long time after you wrote this comment, but I could not think either.
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Well, in our case, we have many layers so.. it would look dirtier though.. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We can keep it as it is but I feel it could be optimized. Like: how many times QAT is mentioned on that row? Or, would There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Umm, that is not related to this PR..! They are already mentioned multiple times without the labels.. :(
Actually it was what I was thinking at first,, but then have no idea for [Resource] or [App] because some verbs (e.g. 'deploys') or 'When' should be before the labels... For example,
To me,, this looked more messy because labels seem like to be in random places... There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
My original comment was just "something for you to think about". It's not directly related to this PR but here we are modifying these lines so there could be an opportunity to have refinements included in the same changes. |
||
} | ||
|
||
func describe() { | ||
|
@@ -81,30 +81,38 @@ func describe() { | |
} | ||
}) | ||
|
||
ginkgo.Context("When PF resources are available", func() { | ||
ginkgo.Context("When PF resources are available [Resource:pf]", func() { | ||
ginkgo.BeforeEach(func(ctx context.Context) { | ||
resource := v1.ResourceName("dlb.intel.com/pf") | ||
if err := utils.WaitForNodesWithResource(ctx, f.ClientSet, resource, 30*time.Second); err != nil { | ||
framework.Failf("unable to wait for nodes to have positive allocatable resource %s: %v", resource, err) | ||
} | ||
}) | ||
|
||
ginkgo.It("can run demo app", func(ctx context.Context) { | ||
ginkgo.It("can run demo app [App:libdlb]", func(ctx context.Context) { | ||
runDemoApp(ctx, "PF", demoPFYaml, f) | ||
}) | ||
|
||
ginkgo.When("there is no app to run [App:noapp]", func() { | ||
ginkgo.It("does nothing", func() {}) | ||
}) | ||
}) | ||
|
||
ginkgo.Context("When VF resources are available", func() { | ||
ginkgo.Context("When VF resources are available [Resource:vf]", func() { | ||
ginkgo.BeforeEach(func(ctx context.Context) { | ||
resource := v1.ResourceName("dlb.intel.com/vf") | ||
if err := utils.WaitForNodesWithResource(ctx, f.ClientSet, resource, 30*time.Second); err != nil { | ||
framework.Failf("unable to wait for nodes to have positive allocatable resource %s: %v", resource, err) | ||
} | ||
}) | ||
|
||
ginkgo.It("can run demo app", func(ctx context.Context) { | ||
ginkgo.It("can run demo app [App:libdlb]", func(ctx context.Context) { | ||
runDemoApp(ctx, "VF", demoVFYaml, f) | ||
}) | ||
|
||
ginkgo.When("there is no app to run [App:noapp]", func() { | ||
ginkgo.It("does nothing", func() {}) | ||
}) | ||
}) | ||
} | ||
|
||
|
Uh oh!
There was an error while loading. Please reload this page.