-
Notifications
You must be signed in to change notification settings - Fork 38.3k
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
Introduce class-level execution phases for @Sql
[SPR-14357]
#18929
Comments
Semukhin Dmitry commented ProposalIntroduce additional public void beforeTestClass(TestContext testContext) throws Exception {
executeSqlScripts(testContext, ExecutionPhase.BEFORE_TEST_CLASS);
} The implementation of Sam Brannen, please share your thoughts on the plan if you have time for that. |
Semukhin Dmitry commented Actually issue #20570 should be marked not as "relates to" but rather "blocked by" |
Sam Brannen commented In what way do you foresee that it is blocked? |
Sam Brannen commented FYI: I took the liberty to edit your comments/proposal. |
Sam Brannen commented
I think the general idea sounds fine. The main issue I see is coming up with a compelling story for implementing both #20570 and #18929, and if we implement both we will then need to test use cases that combine the two (i.e., in order to verify that they work together in harmony and whether or not it makes sense to implement both). So I would appreciate it if you could document that story as you see it. |
Is this still being implemented? |
@Sql
[SPR-14357]
|
urbanq opened SPR-14357 and commented
It would be helpful to introduce class-level support in the
ExecutionPhase
enum used by@Sql
:BEFORE_CLASS
andAFTER_CLASS
.So when executing integration test we can easily run one single SQL script for all test methods in the test class.
Affects: 4.2.6
Reference URL: https://stackoverflow.com/questions/32871817/using-annotation-sql-is-it-possible-to-execute-scripts-in-class-level-before-m
Issue Links:
@Sql
declarations4 votes, 5 watchers
The text was updated successfully, but these errors were encountered: