<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi pranith;<br><br>The bigtop smoke tests are a good way to go. You can run them against pig hive and so on.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">In general running a simple mapreduce job like wordcount is a good first pass start.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Many other communities like orangefs and so on run Hadoop tests on alternative file systems, you can collaborate with them.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">There is an hcfs wiki page you can contribute to on <a href="http://hadoop.apache.org">Hadoop.apache.org</a> where we detail Hadoop interoperability </div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature"><br></div><div><br>On Sep 2, 2016, at 3:33 PM, Pranith Kumar Karampuri <<a href="mailto:pkarampu@redhat.com">pkarampu@redhat.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div>hi Jay,<br></div> Are there any tests that are done before releasing glusterfs upstream to make sure the plugin is stable? Could you let us know the process, so that we can add it to <a href="https://public.pad.fsfe.org/p/gluster-component-release-checklist">https://public.pad.fsfe.org/p/gluster-component-release-checklist</a><br clear="all"><div><div><br>-- <br><div class="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</div></div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Gluster-devel mailing list</span><br><span><a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a></span><br><span><a href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a></span></div></blockquote></body></html>