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

Document code coverage report #467

Open
iandunn opened this issue Oct 7, 2022 · 4 comments
Open

Document code coverage report #467

iandunn opened this issue Oct 7, 2022 · 4 comments

Comments

@iandunn
Copy link
Member

iandunn commented Oct 7, 2022

I tried to find the report by guessing what the coveralls.io URL would be, but wasn't successful. Adding it to the readme could be helpful. I'm happy to open a PR if someone can share the URL.

@kasparsd
Copy link
Collaborator

kasparsd commented Oct 7, 2022

After being moved to the WordPress org the URL is https://coveralls.io/github/WordPress/two-factor but it used to be under @georgestephanis vendor https://coveralls.io/github/georgestephanis/two-factor

I haven't checked if the new one is even configured.

@jeffpaul jeffpaul added this to the Future Release milestone Oct 7, 2022
@iandunn
Copy link
Member Author

iandunn commented Oct 10, 2022

Thanks! It doesn't seem to be showing any reports, so I guess documenting should probably wait until it's configured 👍🏻

Related #468

@iandunn
Copy link
Member Author

iandunn commented Oct 11, 2022

Related #364

@jeffpaul
Copy link
Member

jeffpaul commented Dec 3, 2024

Are unit tests and related code coverage reports as useful as say documented critical flows and associated e2e tests with some basic test report formatting?

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

No branches or pull requests

3 participants