-
Notifications
You must be signed in to change notification settings - Fork 82
Reorganize Tests against R #828
Copy link
Copy link
Open
Labels
dependenciesPull requests that update a dependency filePull requests that update a dependency filehelp wantedExtra attention is neededExtra attention is neededinfrastructureEverything Related to Package Infrastructure: Github Actions, pre-commit hooks, poetry, linting, etcEverything Related to Package Infrastructure: Github Actions, pre-commit hooks, poetry, linting, etc
Metadata
Metadata
Assignees
Labels
dependenciesPull requests that update a dependency filePull requests that update a dependency filehelp wantedExtra attention is neededExtra attention is neededinfrastructureEverything Related to Package Infrastructure: Github Actions, pre-commit hooks, poetry, linting, etcEverything Related to Package Infrastructure: Github Actions, pre-commit hooks, poetry, linting, etc
The current test suite against R requires users to install R and multiple packages from CRAN into the global R environment.
Optimally, we would directly install R and all R dependencies available on
conda-forgedirectly fromconda-forgeinto the pyfixest dev environment, which should help developers to run unit tests against R locally + keep the dev's R installation "clean".I think it would be best to reorganize the unit tests against R to have the following structure:
tests-against-r-core: tests against packages available viaconda-forge:fixestandsandwich. These are directly added to thetestsenvironment as dependencies.tests-against-r-extended: tests against R packages not availabe onconda-forge:did2s,ritest,fwildclusterboot, etc.To do's:
testsenvironment:r-fixest,r-sandwich,r-broom, R itselfagainst-r-core& decorate all tests that only depend offixest,sandwich,broomagainst-r-extended& decorate all tests that only depend on "other" r packages