-
Notifications
You must be signed in to change notification settings - Fork 3
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
[ORCA-288] Test Object Naming Refactor #52
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.
LGTM! Thanks for making these tests more clear!
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #52 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 24 24
Lines 1184 1184
Branches 192 192
=========================================
Hits 1184 1184 ☔ View full report in Codecov by Sentry. |
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.
🔥 Looks very straightforward to me. Unfortunately, tox is somewhat of a headache which is making me wonder if it's worth just sticking to basics.
…/fix_tox [ORCA-294] Fix `tox` implementation in CI pipeline
…9/refactor_tests_in_classes
…/refactor_tests_in_classes [ORCA-289] Refactor External and Internal Testing Unit Tests as Test Classes
Quality Gate passedThe SonarCloud Quality Gate passed, but some issues were introduced. 1 New issue |
Problem:
The test file, target, and suite objects defined in
conftest.py
that we use in our unit tests have confusing names, making it difficult to know what is happening in our tests.Solution:
Change the names to a loose convention of
good_<type_of_file>
for "good" files and<reason_why_this_file_is_bad_<type_of_file>
for "bad" files.Notes:
conftest.py
.