Enable transaction auto-configuration when using @DataMongoTest and there is a MongoTransactionManager bean

[odrotbohm]

Using @DataMongoTest currently does not enable auto-configuration for transactions which means that tests for transactional behavior, e.g. data not persisted on transaction rollback, will not work out of the box. Adding @ImportAutoConfiguration(TransactionAutoConfiguration.class) (or the equivalent reactive variant) makes this work.

Original StackOverflow post: https://stackoverflow.com/questions/60178310/spring-data-mongodb-transactional-isnt-working/60184283?noredirect=1#comment106470903_60184283

[mp911de]

Note that transactions require a ReplicaSet setup. It makes sense to enable transactional interceptors but we should leave the decision, whether a Mongo Transaction manager gets registered up to the user.

[snicoll]

Thanks @mp911de.

@odrotbohm Spring Boot does not currently auto-configure MongoTransactionManager as far as I can see so I think we need to revisit this a bit. I am not sure adding @Transactional on @DataMongoTest is consistent if we don't auto-configure the necessary infrastructure that is required for it to operate properly.

[spring-projects-issues]

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

[odrotbohm]

I agree. I guess the question is then two-fold:

1. How do we make the difference in bootstrapped setup obvious to users. @DataJpaTests includes transactional auto-configuration, @DataMongoTests doesn't. Shall we add an explicit note about that in the annotation's Javadoc?
2. What's the most idiomatic to add transactional behavior to the tests? Could we maybe use the availability of a MongoDbTransactionManager in the ApplicationContext to automatically enable transactions? That would at least let users properly run into the limitation outlined by Mark which then brings them to the topic they actually need to solve.

WDYT?