-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
regression: forked container unit tests failing #1056
Comments
cc @jbonofre |
@reschke Does downgrading Swissbox in 4.13.6-SNAPSHOT also fix the issue? |
I don't quiet understand the question - the bug report is for what's current in "master"; and that hasn't changed since Nov 2021. |
There is a regression in versions newer 4.13.3 which could be the same or similar and prevents me from upgrading Pax Exam in several Sling projects. Never mind, I will investigate when back at desk. |
Yes, I believe we talk about the same regression (or multiple ones). |
Just checking: is anybody actually working actively on pax-exam? |
Not that I'm aware of depending on your needs osgi-test might be a more lightweight alternative:
but it is all open source so if you want open a PR with a fix and I think it could be merged without much issues, |
@reschke I intended to do some work around junit 5 support and relatives, however ended up not doing so yet. Main difference there is - you can verify system behavior. If you are still interested in asserting internal state of framework or supplied extensions - exam or tools pointed by @laeubi is way to go, as it will give you access to all low level details. For any system level testing test-containers will do the job. I hope to put some more effort into ConnectorIO/connectorio-addons#5 in July and make it a drop-in replacement of higher level tests. |
FYI, I've extracted some of the code from that repository into separate repository. I made also an attempt to separate container handling from customization (what we know as exam options) so they can be applied across different distributions. |
downgrade Swissbox to 1.8.3 until issue with/in Swissbox is fixed
@reschke, Were you able to identify the change in Swissbox which is causing the issue? |
Nope. |
The issue was caused by the introduction of |
Fixed by #1124. |
Downgrading the swissbox dependency to 1.8.3 fixes the issue (that is, reverting #1021)
The text was updated successfully, but these errors were encountered: