Hi,
Moving this conversations to [email protected].
Yes, what you are talking about is [1], which is an attempt to define
blackbox acceptance tests in a way that lets us test our final
deliverables (rpm, deb, etc.) It contains the page objects, among other
things.
I think having a java library that defines page objects for Jenkins is
useful. Go for it!
You might be also interested in [2], which creates handles in the form
input fields that simplifies the XPath-based selection of the right
target node.
There's also a conversation of adding another functionality (either in
this plugin or another one) that exposes Groovy scripting console in a
way that lets you verify side-effects that happen on the server more easily.
And then maybe it's possible to run selenium-tests in JRuby so that we
can run some Java-based selenium tests in the same environment, which
allows you to leverage pluggable layers in the selenium-tests and
VirtualBox integrations.
[1] https://github.com/jenkinsci/selenium-tests
[2] https://wiki.jenkins-ci.org/display/JENKINS/Form+Element+Path+Plugin
On 11/20/2012 06:23 PM, Richard Lavoie wrote:
Hey Kohsuke,
I'll be starting the work of a framework based on selenium page object
design pattern.
I know you are doing something similar (in ruby or python afaik) with
rtyler to test jenkins itself but I thought it would be nice to have the
same thing in java for those who'd want to be able to test form fill and
actions in their plugins.
Let me know what you think about it.
--
Richard Lavoie
IT consultant / consultant en informatique
--
Kohsuke Kawaguchi http://kohsuke.org/
