The archiver-UI-Debug-files shouldn't live in the root of the project. However, we still want this code to exist, so we should move them somewhere.
My suggestion is, since they are "debug-files", that they are moved somewhere in the "test" directory.
We still want them to be grouped together, so they can be easily found. Since we've currently got a test// structure. I'd like:
.sh -> test/sh
.py -> test/py
.conf -> test/conf
etc..
And maybe keep the java package structure like so:
test/sh/com/splunk/shuttl/archiver/ui/
test/py/com/splunk/shuttl/archiver/ui/
test/conf/com/splunk/shuttl/archiver/ui/
Another solution would be to let them be in the same structure as they are today. But then I'd still want something like grouping by component:
test/component/archiver/ui/
If any of these "debug-files" are more generic and can be used for other kinds of testing, then put them somewhere where it would make sense. For example, the "indexes.conf" seems useful for manually testing the archiver, even though it's not through the UI.
Choose a solution and make sure everything still works after the move.
The archiver-UI-Debug-files shouldn't live in the root of the project. However, we still want this code to exist, so we should move them somewhere.
My suggestion is, since they are "debug-files", that they are moved somewhere in the "test" directory. We still want them to be grouped together, so they can be easily found. Since we've currently got a test// structure. I'd like:
And maybe keep the java package structure like so:
Another solution would be to let them be in the same structure as they are today. But then I'd still want something like grouping by component:
If any of these "debug-files" are more generic and can be used for other kinds of testing, then put them somewhere where it would make sense. For example, the "indexes.conf" seems useful for manually testing the archiver, even though it's not through the UI.
Choose a solution and make sure everything still works after the move.