You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some portion of the code base is only tested via mocks where it could be tested more thoroughly. A good example of an area for improvement is publish testing. Both the s3 connection and the publisher itself are mocked where only one is needed (for instance, you can replace this code block with yield None and the test will still pass). Since we are using moto to mock AWS calls, we should unmock the calls to AWS and see if the mocked services have the files/properties we expect.
Acceptance Criteria
Determine whether this is a priority
Decide on which functions and tests should be improved
The text was updated successfully, but these errors were encountered:
drewbo
changed the title
Reduce usage of test mocking
Reduce use of test mocking
Aug 26, 2022
Some portion of the code base is only tested via mocks where it could be tested more thoroughly. A good example of an area for improvement is publish testing. Both the s3 connection and the publisher itself are mocked where only one is needed (for instance, you can replace this code block with
yield None
and the test will still pass). Since we are usingmoto
to mock AWS calls, we should unmock the calls to AWS and see if the mocked services have the files/properties we expect.Acceptance Criteria
The text was updated successfully, but these errors were encountered: