How to mock class inside another class that being tested?
I'm trying to write an integration test for authentification with Spring Security and JWT. My problem is that during authentification in authentification filter it checks that user is valid in the external system. How can I mock class that makes calls to external system during the test?
Here is a security config:
public class WebSecurityConfig extends WebSecurityConfigurerAdapter {
private final AuthService authService;
public WebSecurityConfig(AuthService authService) {
this.authService = authService;
}
@Bean
public AuthentificationTokenFilter authenticationTokenFilter() {
return new AuthentificationTokenFilter(authService);
}
@Override
protected void configure(HttpSecurity httpSecurity) throws Exception {
httpSecurity.addFilterBefore(authenticationTokenFilter, UsernamePasswordAuthenticationFilter.class);
}
}
I need to mock AuthService
inside AuthentificationTokenFilter
where actual authentification is happening, but I don't directly interact with it and security config. I only trying to make a rest request to RestController
and if authentification is correct then this request should return 200
code.
java spring spring-mvc spring-security mocking
add a comment |
I'm trying to write an integration test for authentification with Spring Security and JWT. My problem is that during authentification in authentification filter it checks that user is valid in the external system. How can I mock class that makes calls to external system during the test?
Here is a security config:
public class WebSecurityConfig extends WebSecurityConfigurerAdapter {
private final AuthService authService;
public WebSecurityConfig(AuthService authService) {
this.authService = authService;
}
@Bean
public AuthentificationTokenFilter authenticationTokenFilter() {
return new AuthentificationTokenFilter(authService);
}
@Override
protected void configure(HttpSecurity httpSecurity) throws Exception {
httpSecurity.addFilterBefore(authenticationTokenFilter, UsernamePasswordAuthenticationFilter.class);
}
}
I need to mock AuthService
inside AuthentificationTokenFilter
where actual authentification is happening, but I don't directly interact with it and security config. I only trying to make a rest request to RestController
and if authentification is correct then this request should return 200
code.
java spring spring-mvc spring-security mocking
1
docs.spring.io/spring-boot/docs/current/reference/htmlsingle/…
– JB Nizet
Nov 23 '18 at 11:24
add a comment |
I'm trying to write an integration test for authentification with Spring Security and JWT. My problem is that during authentification in authentification filter it checks that user is valid in the external system. How can I mock class that makes calls to external system during the test?
Here is a security config:
public class WebSecurityConfig extends WebSecurityConfigurerAdapter {
private final AuthService authService;
public WebSecurityConfig(AuthService authService) {
this.authService = authService;
}
@Bean
public AuthentificationTokenFilter authenticationTokenFilter() {
return new AuthentificationTokenFilter(authService);
}
@Override
protected void configure(HttpSecurity httpSecurity) throws Exception {
httpSecurity.addFilterBefore(authenticationTokenFilter, UsernamePasswordAuthenticationFilter.class);
}
}
I need to mock AuthService
inside AuthentificationTokenFilter
where actual authentification is happening, but I don't directly interact with it and security config. I only trying to make a rest request to RestController
and if authentification is correct then this request should return 200
code.
java spring spring-mvc spring-security mocking
I'm trying to write an integration test for authentification with Spring Security and JWT. My problem is that during authentification in authentification filter it checks that user is valid in the external system. How can I mock class that makes calls to external system during the test?
Here is a security config:
public class WebSecurityConfig extends WebSecurityConfigurerAdapter {
private final AuthService authService;
public WebSecurityConfig(AuthService authService) {
this.authService = authService;
}
@Bean
public AuthentificationTokenFilter authenticationTokenFilter() {
return new AuthentificationTokenFilter(authService);
}
@Override
protected void configure(HttpSecurity httpSecurity) throws Exception {
httpSecurity.addFilterBefore(authenticationTokenFilter, UsernamePasswordAuthenticationFilter.class);
}
}
I need to mock AuthService
inside AuthentificationTokenFilter
where actual authentification is happening, but I don't directly interact with it and security config. I only trying to make a rest request to RestController
and if authentification is correct then this request should return 200
code.
java spring spring-mvc spring-security mocking
java spring spring-mvc spring-security mocking
edited Nov 23 '18 at 14:25
Nikolas
13.6k53669
13.6k53669
asked Nov 23 '18 at 11:21
user2452483user2452483
87111
87111
1
docs.spring.io/spring-boot/docs/current/reference/htmlsingle/…
– JB Nizet
Nov 23 '18 at 11:24
add a comment |
1
docs.spring.io/spring-boot/docs/current/reference/htmlsingle/…
– JB Nizet
Nov 23 '18 at 11:24
1
1
docs.spring.io/spring-boot/docs/current/reference/htmlsingle/…
– JB Nizet
Nov 23 '18 at 11:24
docs.spring.io/spring-boot/docs/current/reference/htmlsingle/…
– JB Nizet
Nov 23 '18 at 11:24
add a comment |
1 Answer
1
active
oldest
votes
Do you really need to mock it using Mockito? Use the advantage of Spring profiles and the annotation @Profile
to distinguish the AuthService
interface implementation for the test
and other environments.
@Service
@Profile("test")
public class MockAuthService implements AuthService {
// ... the mock implementation
}
It only has one method that returns true or false, so I thought to mock it will be easier, but by doing it with profiles it will be easier to add it in every test
– user2452483
Nov 23 '18 at 12:53
@user2452483: Yes, with this approach you might control more of the implementations (against in-memory data, against the dev. database or another one...). I feel this way is easier to test and mainly, you focus on the testing itself than mocking.
– Nikolas
Nov 23 '18 at 14:15
add a comment |
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%2f53445760%2fhow-to-mock-class-inside-another-class-that-being-tested%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
Do you really need to mock it using Mockito? Use the advantage of Spring profiles and the annotation @Profile
to distinguish the AuthService
interface implementation for the test
and other environments.
@Service
@Profile("test")
public class MockAuthService implements AuthService {
// ... the mock implementation
}
It only has one method that returns true or false, so I thought to mock it will be easier, but by doing it with profiles it will be easier to add it in every test
– user2452483
Nov 23 '18 at 12:53
@user2452483: Yes, with this approach you might control more of the implementations (against in-memory data, against the dev. database or another one...). I feel this way is easier to test and mainly, you focus on the testing itself than mocking.
– Nikolas
Nov 23 '18 at 14:15
add a comment |
Do you really need to mock it using Mockito? Use the advantage of Spring profiles and the annotation @Profile
to distinguish the AuthService
interface implementation for the test
and other environments.
@Service
@Profile("test")
public class MockAuthService implements AuthService {
// ... the mock implementation
}
It only has one method that returns true or false, so I thought to mock it will be easier, but by doing it with profiles it will be easier to add it in every test
– user2452483
Nov 23 '18 at 12:53
@user2452483: Yes, with this approach you might control more of the implementations (against in-memory data, against the dev. database or another one...). I feel this way is easier to test and mainly, you focus on the testing itself than mocking.
– Nikolas
Nov 23 '18 at 14:15
add a comment |
Do you really need to mock it using Mockito? Use the advantage of Spring profiles and the annotation @Profile
to distinguish the AuthService
interface implementation for the test
and other environments.
@Service
@Profile("test")
public class MockAuthService implements AuthService {
// ... the mock implementation
}
Do you really need to mock it using Mockito? Use the advantage of Spring profiles and the annotation @Profile
to distinguish the AuthService
interface implementation for the test
and other environments.
@Service
@Profile("test")
public class MockAuthService implements AuthService {
// ... the mock implementation
}
answered Nov 23 '18 at 12:07
NikolasNikolas
13.6k53669
13.6k53669
It only has one method that returns true or false, so I thought to mock it will be easier, but by doing it with profiles it will be easier to add it in every test
– user2452483
Nov 23 '18 at 12:53
@user2452483: Yes, with this approach you might control more of the implementations (against in-memory data, against the dev. database or another one...). I feel this way is easier to test and mainly, you focus on the testing itself than mocking.
– Nikolas
Nov 23 '18 at 14:15
add a comment |
It only has one method that returns true or false, so I thought to mock it will be easier, but by doing it with profiles it will be easier to add it in every test
– user2452483
Nov 23 '18 at 12:53
@user2452483: Yes, with this approach you might control more of the implementations (against in-memory data, against the dev. database or another one...). I feel this way is easier to test and mainly, you focus on the testing itself than mocking.
– Nikolas
Nov 23 '18 at 14:15
It only has one method that returns true or false, so I thought to mock it will be easier, but by doing it with profiles it will be easier to add it in every test
– user2452483
Nov 23 '18 at 12:53
It only has one method that returns true or false, so I thought to mock it will be easier, but by doing it with profiles it will be easier to add it in every test
– user2452483
Nov 23 '18 at 12:53
@user2452483: Yes, with this approach you might control more of the implementations (against in-memory data, against the dev. database or another one...). I feel this way is easier to test and mainly, you focus on the testing itself than mocking.
– Nikolas
Nov 23 '18 at 14:15
@user2452483: Yes, with this approach you might control more of the implementations (against in-memory data, against the dev. database or another one...). I feel this way is easier to test and mainly, you focus on the testing itself than mocking.
– Nikolas
Nov 23 '18 at 14:15
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%2f53445760%2fhow-to-mock-class-inside-another-class-that-being-tested%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
1
docs.spring.io/spring-boot/docs/current/reference/htmlsingle/…
– JB Nizet
Nov 23 '18 at 11:24