I'm trying to get git-lfs working so we can fix the model around change tracking and large files. I would propose waiting on this kind of structural change and we see the results of that effort.
I actually would push for something slightly different. There are two main things: the test framework and the tests themselves. It seems like they should be managed in independent trees. E.g. /framework versus /tests. The tests suite is responsible executing the framework. Having the test data mixed with the test harness seems confusing. Other things worth considering. - Better clarify/separate data preparation versus test execution steps. - Remove relocation/abstraction in test files. This allows a simple sync approach to matching cluster data to test data (and makes matching the two way less confusing for devs trying to track down what the test failure output means). - Correct issues where scripts are used outside of the test framework for Drill test generation as part of an internal test pattern. - Move back to the original goal of test definition files having actual test definitions (query, expected result, etc) - Improve convention or configuration (there is a lot of boilerplate in the test files that should be the default) - Fix the odd # of queries/middle check hacks. -- Jacques Nadeau CTO and Co-Founder, Dremio On Wed, Oct 14, 2015 at 12:23 PM, rahul challapalli < [email protected]> wrote: > Drillers, > > The drill test framework [1] which some of you have been using contains a 2 > level maven structure. This has always been a source of confusion for a > first time user. We would like to get rid of this and have a single pom > file to build the framework. This has a side effect of restructuring the > tests. The new repository will no longer contain a "framework" sub folder > and is more intuitive. Refer to [2] for the new structure. Let me know your > thoughts. > > > [1] https://github.com/mapr/drill-test-framework > [2] https://github.com/rchallapalli/drill-test-framework/tree/onelevel > > - Rahul >
