> Currently we name tests associated with a bug with just the bug-id as > 'bug-XXXXXXX.t'. This naming doesn't provide any context directly, and > someone looking at just the name wouldn't know what it does. > > I suggest that we use slightly more descriptive names to the tests. > Lets name the tests as 'bug-XXXXXXX-checking-if-feature-Y-works.t'. > This provides just enough context to understand what the test is > trying to do from just the name. > > How do you all feel about this? It's an excellent idea. While we're at it, it would also be nice if tests were arranged into subdirectories so that it's easier to find those that might be particularly useful for testing new code. BTW, it should be possible to write a script that would fetch the bug title from Bugzilla, which (properly mangled) could be a first guess at the new test name. _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
