2:45 a.m.
Hey,
where would one put tests for the aggregator build ?
Looking for such a place to write tests for https://issues.jboss.org/browse/JBIDE-12093
concerning resources that should be in all our aggregated bundles
that would be really tedious to put in every testsuite.
Thus I thought, lets put it in the aggregator build but thats where I got lost inside
build/aggregator.
For some reason the build/aggregator looks like one big dumping ground of different
attempts on a build so not sure where the tests could be placed ?
/max
9:31 p.m.
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/
contains some shared scripts in the root, and then child folders are for
building different types of aggregates:
* bottests-site (deprecated in favour of two sites, one for
coretests-site and one for soatests-site),
* coretests-site (test features/plugins for core components),
* local-site (to assist w/ building and testing locally - see README),
* site (standard core aggregate, might benefit from being renamed),
* soa-site (standard soa tools aggregate),
* soatests-site (test plugins/features for the soa components), and
* webtools-site (which is AS, Archives, and JMX under a special category
which WTP uses to make AS and EAP discoverable server types within their
wizards).
So... if you wanted to nest some test plugins for verifying content on
the sites, I might suggest site/tests/ as a reasonable place to start.
N
On 09/04/2012 03:45 AM, Max Rydahl Andersen wrote:
Hey,
where would one put tests for the aggregator build ?
Looking for such a place to write tests for https://issues.jboss.org/browse/JBIDE-12093
concerning resources that should be in all our aggregated bundles
that would be really tedious to put in every testsuite.
Thus I thought, lets put it in the aggregator build but thats where I got lost inside
build/aggregator.
For some reason the build/aggregator looks like one big dumping ground of different
attempts on a build so not sure where the tests could be placed ?
/max
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
3:04 a.m.
On 05 Sep 2012, at 04:31, Nick Boldt <nboldt(a)redhat.com> wrote:
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/
contains some shared scripts in the root, and then child folders are for building
different types of aggregates:
* bottests-site (deprecated in favour of two sites, one for coretests-site and one for
soatests-site),
* coretests-site (test features/plugins for core components),
* local-site (to assist w/ building and testing locally - see README),
* site (standard core aggregate, might benefit from being renamed),
* soa-site (standard soa tools aggregate),
* soatests-site (test plugins/features for the soa components), and
* webtools-site (which is AS, Archives, and JMX under a special category which WTP uses
to make AS and EAP discoverable server types within their wizards).
So... if you wanted to nest some test plugins for verifying content on the sites, I might
suggest site/tests/ as a reasonable place to start.
well site it self is a eclipse-update-site packaging so putting tests subdirs under it is
not really possible.
I wonder if I could just add a basic java unit test to this one....i'll try that.
/max
N
On 09/04/2012 03:45 AM, Max Rydahl Andersen wrote:
> Hey,
>
> where would one put tests for the aggregator build ?
>
> Looking for such a place to write tests for
https://issues.jboss.org/browse/JBIDE-12093 concerning resources that should be in all our
aggregated bundles
> that would be really tedious to put in every testsuite.
>
> Thus I thought, lets put it in the aggregator build but thats where I got lost inside
build/aggregator.
>
> For some reason the build/aggregator looks like one big dumping ground of different
attempts on a build so not sure where the tests could be placed ?
>
> /max
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
3:43 a.m.
On 09/05/2012 10:04 AM, Max Rydahl Andersen wrote:
On 05 Sep 2012, at 04:31, Nick Boldt <nboldt(a)redhat.com>
wrote:
> So... if you wanted to nest some test plugins for verifying content on the sites, I
might suggest site/tests/ as a reasonable place to start.
well site it self is a eclipse-update-site packaging so putting tests subdirs under it is
not really possible.
I wonder if I could just add a basic java unit test to this one....i'll try that.
Eclipse-update-site lifecycle mapping does not contain any compilation
phase (see
http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/tree/tycho-maven-plu...
), so you'll need to explicitly invoke maven-compiler-plugin...
Something that may work better:
1. Write your test-case in the tests/ module
2. Invoke surefire in the site pom.xml (in an integration-test step) and
reference this test-case in surefire configuration
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
4 a.m.
>
>> So... if you wanted to nest some test plugins for verifying content on the sites,
I might suggest site/tests/ as a reasonable place to start.
>>
> well site it self is a eclipse-update-site packaging so putting tests subdirs under
it is not really possible.
>
> I wonder if I could just add a basic java unit test to this one....i'll try that.
>
Eclipse-update-site lifecycle mapping does not contain any compilation phase (see
http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/tree/tycho-maven-plu...
), so you'll need to explicitly invoke maven-compiler-plugin..
that sucks...
.
Something that may work better:
1. Write your test-case in the tests/ module
where ? you mean create a build/aggregator/tests module?
2. Invoke surefire in the site pom.xml (in an integration-test step)
and reference this test-case in surefire configuration
hmm - okey - that could possibly work.
Would actually allow me to write a general test run for any updatesite now that I think
about it.
/max
4:11 a.m.
On 09/05/2012 11:00 AM, Max Rydahl Andersen wrote:
Something that may work better:
1. Write your test-case in the tests/ module
where ? you mean create a build/aggregator/tests module?
No, I thought about making
it a bundle in the tests/ modules. That's the
purpose of this module: providing classes that are helpful in many
places of JBoss Tools.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
4:39 a.m.
On 05 Sep 2012, at 11:11, Mickael Istria <mistria(a)redhat.com> wrote:
On 09/05/2012 11:00 AM, Max Rydahl Andersen wrote:
> Something that may work better:
> 1. Write your test-case in the tests/ module
>
> where ? you mean create a build/aggregator/tests module?
>
No, I thought about making it a bundle in the tests/ modules. That's the purpose of
this module: providing classes that are helpful in many places of JBoss Tools.
yeah, now i grok what you suggest (have site reference the speicific test dependency) this
makes sense.
trying to make that work - just very slow ;)
/max
4466
days inactive
4467
days old
jbosstools-dev@lists.jboss.org
6 comments
3 participants
participants (3)
-
Max Rydahl Andersen -
Mickael Istria -
Nick Boldt