Currently most of the e2e test files only contain 1 test. This makes it harder to see optimizations between tests.
A good example of this is the folder tests. The folder and cached folder tests are basically the same test with the exception of the cached tests also using multiple instances and adding folders after a commit instead of before.
90% of these two tests is duplicated.
This is probably also true for the file tests.
The test files should be more general, and contain all the tests associated with that scope. i.e. folder_test.go should contain all tests associated with folders.
Currently most of the e2e test files only contain 1 test. This makes it harder to see optimizations between tests.
A good example of this is the folder tests. The folder and cached folder tests are basically the same test with the exception of the cached tests also using multiple instances and adding folders after a commit instead of before.
90% of these two tests is duplicated.
This is probably also true for the file tests.
The test files should be more general, and contain all the tests associated with that scope. i.e. folder_test.go should contain all tests associated with folders.