-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
QuarkusTestExtension
fails to run @AfterAll
with nested test classes and per-class test instance lifecycle
#25812
Comments
@Sgitario since you've made various fixes for the nested class support, would you like to tackle this one? |
Before these changes, we were creating instances regardless even though the parent classes were already created. This pull request fixes this issue and adds a test coverage when running nested classes with lifecycle test instance. Fix quarkusio#25812
Still fails in
As I mentioned in the #25831, the added |
@ivansenic you're right. This is still not working for the methods annotated with |
The issue was not completely fixed in the commit quarkusio@b306d8a. The problem was that we were clearing out all the outer instances and hence the current class was not matching with the current test instance. Fix quarkusio#25812
The issue was not completely fixed in the commit quarkusio@b306d8a. The problem was that we were clearing out all the outer instances and hence the current class was not matching with the current test instance. Fix quarkusio#25812
The issue was not completely fixed in the commit quarkusio@b306d8a. The problem was that we were clearing out all the outer instances and hence the current class was not matching with the current test instance. Fix quarkusio#25812 (cherry picked from commit 328e679)
Describe the bug
I am hitting an
IllegalArgumentException
with the following test setup. Seems that after all is run with theeffectiveTestInstance
being a instance of aNestedTest
class, which is not a sub-class of the mainTest
class.Stacktrace:
Expected behavior
Exception is not raised and test runs fine.
Actual behavior
Test fails on the
Class Configuration
"step".How to Reproduce?
Use the test class example I provided.
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
2.9.1.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: