-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Refactor engine client test_create_job
test names for better clarity and consistency
#6885
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6885 +/- ##
=======================================
Coverage 97.86% 97.86%
=======================================
Files 1084 1084
Lines 94225 94321 +96
=======================================
+ Hits 92215 92311 +96
Misses 2010 2010 ☔ View full report in Codecov by Sentry. |
34fbebd
to
eddb152
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.
Thanks for contributing! Consider assigning the original bug to yourself, thanks! #6761
Split initial test_create_job into: - Four successful tests: - test_create_job_with_all_parameters - test_create_job_without_labels - test_create_job_without_description - test_create_job_without_specified_job_id - One failure test: - test_create_job_with_invalid_priority Note: Splitting successful tests to stay consistent with existing tests: - test_create_job_with_invalid_processor_and_device_config_arguments_throws - test_create_job_with_run_name_and_device_config_name_succeeds
35d0cf5
to
2aca27c
Compare
Thanks for the review! Unfortunately, I don't think I have permission to assign the original bug to myself. |
Following @senecameeks's comment -> Refactored the test cases to use pytest fixtures for |
…default_engine_client` - Updated all test cases to use these fixtures directly for consistency and clarity.
778e886
to
b0723b0
Compare
Split initial
test_create_job
test into:test_create_job_with_all_parameters
test_create_job_without_labels
test_create_job_without_description
test_create_job_without_specified_job_id
test_create_job_with_invalid_priority
Note: Splitting successful tests to stay consistent with existing tests:
test_create_job_with_invalid_processor_and_device_config_arguments_throws
test_create_job_with_run_name_and_device_config_name_succeeds
EDIT: Also refactored the test cases to use pytest fixtures for
default_run_context
anddefault_engine_client
for consistency and to reduce redundancy.Fixes #6761