-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Do Not Review: Remove Workflow Interface Tests workflow and related test folder #1409
base: develop
Are you sure you want to change the base?
Do Not Review: Remove Workflow Interface Tests workflow and related test folder #1409
Conversation
Signed-off-by: noopur <noopur@intel.com>
Hi @noopurintel , could you update the PR description as per the template? |
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.
This means task runner and workflow API tests will be run for all PRs, right?
Using labels is one way to reduce the number of tests run per PR. Is it possible to run tests based on the directories where changes have been made, thus reducing the CI run time and not running unnecessary tests?
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.
While this PR does clean-up duplication of Workflow API test cases, there are two folders which now contain end-to-end test cases
tests/github
, andtests/end_to_end
As per my understanding the old convention was
tests/github
: End to End test casestests/openfl
: Module level test cases
Request to please harmonize the test directory also to avoid any confusion
Signed-off-by: Noopur <noopur@intel.com>
Signed-off-by: Noopur <noopur@intel.com>
Signed-off-by: Noopur <noopur@intel.com>
Signed-off-by: Noopur <noopur@intel.com>
Type of Change (Mandatory)
Specify the type of change being made.
Description (Mandatory)
Workflow Functional E2E which is already a part of PR pipeline covers all the tests present in Workflow Interface Tests in Pytest framework, thus removing the workflow as well as folder
LocalRuntime
specific to it.Earlier, both of these were kept just to ensure smooth transition and stability of pytest based workflow.
Testing
PR pipeline already covers Functional E2E workflow.