You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, I have not been able to use that feature with Spring Data.
Specifically, I have tried with Spring Data Neo4j 6.0.0 (via Spring Boot 2.4.0-RC1) in a private repository.
I have the same issue with Spring Data JPA 2.4.0 (via Spring Boot 2.4.0-RC1), as reproducible here: https://github.com/fbiville/spring-data-jpa-nested.
All the instructions to reproduce the issue are described in the aforementioned repository README
Affects: 2.4.1 (2020.0.1)
The text was updated successfully, but these errors were encountered:
Spring Data doesn't contribute to the JUnit test context nor to bootstrap/configure tests. All this is done either by Spring Framework or Spring Boot. @DataJpaTest/@DataNeo4jTest are Spring Boot annotations
Gah, I should have read the fully qualified name before posting here, sorry.
Will open an issue against the appropriate repository then.
Thanks for your quick answer!
Florent Biville opened DATACMNS-1829 and commented
Spring Framework seems to recently support JUnit 5
@Nested
test classes and allow them to inherit the enclosing class configuration (based on my quick reading of spring-projects/spring-framework#19930 and https://github.com/spring-projects/spring-framework/blob/fbb3c5cce73f07679afebbb39980fb971efb9f4f/spring-test/src/test/java/org/springframework/test/context/junit/jupiter/nested/TransactionalNestedTests.java).However, I have not been able to use that feature with Spring Data.
Specifically, I have tried with Spring Data Neo4j 6.0.0 (via Spring Boot 2.4.0-RC1) in a private repository.
I have the same issue with Spring Data JPA 2.4.0 (via Spring Boot 2.4.0-RC1), as reproducible here: https://github.com/fbiville/spring-data-jpa-nested.
All the instructions to reproduce the issue are described in the aforementioned repository README
Affects: 2.4.1 (2020.0.1)
The text was updated successfully, but these errors were encountered: