Hi,
I have just finished a rough draft [1] of our integration tests using
Pax Exam [2]. Only "CreateNodeTest" until now.
I have had to make some changes in order to re-use our prior
integration testing stuff:
* HttpTestBase [3] doesn´t extend TestCase anymore and extends
PaxExamTestBase [4] inst
On Mon, Apr 6, 2009 at 12:27 PM, Felix Meschberger wrote:
> Bertrand Delacretaz schrieb:
>> ...Can't we just use a specific system property to set the sling.home
>> value for integration tests?...
> ...But having a special system property coded into Sling just for the sake
> of keeping the curre
Hi,
Bertrand Delacretaz schrieb:
>> ...Maybe we would have to start and stop Sling differently. Eg. by
>> launching a separate process with Sling standalone and shutdown that
>> instance after the tests. Such setup could be hooked into the
>> pre-integration-test and post-integration-test phases..
> Redoing our testing infrastructure just for this reason feels a bit
> like overkill to me.
Not only. With Pax Exam we could test Sling deployed on any OSGi
environment (at least on some of them).
Juanjo.
On Mon, Apr 6, 2009 at 9:37 AM, Felix Meschberger wrote:
> Hi Bertrand
>
> Bertrand Delacretaz schrieb:
>> ...Why did we move the "sling" folders from target/sling (where mvn clean
>> kills them) to siblings of src folders?
>> Is that on purpose, or a side effect of other changes?...
> This start
Hi,
Juan José Vázquez Delgado schrieb:
>> Do you know it a bit ? Can you take a stab at converting the current
>> Cargo based setup to be using Pax Exam ?
>
> First time for me. I´m gonna try this and tell us.
Great ! Thanks.
Regards
Felix
> Do you know it a bit ? Can you take a stab at converting the current
> Cargo based setup to be using Pax Exam ?
First time for me. I´m gonna try this and tell us.
Juanjo.
Hi,
Juan José Vázquez Delgado schrieb:
> Hi,
>
>> Maybe we would have to start and stop Sling differently. Eg. by
>> launching a separate process with Sling standalone and shutdown that
>> instance after the tests. Such setup could be hooked into the
>> pre-integration-test and post-integration-t
Hi,
> Maybe we would have to start and stop Sling differently. Eg. by
> launching a separate process with Sling standalone and shutdown that
> instance after the tests. Such setup could be hooked into the
> pre-integration-test and post-integration-test phases.
>
> WDYT ?
Really, I´m not very com
Hi Bertrand
Bertrand Delacretaz schrieb:
> Hi,
>
> I was bitten by this one again, trying to run Sling tests failed due
> to a stale "sling" work folder, or more precisely gave different
> results when run in the launchpad/testing folder vs. top of the source
> code tree.
>
> In my opinion, "mvn
Yeah, that cost me a fair bit of time when I tried starting using Sling
again last week. I patched launchpad/testing/pom.xml to clean some of
the files in that sling folder, but I suspect the right thing is to
delete the whole thing.
https://issues.apache.org/jira/browse/SLING-900
Jim
Carst
Bertrand Delacretaz wrote:
> Hi,
>
> I was bitten by this one again, trying to run Sling tests failed due
> to a stale "sling" work folder, or more precisely gave different
> results when run in the launchpad/testing folder vs. top of the source
> code tree.
>
> In my opinion, "mvn clean test" sh
Hi,
I was bitten by this one again, trying to run Sling tests failed due
to a stale "sling" work folder, or more precisely gave different
results when run in the launchpad/testing folder vs. top of the source
code tree.
In my opinion, "mvn clean test" should have predictable results,
without taki
13 matches
Mail list logo
