Currently tests and the codebase is written together with their test_data all in one folder making it hard dig through the files and folders once it starts to mature.
Can we think of making a parent folder with e2e tests written
like:
|-cmd
|-tests
|-pkg
or we can think of writing tests within the same package that we are doing now, but extract out all the test resources in their own folder named like tests
Currently tests and the codebase is written together with their test_data all in one folder making it hard dig through the files and folders once it starts to mature. Can we think of making a parent folder with e2e tests written like:
or we can think of writing tests within the same package that we are doing now, but extract out all the test resources in their own folder named like tests