On 08/27/2014 02:13 PM, Niels de Vos wrote:
On Wed, Aug 27, 2014 at 01:50:40PM +0530, Kaushal M wrote:
I'll do that, if someone could point me to it. Is it on the community
wiki or in doc/ directory in the source?
Seems to be only (?) on the wiki:
- http://www.gluster.org/community/documentation/index.php/Using_the_Gluster_Test_Framework#Creating_your_own_tests
Niels
We should also update README.md file in source code i.e. glusterfs/tests.
-Lala
~kaushal
On Wed, Aug 27, 2014 at 1:12 PM, Niels de Vos <ndevos@xxxxxxxxxx> wrote:
On Wed, Aug 27, 2014 at 12:21:56PM +0530, 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?
Sounds good to me. Please make sure to update the documentation about
writing test-cases in a few days, if nobody objects.
Thanks,
Niels
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
