On 27/08/2014, at 7:56 AM, Pranith Kumar Karampuri wrote: > On 08/27/2014 12:21 PM, Kaushal M wrote: >> Hi all, >> >> 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? > +100
Yeah, this sounds like a good idea. If I ever get around to writing test cases :>, I'll try that out. ;) + Justin -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift _______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://supercolony.gluster.org/mailman/listinfo/gluster-devel
