SprintBootTest - create only necessary beans
I have a code similar to the follows:
@RunWith(SpringRunner.class)
@SpringBootTest
public class ModelRunnerTest {
@Autowired
private SomeRepository repository;
@Autowired
private SomeSearcher someSearcher;
@Test
public void test(){
someSearcher.search(repository);
}
}
It works - but also create all beans in the same context as the 2 created beans.
This can take a long time (and I run this test every build/deploy).
So, I would like to find a way for the test to load only the necessary beans for the test. In this example it will be only repository & someSearcher.
I know I can provide an alternative implementation for beans using @BeanMock, but the actual implementations for the beans will still be created (although not used).
Any suggestions?
java spring junit spring-boot-test springrunner
asked Nov 15 '18 at 10:21
user1028741user1028741
1,02321939
add a comment |
I have a code similar to the follows:
@RunWith(SpringRunner.class)
@SpringBootTest
public class ModelRunnerTest {
@Autowired
private SomeRepository repository;
@Autowired
private SomeSearcher someSearcher;
@Test
public void test(){
someSearcher.search(repository);
}
}
It works - but also create all beans in the same context as the 2 created beans.
This can take a long time (and I run this test every build/deploy).
So, I would like to find a way for the test to load only the necessary beans for the test. In this example it will be only repository & someSearcher.
I know I can provide an alternative implementation for beans using @BeanMock, but the actual implementations for the beans will still be created (although not used).
Any suggestions?
java spring junit spring-boot-test springrunner
asked Nov 15 '18 at 10:21
user1028741user1028741
1,02321939
you can try to load test application context using @ContextConfiguration and setting profile to test
– Sachin Tiwari
Nov 15 '18 at 10:37
Create them yourself. Also take into account if you use the same context again it will be reused. So if you have 100 tests the context will be constructed only once!.
– M. Deinum
Nov 15 '18 at 11:43
add a comment |
I have a code similar to the follows:
@RunWith(SpringRunner.class)
@SpringBootTest
public class ModelRunnerTest {
@Autowired
private SomeRepository repository;
@Autowired
private SomeSearcher someSearcher;
@Test
public void test(){
someSearcher.search(repository);
}
}
It works - but also create all beans in the same context as the 2 created beans.
This can take a long time (and I run this test every build/deploy).
So, I would like to find a way for the test to load only the necessary beans for the test. In this example it will be only repository & someSearcher.
I know I can provide an alternative implementation for beans using @BeanMock, but the actual implementations for the beans will still be created (although not used).
Any suggestions?
java spring junit spring-boot-test springrunner
asked Nov 15 '18 at 10:21
user1028741user1028741
1,02321939
I have a code similar to the follows:
@RunWith(SpringRunner.class)
@SpringBootTest
public class ModelRunnerTest {
@Autowired
private SomeRepository repository;
@Autowired
private SomeSearcher someSearcher;
@Test
public void test(){
someSearcher.search(repository);
}
}
It works - but also create all beans in the same context as the 2 created beans.
This can take a long time (and I run this test every build/deploy).
So, I would like to find a way for the test to load only the necessary beans for the test. In this example it will be only repository & someSearcher.
I know I can provide an alternative implementation for beans using @BeanMock, but the actual implementations for the beans will still be created (although not used).
Any suggestions?
java spring junit spring-boot-test springrunner
java spring junit spring-boot-test springrunner
asked Nov 15 '18 at 10:21
user1028741user1028741
1,02321939
asked Nov 15 '18 at 10:21
user1028741user1028741
1,02321939
asked Nov 15 '18 at 10:21
user1028741user1028741
1,02321939
asked Nov 15 '18 at 10:21
user1028741user1028741
1,02321939
asked Nov 15 '18 at 10:21
user1028741user1028741
1,02321939
1,02321939
you can try to load test application context using @ContextConfiguration and setting profile to test
– Sachin Tiwari
Nov 15 '18 at 10:37
Create them yourself. Also take into account if you use the same context again it will be reused. So if you have 100 tests the context will be constructed only once!.
– M. Deinum
Nov 15 '18 at 11:43
add a comment |
you can try to load test application context using @ContextConfiguration and setting profile to test
– Sachin Tiwari
Nov 15 '18 at 10:37
Create them yourself. Also take into account if you use the same context again it will be reused. So if you have 100 tests the context will be constructed only once!.
– M. Deinum
Nov 15 '18 at 11:43
you can try to load test application context using @ContextConfiguration and setting profile to test
– Sachin Tiwari
Nov 15 '18 at 10:37
you can try to load test application context using @ContextConfiguration and setting profile to test
– Sachin Tiwari
Nov 15 '18 at 10:37
Create them yourself. Also take into account if you use the same context again it will be reused. So if you have 100 tests the context will be constructed only once!.
– M. Deinum
Nov 15 '18 at 11:43
Create them yourself. Also take into account if you use the same context again it will be reused. So if you have 100 tests the context will be constructed only once!.
– M. Deinum
Nov 15 '18 at 11:43
add a comment |
1 Answer
1
active
oldest
votes
You could use @ContextConfiguration instead of @SpringBootTest to create a custom Spring context for particular classes. Spring Boot further simplifies this with classes designed for particular use-cases e.g. @WebMvcTest or @DataJdbcTest.
This approach however has two main drawbacks:
What are you actually testing with this new limited context? Definitely not the production application since you are not starting the whole Spring context. This can lead to bugs being missed by the tests e.g. bean overriding problems might not be spotted.
SpringRunnerwill attempt to reuse the Spring context between the tests if possible. Starting one big context once and sharing it across all the tests might be faster when you have multiple tests.
answered Nov 15 '18 at 10:28
Karol DowbeckiKarol Dowbecki
22.7k93556
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53317227%2fsprintboottest-create-only-necessary-beans%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
You could use @ContextConfiguration instead of @SpringBootTest to create a custom Spring context for particular classes. Spring Boot further simplifies this with classes designed for particular use-cases e.g. @WebMvcTest or @DataJdbcTest.
This approach however has two main drawbacks:
What are you actually testing with this new limited context? Definitely not the production application since you are not starting the whole Spring context. This can lead to bugs being missed by the tests e.g. bean overriding problems might not be spotted.
SpringRunnerwill attempt to reuse the Spring context between the tests if possible. Starting one big context once and sharing it across all the tests might be faster when you have multiple tests.
answered Nov 15 '18 at 10:28
Karol DowbeckiKarol Dowbecki
22.7k93556
add a comment |
You could use @ContextConfiguration instead of @SpringBootTest to create a custom Spring context for particular classes. Spring Boot further simplifies this with classes designed for particular use-cases e.g. @WebMvcTest or @DataJdbcTest.
This approach however has two main drawbacks:
What are you actually testing with this new limited context? Definitely not the production application since you are not starting the whole Spring context. This can lead to bugs being missed by the tests e.g. bean overriding problems might not be spotted.
SpringRunnerwill attempt to reuse the Spring context between the tests if possible. Starting one big context once and sharing it across all the tests might be faster when you have multiple tests.
answered Nov 15 '18 at 10:28
Karol DowbeckiKarol Dowbecki
22.7k93556
add a comment |
You could use @ContextConfiguration instead of @SpringBootTest to create a custom Spring context for particular classes. Spring Boot further simplifies this with classes designed for particular use-cases e.g. @WebMvcTest or @DataJdbcTest.
This approach however has two main drawbacks:
What are you actually testing with this new limited context? Definitely not the production application since you are not starting the whole Spring context. This can lead to bugs being missed by the tests e.g. bean overriding problems might not be spotted.
SpringRunnerwill attempt to reuse the Spring context between the tests if possible. Starting one big context once and sharing it across all the tests might be faster when you have multiple tests.
answered Nov 15 '18 at 10:28
Karol DowbeckiKarol Dowbecki
22.7k93556
You could use @ContextConfiguration instead of @SpringBootTest to create a custom Spring context for particular classes. Spring Boot further simplifies this with classes designed for particular use-cases e.g. @WebMvcTest or @DataJdbcTest.
This approach however has two main drawbacks:
What are you actually testing with this new limited context? Definitely not the production application since you are not starting the whole Spring context. This can lead to bugs being missed by the tests e.g. bean overriding problems might not be spotted.
SpringRunnerwill attempt to reuse the Spring context between the tests if possible. Starting one big context once and sharing it across all the tests might be faster when you have multiple tests.
answered Nov 15 '18 at 10:28
Karol DowbeckiKarol Dowbecki
22.7k93556
edited Nov 15 '18 at 10:33
answered Nov 15 '18 at 10:28
Karol DowbeckiKarol Dowbecki
22.7k93556
answered Nov 15 '18 at 10:28
Karol DowbeckiKarol Dowbecki
22.7k93556
answered Nov 15 '18 at 10:28
Karol DowbeckiKarol Dowbecki
22.7k93556
22.7k93556
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53317227%2fsprintboottest-create-only-necessary-beans%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
you can try to load test application context using @ContextConfiguration and setting profile to test
– Sachin Tiwari
Nov 15 '18 at 10:37
Create them yourself. Also take into account if you use the same context again it will be reused. So if you have 100 tests the context will be constructed only once!.
– M. Deinum
Nov 15 '18 at 11:43