| Re: [epp-dev] Testing of the different packages |
Hi Steffen,
thank you for the encouraging feedback.
I could explain how the test process works so far:
1. A hudson job starts a download of the all targets for a package
2. For every target a job starts the AUTAgent (AUT=Application Under Test)
3. This job starts the AUT and run the tests
4. This job closes the AUTAgent again
We need:
1. A virtual machine or a server to run the tests for every target
2. Jubula installation on the targets
3. A centralized database for the test definitions and results (I would prefer Oracle XE)
When developing tests on your own you need:
1. A connection to the db (to reuse projects and add your project)
2. Configurations for starting the tests on eclipse via hudson
3. Configurations for starting the tests locally
If we consider that this process will work who can help me for setup?
Regards,
Felix
Zitat von Steffen Pingel <steffen.pingel@xxxxxxxxxxx>:
I was very impressed when I saw this working in action at EclipseCon
Europe. I believe this will be a great step forward to improve the QA
process in EPP and it'd be great to get this up and running soon. As far as
I understood there are still some infrastructure issues that need to be
resolved before we can run this on the Eclipse.org Hudson.
Felix, do you have a list of items that are outstanding in order to
integrate this into the build process?
Thanks,
Steffen
On Fri, Nov 18, 2011 at 3:41 PM, Felix Ziesel <Felix.Ziesel@xxxxxxxxx>wrote:
**<krishsandy85@xxxxxxxxx> <krishsandy85@xxxxxxxxx> [2011-11-07 11:53]:
Hi David, Andrew & all the others package maintainers,
I already have created an example to show how dull testing can be executed
automatically using Jubula(
https://bugs.eclipse.org/bugs/show_bug.cgi?id=347651).
Imho it has the following advantages:
- You don´t have to do the tests for every release and every target again
- You instantly get report after the build process (getting +/-1
automatically)
- You can track executed tests for every release candidate
- You don´t have to reinvent the wheel again (because you can reuse some
common eclipse workflows and use cases)
- You can use a very nice tool ;-)
I created some very simple tests looking for availability of views,
perspectives, documentation and testing a HelloWorld class.
The tests can be used for Eclipse for Testers and Eclipse for RCP and RAP
Developers but other packages can be involved easily.
I also write a short blog entry about testing the EPP(
http://www.bredex.de/web/index.php/blog_article_de/items/your-packaging-project-needs-you.html
).
If you are interested in getting involved let´s talk about the
possibilties to make it available for you in the building process for Juno.
Regards,
Felix
On 16.11.2011 21:48, David M Williams wrote:
FYI ... I added this Linux Tools testing link to
http://wiki.eclipse.org/EPP/Package_Testing
just for improved cross-referencing. (And, I think it is very good, Andrew
... sets a good example for us all :).
I suspect some other packages could add a little something or links to the
EPP Testing page?
No concrete reason to ... just helps show how it is tested.
I also removed the PHP Package from the test page, since it no longer is a
package.
[image: Inactive hide details for Andrew Overholt ---11/16/2011 12:02:13
PM---Hi, * Sandeep Krishnan <krishsandy85@xxxxxxxxx> [2011-11-]Andrew
Overholt ---11/16/2011 12:02:13 PM---Hi, * Sandeep Krishnan
From: Andrew Overholt <overholt@xxxxxxxxxx> <overholt@xxxxxxxxxx>
To: Eclipse Packaging Project <epp-dev@xxxxxxxxxxx> <epp-dev@xxxxxxxxxxx>,------------------------------
Date: 11/16/2011 12:02 PM
Subject: Re: [epp-dev] Testing of the different packages
Sent by: epp-dev-bounces@xxxxxxxxxxx
Hi,
* Sandeep Krishnan <krishsandy85@xxxxxxxxx> <krishsandy85@xxxxxxxxx>[2011-11-07 11:53]:epp-dev mailing listepp-dev@eclipse.orghttps://dev.eclipse.org/mailman/listinfo/epp-dev
>
> I wanted to know what are the different package leaders testing
For the Linux C/C++ package we have a set of smoke tests:
http://wiki.eclipse.org/Linux_Tools_Project/EPP_Testing
These are probably a bit too verbose and I'd like to see more of them
automated but it's what we use so I thought you'd like to know :)
HTH,
Andrew
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
_______________________________________________
--
BREDEX GmbH
Mauernstr. 33
38100 Braunschweig
Tel.: +49-531-24330-0
Fax: +49-531-24330-99
http: www.bredex.de
Geschäftsführer: Hans-J. Brede, Achim Lörke, Ulrich Obst
Amtsgericht Braunschweig HRB 2450
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
--------------------------------------------------------
BREDEX GmbH
Mauernstr. 33
38100 Braunschweig
Tel.: +49-531-24330-0
Fax: +49-531-24330-99
http: www.bredex.de
Geschäftsführer: Hans-J. Brede, Achim Lörke, Ulrich Obst
Amtsgericht Braunschweig HRB 2450
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev