Hi Poornima,<div><br></div><div>Generic I meant, because the test doesn't have any report at end, like how any unit test framework does. Consider creating screenshot incase of test failure. If everything goes fine, the test will not quit Firefox, I think.</div>
<div><br></div><div>Still some of the window names or object names have hard coded text, they are not reused from common variables.</div><div><br></div><div>Thanks</div><div>Nagappan</div><div><br><div class="gmail_quote">
On Mon, Apr 16, 2012 at 6:59 AM, Poornima Nayak <span dir="ltr"><<a href="mailto:mpnayak@linux.vnet.ibm.com">mpnayak@linux.vnet.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Incorporated all the comments given by Nagappan. Modified header of all<br>
the files.<br>
<a href="https://github.com/PoornimaNayak/gnomeautomation" target="_blank">https://github.com/PoornimaNayak/gnomeautomation</a><br>
<div class="HOEnZb"><div class="h5">On Sat, 2012-04-14 at 22:35 +0530, Poornima Nayak wrote:<br>
> On Wed, 2012-04-11 at 19:24 -0700, Nagappan Alagappan wrote:<br>
> > Hi Poornima,<br>
> ><br>
> ><br>
> > I'm not convinced with firefox.py. I see the following issues:<br>
> ><br>
> ><br>
> > * its not generic<br>
> I missed this line while replying earlier. Not very sure what you meant<br>
> by 'not generic'<br>
> > * It doesn't handle any exception, say if you have test script 1 to<br>
> > 10, if the test fails for some reason and throws any exception in test<br>
> > 2, tests starting 3 to 10 won't be executed<br>
> > * The test doesn't put back to the old state, I mean if some exception<br>
> > happens, all the current window should be closed and should be smooth<br>
> > for the next test<br>
> ><br>
> ><br>
> > Other comments from IRC:<br>
> ><br>
> ><br>
> > * Create a readme file with version of Firefox, Linux distribution<br>
> > * Add respective license / author files<br>
> > * Move 'frm*MozillaFirefox' and other object names to some common<br>
> > file, so changing things will be at one place, will be really helpful<br>
> > at later point, if you are planing for i18n / l10n. Just change that<br>
> > file content with appropriate locale text and your scripts are ready<br>
> > for localization testing<br>
> > * time module imported couple of times in navigation.py<br>
> > * Comment navigation.py line#57, verifyabout.py line#46,<br>
> > verifynewtab.py line#40<br>
> > * Use wait instead of time.sleep<br>
> > * Additional space between url and = in verifynewtab.py<br>
> ><br>
> ><br>
> > Additional comments:<br>
> ><br>
> ><br>
> > * Don't use space between the function name and open bracket, ex:<br>
> > instead of 'log (' use 'log('<br>
> > * Maybe you can use 'if not waittillguinotexist('window')' instead<br>
> > of 'if waittillguinotexist('window') == 0'<br>
> > * At end of the complete test execution, application should exit<br>
> ><br>
> ><br>
> > Thanks<br>
> > Nagappan<br>
> ><br>
> > On Wed, Apr 11, 2012 at 12:06 PM, Poornima Nayak<br>
> > <<a href="mailto:mpnayak@linux.vnet.ibm.com">mpnayak@linux.vnet.ibm.com</a>> wrote:<br>
> > Hi All<br>
> ><br>
> > Sheetal & I work in IBM Linux Technology Center, we are<br>
> > testing<br>
> > Accessibility. We are using LDTP test script written for<br>
> > automating<br>
> > Firefox testing. These scripts where written based on Firefox<br>
> > version in<br>
> > 2004/2006 and LDTP supported API's in 2004/2006.<br>
> > So we had to do lot of modification and come out with some<br>
> > work arounds.<br>
> ><br>
> > Nagappan already suggested lot of changes, those will be done.<br>
> > I specially need comment on firefox.py which triggeres test<br>
> > one by one.<br>
> ><br>
> > I have uploaded scripts at<br>
> > <a href="https://github.com/PoornimaNayak/gnomeautomation" target="_blank">https://github.com/PoornimaNayak/gnomeautomation</a>.<br>
> ><br>
> > We are planning to modify around 23 more Firefox test scripts<br>
> > and<br>
> > publish in the above repository after we learn the expectation<br>
> > from LDTP<br>
> > maintainer and the community.<br>
> ><br>
> > Regards<br>
> > Poornima<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > LDTP-dev mailing list<br>
> > <a href="mailto:LDTP-dev@lists.freedesktop.org">LDTP-dev@lists.freedesktop.org</a><br>
> > <a href="http://lists.freedesktop.org/mailman/listinfo/ldtp-dev" target="_blank">http://lists.freedesktop.org/mailman/listinfo/ldtp-dev</a><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Linux Desktop (GUI Application) Testing Project -<br>
> > <a href="http://ldtp.freedesktop.org" target="_blank">http://ldtp.freedesktop.org</a><br>
> > <a href="http://nagappanal.blogspot.com" target="_blank">http://nagappanal.blogspot.com</a><br>
> ><br>
><br>
><br>
> _______________________________________________<br>
> LDTP-dev mailing list<br>
> <a href="mailto:LDTP-dev@lists.freedesktop.org">LDTP-dev@lists.freedesktop.org</a><br>
> <a href="http://lists.freedesktop.org/mailman/listinfo/ldtp-dev" target="_blank">http://lists.freedesktop.org/mailman/listinfo/ldtp-dev</a><br>
><br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Linux Desktop (GUI Application) Testing Project - <a href="http://ldtp.freedesktop.org">http://ldtp.freedesktop.org</a><br><a href="http://nagappanal.blogspot.com">http://nagappanal.blogspot.com</a><br>
</div>