-
Notifications
You must be signed in to change notification settings - Fork 55
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
Add documentation on our testing environment #589
Comments
mpadge
added a commit
to mpadge/dev_guide
that referenced
this issue
Feb 9, 2023
maelle
added a commit
that referenced
this issue
Sep 28, 2023
Co-authored-by: Yanina Bellini Saibene <[email protected]> Co-authored-by: Maëlle Salmon <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given our last submissions have issues with the automated tests with respect to our testing environment, I'm wondering if we might be able to help the situation with a little more transparency regarding the testing environment we use. I suggest a section in our devguide with:
In any case, transparency over both what we have available and any additional dependencies installed could also benefit reviewers who might also hit issues at times with local installations.
Related to #587
The text was updated successfully, but these errors were encountered: