如何使用jUnit对Servlet过滤器进行单元测试? ServletRequest,ServletResponse,FilterChain

如何解决如何使用jUnit对Servlet过滤器进行单元测试? ServletRequest,ServletResponse,FilterChain

如何用JUnit正确覆盖Filter?

@SlingFilter(order = -700,scope = SlingFilterScope.REQUEST)
public class LoggingFilter implements Filter {

    private final Logger logger = LoggerFactory.getLogger(getClass());

    @Override
    public void doFilter(final ServletRequest request,final ServletResponse response,final FilterChain filterChain) throws IOException,ServletException {

        final SlingHttpServletRequest slingRequest = (SlingHttpServletRequest) request;
        logger.debug("request for {},with selector {}",slingRequest
                .getRequestPathInfo().getResourcePath(),slingRequest
                .getRequestPathInfo().getSelectorString());

        filterChain.doFilter(request,response);
    }

    @Override
    public void init(FilterConfig filterConfig) {}

    @Override
    public void destroy() {}

}

解决方法

调用doFilter并将模拟ServletRequest,ServletResponse和FilterChain作为其参数。

@Test
public void testDoFilter() {
    LoggingFilter filterUnderTest = new LoggingFilter();    
    MockFilterChain mockChain = new MockFilterChain();
    MockServletRequest req = new MockServletRequest("/test.jsp");
    MockServletResponse rsp = new MockServletResponse();

    filterUnderTest.doFilter(req,rsp,mockChain);

    assertEquals("/test.jsp",rsp.getLastRedirect());
}

在实践中,您将希望将设置移至@Before setUp()方法中,并编写更多@Test方法以涵盖所有可能的执行路径。

您可能会使用JMockMockito之类的模拟框架来创建模拟,而不是假设的MockModeService等。我在这里使用过。

与集成测试相反,这是一种单元测试方法。您仅在行使被测设备(和测试代码)。

,

您可以使用以下代码对Junit-5进行测试

@ExtendWith(MockitoExtension.class)
public class LoggingFilterTest{
    
    @InjectMocks
    private LoggingFilter loggingFilter;
    
    @Mock
    private ServletRequest request
    
    @Mock
    private ServletResponse response
    
    @Mock
    private FilterChain filterChain
    
    @Mock
    private RequestPathInfo requestPathInfo;
    
    @Test
    public void testDoFilter() throws IOException,ServletException{
    
        Mockito.when(request.getResourcePath()).thenReturn(requestPathInfo);
        Mockito.when(requestPathInfo.getResourcePath()).thenReturn("/testPath","selectorString");
        Mockito.doNothing().when(filterChain).doFilter(Mockito.eq(request),Mockito.eq(response));
        
        loggingFilter.doFilter(request,response,filterChain);
        
        Mockito.verify(filterChain,times(1)).doFilter(Mockito.eq(request),Mockito.eq(response));
    }
}

如果您使用的是junit4,则将@ExtendWith(MockitoExtension.class)更改为@RunWith(MockitoJUnitRunner.class)

,

如果将AEM Mocks与Junit5一起使用,则可能看起来像这样。

@ExtendWith(AemContextExtension.class)
class SimpleFilterTest {

    private static final AemContext context =  new AemContext(ResourceResolverType.RESOURCERESOLVER_MOCK);

    private static final String RESOURCE_PATH = "/content/test";
    private static final String SELECTOR_STRING = "selectors";

    private static SimpleFilter simpleFilter;
    private static FilterChain filterChain;

    @BeforeAll
    static void setup() {
        simpleFilter = context.registerService(SimpleFilter.class,new SimpleFilter());
        filterChain = context.registerService(FilterChain.class,new MockFilterChain());
    }

    @Test
    @DisplayName("GIVEN the request,WHEN is executed,THEN request should be filtered and contain corresponding header")
    void testDoFilter() throws ServletException,IOException {
        context.requestPathInfo().setResourcePath(RESOURCE_PATH);
        context.requestPathInfo().setSelectorString(SELECTOR_STRING);

        simpleFilter.doFilter(context.request(),context.response(),filterChain);

        assertEquals("true",context.response().getHeader("filtered"));
    }

}

模拟

public class MockFilterChain implements FilterChain {

    @Override
    public void doFilter(final ServletRequest request,final ServletResponse response) throws IOException,ServletException {
        // do nothing
    }

}

一些简单的过滤器

@Component(service = Filter.class)
@SlingServletFilter(scope = SlingServletFilterScope.REQUEST)
@ServiceRanking(-700)
public class SimpleFilter implements Filter {

    @Override
    public void doFilter(final ServletRequest request,final ServletResponse response,final FilterChain filterChain) throws IOException,ServletException {
        final SlingHttpServletRequest slingRequest = (SlingHttpServletRequest) request;
        log.debug("request for {},with selector {}",slingRequest.getRequestPathInfo().getResourcePath(),slingRequest.getRequestPathInfo().getSelectorString());

        final SlingHttpServletResponse slingResponse = (SlingHttpServletResponse) response;
        slingResponse.setHeader("filtered","true");
        filterChain.doFilter(request,response);
    }

    @Override
    public void init(FilterConfig filterConfig) {
    }

    @Override
    public void destroy() {
    }

}

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 <select id="xxx"> SELECT di.id, di.name, di.work_type, di.updated... <where> <if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 <property name="dynamic.classpath" value="tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -> systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-