Jenkins for automated GUI test

[LazyBird]

Hi,

I am trying to use Jenkins for our automated GUI test. Here is my test
steps

1. Receive new build notification mail.
2. Download build from FTP server.
3. Prepare test machine(VMware virtual machine):
1) Revert virtual machine to clean snapshot
2) Check out the test script from SVN server
3) Install the software under test.
4) Run test scripts
4. Analyze test report

My question is whether Jenkins suite my need? If it is true, could any
one show me the road map to set up Jenkins for my task?

[Eyal Edri]

i don't see why you can't use jenkins for it..

also, you might want to check 'Selenium' for gui tests.

it also has a jenkins plugins[1].
if your tests reports are not in JUNIT format, you can use this plugin[2], with a custom XSLT.

[1] https://wiki.jenkins-ci.org/display/JENKINS/Selenium+Plugin
[2] https://wiki.jenkins-ci.org/display/JENKINS/xUnit+Plugin

Eyal.

[Vojtech Juranek]

also VNC plugin [1] and URL trigger plugin [2] could be intersting for you.
AFAIK no email trigger plugin is available, but polling FTP server via URL
trigger can be probably used intead of it.

[1] https://wiki.jenkins-ci.org/display/JENKINS/Xvnc+Plugin
[2] https://wiki.jenkins-ci.org/display/JENKINS/URLTrigger+Plugin

[Jminne]

The question you are asking is very general, but what you are
describing is what Jenkins is designed for. Jenkins is definitely the
best open source tool (continuous integration server) for the job and
probably the best one out there. I just haven't tried the paid ones
recently so I can't compare.

Here's some tips:

1) have the test job triggered by the api as the last build step.
Eventually you want to get the build in jenkins to make build/test
pipelines easier to manage.
2) Write scripts to run the test setup. Use a freestyle jenkins job
to check them out and run them as a task
3) have a second task run the tests themselves.
3) have your test output in junit xml format so you all the nice
analysis tools that are build in: duration trends, new failures,
etc.

[LazyBird]

That looks great, thanks.

On Dec 29, 8:27 pm, Vojtech Juranek <vjura...@redhat.com> wrote:
> also VNC plugin [1] and URL trigger plugin [2] could be intersting for you.
> AFAIK no email trigger plugin is available, but polling FTP server via URL
> trigger can be probably used intead of it.
>
> [1]https://wiki.jenkins-ci.org/display/JENKINS/Xvnc+Plugin
> [2]https://wiki.jenkins-ci.org/display/JENKINS/URLTrigger+Plugin
>
>
>
>
>
>
>
> > i don't see why you can't use jenkins for it..
>
> > also, you might want to check 'Selenium' for gui tests.
>
> > it also has a jenkins plugins[1].
> > if your tests reports are not in JUNIT format, you can use this plugin[2],
> > with a custom XSLT.
>
> > [1]https://wiki.jenkins-ci.org/display/JENKINS/Selenium+Plugin
> > [2]https://wiki.jenkins-ci.org/display/JENKINS/xUnit+Plugin
>
> > Eyal.
>
> > ----- Original Message -----
>

[LazyBird]

Thanks for your tips.
1) this is definitely the best choice, but it need negotiate with
build team.
4) That's a good idea, the only problem is I use RFT(Rational
Functional Tester) as my GUI test tool, and it could only generate two
type of report: plain text and HTML. I will need to write some code to
do the conversion. I will contribute it as a plugin if I made
progress.

[Mark Waite]

If your test tool of choice already generates HTML, then you might consider just linking to the HTML output rather than transforming it into JUnit XML format.  

There is a plugin that allows you to publish HTML reports.  I use it to provide easy access to the output from the gcc coverage reports as generated by "lcov".  I think you could do something similar with the HTML reports from Rational Functional Tester.

Refer to https://wiki.jenkins-ci.org/display/JENKINS/HTML+Publisher+Plugin 

Mark Waite

---

From: LazyBird <eric2...@gmail.com>
To: Jenkins Users <jenkins...@googlegroups.com>
Sent: Thursday, December 29, 2011 7:21 PM
Subject: Re: Jenkins for automated GUI test

[LazyBird]

Thanks, Mark.

On Dec 30, 10:38 am, Mark Waite <markwa...@yahoo.com> wrote:
> If your test tool of choice already generates HTML, then you might consider just linking to the HTML output rather than transforming it into JUnit XML format.
>
> There is a plugin that allows you to publish HTML reports.  I use it to provide easy access to the output from the gcc coverage reports as generated by "lcov".  I think you could do something similar with the HTML reports from Rational Functional Tester.
>
> Refer to https://wiki.jenkins-ci.org/display/JENKINS/HTML+Publisher+Plugin
>
> Mark Waite
>
>
>
>
>
>
>
> >________________________________

> > From: LazyBird <eric2323...@gmail.com>