You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we have some test files that have all (or almost all) tests of a module within a single file, the ideal here is to split these cases into multiple test files. Which file should be testing a single functionality, or file of our library.
This issue will work as a tracker to map some of these files that need to be split, feel free to help us find others and/or help us split them into multiple files.
The goal here is to reorganize our test suite. If you have any questions, you can call us and/or ask on our Slack page too
@johnnv1 I'll help splitting the losses test into their individual loss file and can you help point me to the testing docs so that I can run the tests after I've done splitting the file thanks.
Currently, we have some test files that have all (or almost all) tests of a module within a single file, the ideal here is to split these cases into multiple test files. Which file should be testing a single functionality, or file of our library.
Example:
This issue will work as a tracker to map some of these files that need to be split, feel free to help us find others and/or help us split them into multiple files.
The goal here is to reorganize our test suite. If you have any questions, you can call us and/or ask on our Slack page too
Originally posted by @edgarriba in #2745 (comment)
You can choose anyone below, or find new ones. You don't have to worry about separating all the tests in a file into a single PR
The text was updated successfully, but these errors were encountered: