jdaugherty opened a new issue, #313:
URL: https://github.com/apache/grails-intellij-plugin/issues/313

   
[https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000474324-Grails-integration-tests-incorrectly-running-as-unit-tests-since-last-intellij-update-2017-2-1-causing-No-transactionManager-was-specified-errors?page=1#community_comment_115000402384](https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000474324-Grails-integration-tests-incorrectly-running-as-unit-tests-since-last-intellij-update-2017-2-1-causing-No-transactionManager-was-specified-errors?page=1#community_comment_115000402384)
   
   Some details from the forum above. Test case project attached. Steps:
   
   1. Open project (grails 3.2.11) as gradle with auto import
   2. Right click on src/integration-tests -> Run All Tests
   Immediate failure:
   ```
   java.lang.IllegalStateException: No transactionManager was specified. Using 
@Transactional or @Rollback requires a valid configured transaction manager. If 
you are running in a unit test ensure the test has been properly configured and 
that you run the test suite not an individual test method.
   
       at 
grails.transaction.GrailsTransactionTemplate.<init>(GrailsTransactionTemplate.groovy:60)
       at PersonIntegrationSpec.Creating people should 
work(PersonIntegrationSpec.groovy)
   ```
   - It appears that the grails integration environment isn't starting, and the 
test is running as though it were a unit test, which it is not.
   - grails test-app works fine
   
   Host System:
   IntelliJ IDEA Ultimate 2017.2.1 Build #IU-172.3544.35 July 31 / JRE 
1.8.0_152-release-915b6 x86_64
   java 8u131-zulu
   grails 3.2.11
   macOS Sierra 10.12.6
   
   ---
   
   *Imported from 
[IDEA-176984](https://youtrack.jetbrains.com/issue/IDEA-176984) · Type: Bug · 
Votes: 1*
   *Comments, attachments, dates and reporter are not part of the export — 
follow the link above for the full history.*
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to