Skip to content

Conversation

@shaypal5
Copy link
Member

@shaypal5 shaypal5 commented Feb 1, 2024

No description provided.

@shaypal5 shaypal5 force-pushed the enable-mongo-separation branch from 232a37c to 6b5ad19 Compare February 1, 2024 22:10
@codecov
Copy link

codecov bot commented Feb 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (6cfa2c7) 99.40% compared to head (bc6ef2e) 99.40%.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #144   +/-   ##
=======================================
  Coverage   99.40%   99.40%           
=======================================
  Files           5        5           
  Lines         508      508           
  Branches       88       88           
=======================================
  Hits          505      505           
  Misses          2        2           
  Partials        1        1           

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6cfa2c7...bc6ef2e. Read the comment docs.

@shaypal5 shaypal5 merged commit d19b3cf into master Feb 1, 2024
@shaypal5 shaypal5 deleted the enable-mongo-separation branch February 1, 2024 22:28
'mongetter,backend',
[
(_test_mongetter, 'mongo'),
# (_test_mongetter, 'mongo'), # Please do NOT test the mongo backend
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not rather mark it with

pytest.param(_test_mongetter, 'mongo', marks=pytest.mark.mongo)

instead of duplicating whole test

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops. I didn't know you're going to review in time. :P
Anyway, I didn't know you could do that with pytest!
Let's try that later. You can work it into your suite separation PR, or later; I'm not sure I understand the exact syntax you refer to.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems that this parameter marking was already used in the tests, see: #145

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants