[rfc - concept][icedtea-web] plugin tests
dbhole at redhat.com
Fri Mar 2 06:44:33 PST 2012
* Jiri Vanek <jvanek at redhat.com> [2012-03-02 04:18]:
> On 03/01/2012 09:27 PM, Deepak Bhole wrote:
> >* Jiri Vanek<jvanek at redhat.com> [2012-02-13 11:09]:
> >>Hi all!
> >>I think, that I can use current reproducers approach to test applets.
> >>Current approch simple/signed src/resource/testcase and testing server with examination of stdin/out can and will be reused without any modification
> >This won't catch certain issues, like drawing issues for example, or
> >keyboard input related issues.
> Yap - drawing issues and mouse-clicking can be handled via awt robot an this is on the way. (with small observe-observable paradigm to be added into current engine to read stdout/err on the fly will be quit suitable for most interactivity tests)
> For more sophisticated user inputs (can awt tobot do som typing in textfields? I have some misty memories it can - so no issue here!) we must stay away of JCK-graphics tests, when user (me!!!) is sitting infront of monitor and clicking nonsenses and watching wired results, confitming txtxt and shapes.... For this purposes I believe we already have the wikipage with compelx aplications.
Unfortunately I don't know awt robot well enough to know if it can do
that :/ However it is a feature we will need as we have seen bugs where
the user was unable to type into a text field in the applet.
> >>Instead of jnlp files from resources will be used html file and instead of javaws will be used eg firefox (can use more testing browsers for testing, but can be hard to maintaining tests to all three mayor browsers). And I will always kill the browser before next test.
> >I think then we will miss certain issues, since the VM is shared. The
> >browser kill should be optional.
> True. As I have done this now, it is optional - firefox (browser..)is lunched and killed inside test calss. However TestClass should take care and kill him at least in @AfterClass
> >>On the other side I'm afraid I will lost advantage of -headless approach. And I'm not sure if I will be able to use awt robot (as I have failed once already, but some screen-capture approach will be possible for sure). But at least lunching of graphical apps must be solved, as firefox will always have gui! :)
> >>Also I will lost possibility to run plain cron job , But I remeber that "gui" tasks can be run via cron too.
> >Yes, you can use something like Xvfb and run it via cron.
> Ok. With awtrobot, screenshots analyze and and in- browser (do we want to try lynx? :D) tests no-graphic environment have definitely past away...
> >>And it will be necessary to add code coverage for plugin.jar :) [some-when :D ]
> >Agreed! :)
> LOooooNG run!
> >Thanks for taking this initiative!
More information about the distro-pkg-dev