Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Testing framework feedback and improvements

未关闭
#1,663 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
typescript
领域
testing-qa

调研方向

Start by locating the current testing framework and the testenv.exec entry point, then compare how handlers and filters are tested today. Done should include a decided design and tests covering handler hit counts, event order and input assertions, deletion, and intermediate results.

由索引模型根据 Issue 内容生成。

描述

The current testing framework is a good step to being able to check a handlers and filters but has some limitations. Based on feedback we can make improvements to give more control over tests

Example:
import {xxx_event_handler} from '../src/';

it('test XXX event handler for block #123', async () => {
    store = Mock.fn();...
    // blockheight, handler_name, injection, callback
    await testenv.exec(1234, 'xxx_event_handler', {store}, (data) => {
        // assert data.length, how many times it is expected to be hit at this height
        // loop data element, assert content/order of the matching events
        // invoke real handler
        for (const evt of data) {
            await xxx_event_handler(evt);
            // write store asserts
        }
    })
}); 
Advantages:
  • more assertions than the store output, e.g
    • times the handler is hit in the given height
    • order of events hitting the given handler
    • assert the input of the handler
  • assert deletion
  • assert intermediate results
主要语言
TypeScript
星标
18.7k
派生
396
PR 合并指标
30 天内没有已合并 PR

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

subquery/subql 的其他 Issue

查看 subquery/subql 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。