-
Notifications
You must be signed in to change notification settings - Fork 72
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
[Feature] Improve modularity of test cases implementation #1861
Comments
Hello, @agentpoyo, can you please assign this one to me? I'm already work in progress with that and about to propose a change for review. |
Signed-off-by: Martin Matyas <martin.matyas@gmail.com>
@wavell @denverwilliams @agentpoyo please review (do not merge for now, see PR cncf#1867 description). |
I updated the title to be "WIP". You can also create "Draft" pull requests to prevent merges. |
Signed-off-by: Martin Matyas <martin.matyas@gmail.com>
Signed-off-by: Martin Matyas <martin.matyas@gmail.com>
Signed-off-by: Martin Matyas <martin.matyas@gmail.com>
Signed-off-by: Martin Matyas <martin.matyas@gmail.com>
Modularize implementation of tests #1861
Is your feature request related to a problem? Please describe.
Test case implementation contains code that is repeated/duplicated across tests or have unnecessary dependency on test information on other part of the code. Examples:
Describe the solution you'd like
Improve test case implementation and reporting modularity. Avoid information redundancy in code as much as possible. Aoid need for copy/pasting as much as possible. Use more modularity/classes.
Describe alternatives you've considered
An alternativu woul be to keep the code as it is. However it is a pain to add or change a test case with keeping everything consistent.
**How will this be tested? aka Acceptance Criteria (optional) **
full regression test run pass
(optional: unnecessary for things like some version bumps etc.)
Once this issue is addressed how will the fix be verified?
full regression test run pass
Additional context
The text was updated successfully, but these errors were encountered: