-
Notifications
You must be signed in to change notification settings - Fork 89
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
CMR 9792: Int test cleanup part 1 #2113
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2113 +/- ##
===========================================
- Coverage 57.81% 24.75% -33.06%
===========================================
Files 1044 1044
Lines 70318 70296 -22
Branches 1966 1031 -935
===========================================
- Hits 40653 17404 -23249
- Misses 27808 51861 +24053
+ Partials 1857 1031 -826 ☔ View full report in Codecov by Sentry. |
system-int-test/test/cmr/system_int_test/ingest/bulk_update/bulk_update_flow_test.clj
Outdated
Show resolved
Hide resolved
system-int-test/test/cmr/system_int_test/search/scrolling_search_test.clj
Outdated
Show resolved
Hide resolved
...t-test/test/cmr/system_int_test/search/tagging/tag_association_collection_revisions_test.clj
Outdated
Show resolved
Hide resolved
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.
I left several comments
@@ -383,16 +383,16 @@ | |||
;; to vars to make it easier to see what is being ingested. | |||
|
|||
;; Ingest a collection twice. | |||
coll1-1 (d/ingest "PROV1" umm-coll1-1) | |||
coll1-2 (d/ingest "PROV1" umm-coll1-2) | |||
_coll1-1 (d/ingest "PROV1" umm-coll1-1) |
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.
Cases where there are a slew of initializations done in a let block but where we don't actually care about the returned object could be moved to outside the let.
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.
There is a note above that says NOTE - most of the following bindings could be ignored with _, but they are assigned to vars to make it easier to see what is being ingested.
So I think we can keep it in there for easier reading
@@ -23,7 +23,7 @@ _Kaocha will complain if a test is executed with no assertions._ | |||
|
|||
## Test Groups | |||
|
|||
In the CI environment, system integration tests are broken into two groups. | |||
In the CI environment, system integration tests are broken into three groups. |
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.
In the CI environment, system integration tests are broken into three groups. | |
In the CI environment, system integration tests are broken into multiple groups. |
Future proof in the case more or fewer groups are used.
Overview
What is the feature/fix?
Linter errors existed in system-int-test project
What is the Solution?
Since I was already looking at integration tests for research, I decided to do some linter fixes. These are only partial of the many linter errors in the repo.
What areas of the application does this impact?
integration tests
Checklist