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

Don't comment out tests #361

Open
6 of 11 tasks
IndrajeetPatil opened this issue Mar 27, 2023 · 4 comments
Open
6 of 11 tasks

Don't comment out tests #361

IndrajeetPatil opened this issue Mar 27, 2023 · 4 comments
Labels
Code Style 👩‍💻 Core Packages 📦 Discussion and planning about core packages of easystats

Comments

@IndrajeetPatil
Copy link
Member

IndrajeetPatil commented Mar 27, 2023

There is nothing that makes other developers lose faith in our software than discovering that the commented out tests, since it's basically a mechanism to sweep known bugs under the rug.

Unfortunately, we are doing this a lot in some repos, and we need to undo this.

There are a few alternatives to commenting out tests:

  • Uncomment tests and let the build fail until these tests are fixed. The failing builds will act as the fire under our feet to motivate a quick fix.
  • Make a PR and uncomment tests in that PR, and keep working in that PR until the tests pass. The default branch builds remain green in this case.
  • Remove the tests because they are redundant.
  • Skip them in whatever contexts that are currently posing problems for them (e.g. M1mac).
  • Keep them commented but add a TODO, FIXME, etc. marker to remind us to fix them.

You can check the list below when there are no more commented out tests, which might already be the case for a few repos.

Progress tracker

  • insight
  • modelbased
  • bayestestR
  • effectsize
  • parameters
  • performance
  • correlation
  • report
  • see
  • datawizard
  • easystats
@IndrajeetPatil
Copy link
Member Author

If you want to check for commented out tests in your package, one option is to run the following:

lintr::lint_dir("tests", linters = lintr::commented_code_linter())

@IndrajeetPatil
Copy link
Member Author

So {effectsize} is not always perfect.

image

@mattansb
Copy link
Member

effectsize has only one such test of functions that have been moved to parameters! 🏆🏆🏆

IndrajeetPatil added a commit to easystats/effectsize that referenced this issue Mar 28, 2023
mattansb pushed a commit to easystats/effectsize that referenced this issue Mar 28, 2023
strengejacke added a commit to easystats/report that referenced this issue Mar 28, 2023
* Uncomment `report_sample()` tests

easystats/easystats#361

* fix: select can be NULL

* proper weighted MAD

* forgot .

---------

Co-authored-by: Daniel <mail@danielluedecke.de>
@IndrajeetPatil
Copy link
Member Author

bump

IndrajeetPatil added a commit to easystats/bayestestR that referenced this issue Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Code Style 👩‍💻 Core Packages 📦 Discussion and planning about core packages of easystats
Projects
None yet
Development

No branches or pull requests

7 participants