Oh hell yeah… brother, you just made my day. Thanks Eric!
> On Mar 5, 2021, at 5:13 PM, Eric Norman wrote:
>
> Hi Cris,
>
> I took a quick look and noticed a couple of things:
>
> 1. It looks like the package that contains your service interfaces needs to
> be exported. The problem is that
Hi Cris,
I took a quick look and noticed a couple of things:
1. It looks like the package that contains your service interfaces needs to
be exported. The problem is that the service interface class that you are
trying to inject is not visible to the osgi bundle that contains the test
class. Th
Hi all,
You all have been very helpful as I continuing learning about Pax Exam testing.
After some time, I patched the oak bundles version to 1.32. My test logs the
bundles names and states for each; as shown below all bundles but one bundle
report status:active
...
message=org.apache.sling.aut
Am 05.03.2021 um 16:24 schrieb Cris Rockwell:
The hard part about Pax exam testing is getting the project bundle active given
the dependency versions provided by the testing instance. I tried patching the
test instance maven bundles and versions, but gave up after a certain point.
Instead what
The hard part about Pax exam testing is getting the project bundle active given
the dependency versions provided by the testing instance. I tried patching the
test instance maven bundles and versions, but gave up after a certain point.
Instead what I trying is logging the bundles and version
On Wednesday, 3 March 2021 19:17:01 CET Eric Norman wrote:
> Hi Oliver,
>
> I don't get it – where are the requirements for Scripting and CA Config
>
> > coming from?
>
> Ok, let me try to unwind what I was seeing.
>
> The scripting feature got pulled into the set as required because the
> "org
Hi Oliver,
I don't get it – where are the requirements for Scripting and CA Config
> coming from?
Ok, let me try to unwind what I was seeing.
The scripting feature got pulled into the set as required because the
"org.apache.sling:org.apache.sling.starter:slingosgifeature:base:12-SNAPSHOT"
featu
On Tuesday, 2 March 2021 21:35:46 CET Eric Norman wrote:
> Hi Oliver,
>
> Sure I gave it a shot and I stashed the code changes for what I came up
> with at [1] if you wish to review. Most of the effort was to create a
> simple tool to scan all the possible features and find out what bundles are
>
Hi Oliver,
Sure I gave it a shot and I stashed the code changes for what I came up
with at [1] if you wish to review. Most of the effort was to create a
simple tool to scan all the possible features and find out what bundles are
included in each of those and then scan each of those bundles to fin
On Tuesday, 2 March 2021 01:04:06 CET Eric Norman wrote:
> Hi Oliver,
Hi Eric,
> I'm not sure about how a "feature model" feature would express dependencies
> on other features or whether that is even necessary.
>
> But as an experiment, I just tried to create a simple aggregate feature
> that c
Hi Oliver,
I'm not sure about how a "feature model" feature would express dependencies
on other features or whether that is even necessary.
But as an experiment, I just tried to create a simple aggregate feature
that contains just the jcr maintenance feature and nothing else.
During the build th
On Monday, 1 March 2021 18:51:42 CET Eric Norman wrote:
> Hi Oliver,
Hi Eric,
> The problem I frequently run into is that the default configurations from
> SlingOptions are almost always providing versions of bundles that are too
> old to use for testing new features. And then at that point it r
Hi Oliver,
The problem I frequently run into is that the default configurations from
SlingOptions are almost always providing versions of bundles that are too
old to use for testing new features. And then at that point it requires a
lot of research and trial and error to find a compatible set of
On Friday, 26 February 2021 18:54:28 CET Bertrand Delacretaz wrote:
> Hi,
>
> On Fri, Feb 26, 2021 at 6:31 PM Eric Norman wrote:
> > ...Someday, maybe the sling feature model could be used to derive the
> > paxexam configuration so it would be less mysterious and easier to
> > debug?..
This can
It looks like you have the webconsole bundles in your configuration so if
you can figure out what http port it is running on, then you can try using
the felix webconsole at http://localhost:[httpPort]/system/console to
inspect what is there. This is assuming you can keep the test running long
enou
Thanks again Eric and Bertand for the feedback. After more wrangling the
osgi wiring, a basic test passed.
https://github.com/apache/sling-whiteboard/blob/SLING-9397/improve-test-coverage/saml-handler/src/test/java/org/apache/sling/auth/saml2/impl/SamlHandlerIT.java
But to write useful tests, I n
Hi,
On Fri, Feb 26, 2021 at 6:31 PM Eric Norman wrote:
> ...Someday, maybe the sling feature model could be used to derive the paxexam
> configuration so it would be less mysterious and easier to debug?..
That would be great, and in the meantime I suppose the various
versions of the lists of bun
Glad to hear that you are getting further along.
Per OAK-9105, it looks like oak version 1.32.0 has defined the required
minimum version of jackrabbit as version 2.20.1. So if you are switching
to oak 1.32.0 then it means you have to also switch the jackrabbit bundles
in your configuration to ver
Hi,
On Fri, Feb 26, 2021 at 4:28 PM Cris Rockwell wrote:
> ...Now my tests fail because of bundle wiring according to the log …
Getting the right set of bundles is often a bit tricky, your best bet
might be to start with a known working setup like [1] and remove
whatever you don't need.
-Bertra
Thank you! I was indeed missing both the org.apache.felix.framework and
@RunWith(PaxExam.class)
Now my tests fail because of bundle wiring according to the log …
target/failsafe-reports/org.apache.sling.auth.saml2.impl.SamlHandlerIT-output.txt
my configuration looks like this
@Configuration
pu
Hi,
On Fri, Feb 26, 2021 at 12:09 AM Cris Rockwell wrote:
> I was wondering if someone knowledgable about PAX testing in Sling could help
> me out with my Sling Whiteboard project (saml-handler) [1] on branch
> SLING-9397/improve-test-coverage...
FWIW, https://github.com/apache/sling-org-apache-
Also, you'll need to add a version of the felix framework as a dependency
with something like this:
org.apache.felix
org.apache.felix.framework
6.0.3
test
On Thu, Feb 25, 2021 at 3:18 PM Eric Norman wrote:
> Hi,
> I think you might be missing
Hi,
I think you might be missing the annotation declaring that you want to use
the PaxExam test runner for the test class.
For example, something like this may get you further:
import org.ops4j.pax.exam.junit.PaxExam;
import org.junit.runner.RunWith;
@RunWith(PaxExam.class)
On Thu, Feb 25, 202
Hello it’s me again
I was wondering if someone knowledgable about PAX testing in Sling could help
me out with my Sling Whiteboard project (saml-handler) [1] on branch
SLING-9397/improve-test-coverage
The project uses Java 11, but I think that’s supported and should be fine. The
pom [2] should
24 matches
Mail list logo
