Skip to content
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

why is coverage 0% for some models? (eg: subdomain) #830

Closed
donrestarone opened this issue Jun 27, 2022 · 2 comments · Fixed by #929 or #933
Closed

why is coverage 0% for some models? (eg: subdomain) #830

donrestarone opened this issue Jun 27, 2022 · 2 comments · Fixed by #929 or #933
Assignees
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@donrestarone
Copy link
Contributor

Describe the bug

we expect to see more than 0% coverage in models like subdomain

To Reproduce

Run CI and download the coverage report.

Expected behavior

We have tests for these models (eg: test/models/subdomain_test.rb)

Screenshots
Screen Shot 2022-06-27 at 8 11 13 AM
Screen Shot 2022-06-27 at 8 11 01 AM

@donrestarone donrestarone added the bug Something isn't working label Jun 27, 2022
@donrestarone
Copy link
Contributor Author

@Pralish is in discussions with the community on the apartment repo: influitive/apartment#220

PS @Pralish -- I believe we are using ros/apartment (https://github.com/rails-on-services/apartment) there may be changes on that repo that may have introduced this quirk

CC @alis-khadka

@donrestarone donrestarone added the good first issue Good for newcomers label Jul 7, 2022
donrestarone added a commit that referenced this issue Jul 17, 2022
#### resolves: #830 no deploy needed

* try starting simplecov at rails boot to see if model coverage works

* undo

* prevent spring from running in test mode

* remove comment in env
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
2 participants