-
Notifications
You must be signed in to change notification settings - Fork 25
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
Rebuild testing #209
Comments
I'm not sold on the |
The goal is uniquness, to avoid collisions between competing runs of tests, e.g. on my machine and CI. Perhaps the name of the test combined with a millisecond datestamp would do it. |
I never thought about competing runs of the tests. Would that be to test on
multiple OSs?
…On Wed, Feb 3, 2021 at 11:57 AM Ian Lyttle ***@***.***> wrote:
The goal is uniquness, to avoid collisions between competing runs of
tests, e.g. on my machine and CI. Perhaps the name of the test combined
with a millisecond datestamp would do it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#209 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGFKIIXV7AYJPONOUVIWODS5F575ANCNFSM4W3QMBZA>
.
|
It could be, but I wasn't planning on it - at least until I get the tests reworked. |
This is an expansion of #176, this would be a bigger project where we essentially rebuild the testing to use more-recent ideas in testthat.
In "live" testing, each test file should:
We should have persistent folders at Box so that we can test searching.
We can also use snapshot testing to test our translation of Box API responses.
There is a README file in the testthat directory - this should be updated.
The text was updated successfully, but these errors were encountered: