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

[testcontainers]: Emit hawkeye lifecycle events from testcontainer startup/teardown

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

@jpoley 已经在做这个了。

开始于 2026年4月18日。

  • #11 来自 @jpoley —— 未关闭

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
冷清
技术栈
typescript

调研方向

首先定位 testcontainer 的启动和 teardown 入口、hawkeye 的事件总线,以及现有的 audit-trail 和 policy-gate 测试。在追踪 coverage 结果的生成方式之前,先定义四种生命周期事件的 payload 及其关联数据。完成的标准是:事件满足 definition of done 中列出的时序、崩溃存活、coverage-gating、audit-trail 和阻断行为。

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

描述

hawkeye high-priority observability testcontainers

Issue: [testcontainers]: Emit hawkeye lifecycle events from testcontainer startup/teardown

Feature: testcontainers
Priority: high
Labels: testcontainers, hawkeye, high-priority, observability

Description

Testcontainers currently have no integration with hawkeye. When a test runs inside a daax testcontainer, hawkeye has no visibility into: which containers started, whether setup succeeded, test coverage produced, or teardown was clean. Hawkeye should receive structured lifecycle events from testcontainer execution so it can enforce quality gates and contribute to the agentic retrospective.

Intel driver: Sofy AI testing agents (sofy.ai, 2026-04-05) — "agents integrate directly into your pipelines and act as MCP agents communicating with other agents." AWS DevOps Agent GA — agent-level observability is becoming a first-class CI concern. Martin Fowler harness engineering — the harness needs to observe the entire test lifecycle.

What

Define hawkeye lifecycle event schema for testcontainers:

  • testcontainer.started — container ID, image, services, timestamp
  • testcontainer.ready — readiness time, health check results
  • testcontainer.test.run — test file, pass/fail, coverage delta
  • testcontainer.teardown — cleanup success/failure, resource cleanup confirmation

Emit these events via hawkeye's event bus during test execution.

Why

Without this visibility, hawkeye quality gates can't enforce test coverage requirements that span container-level integration tests. The retrospective loop also needs this data to correlate agent-written code with test outcomes.

Definition of Done

  • Each lifecycle event is emitted to hawkeye event bus within 100ms of the underlying event
  • testcontainer.test.run event includes coverage delta (not just pass/fail)
  • Hawkeye policy can gate on coverage.delta < -5% (reject if coverage drops by more than 5 points)
  • Events are visible in hawkeye audit trail with container ID as correlation key
  • Test: run a testcontainer that fails coverage gate → hawkeye blocks the agent's next action and emits actionable feedback
  • Events survive testcontainer crash (emitted before teardown, not after)
主要语言
TypeScript
星标
0
派生
0
PR 合并指标
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

daax-dev/daax-devtools 的其他 Issue

查看 daax-dev/daax-devtools 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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