Add specific annotations for Spring integration testing#2281
Conversation
5a2eae1 to
b35a614
Compare
IlyaMuravjov
left a comment
There was a problem hiding this comment.
It's also desirable to add @Transactional and @AutoConfigureTestDatabase if they are present on the test module class path.
a101ee3 to
de7c03f
Compare
de7c03f to
dadf0bf
Compare
|
|
||
| // Annotations | ||
|
|
||
| enum class AnnotationTarget { |
There was a problem hiding this comment.
May we use kotlin.annotation.AnnotationTarget instead of creating our own type?
There was a problem hiding this comment.
Bue... it may lead the user to a wrong concern that we support or going to support all items from it. Next, in current implementation we are able to do smth like Class(classId) to specify the scope of current or outer class, for example. After that, do not forget that we get salary for the changed lines...
|
|
||
| /** | ||
| * NOTE: use `StatementConstructor.addAnnotation` | ||
| * instead of explicit constructor call. |
There was a problem hiding this comment.
I guess, it's more preferrable to replace all these warnings with TODOs for rearranging packages/classes
There was a problem hiding this comment.
I'm not sure it will be ever done in current codegen. We know about packaging in general. I added this warnings just for other users to avoid additional mess in the code.
There was a problem hiding this comment.
I'm not sure it will be ever done in current codegen
Perhaps it will not, but IMHO todo is much more notable than such a simple comment.
| } | ||
|
|
||
| override fun createDataProviderAnnotations(dataProviderMethodName: String) = mutableListOf<CgAnnotation>() | ||
| override fun addDataProviderAnnotations(dataProviderMethodName: String) { } |
There was a problem hiding this comment.
There is not an error, just annotation is not required.
Description
Fixes #2317
How to test
Should be tested as a part of full integration testing checks.
Self-check list