Files
librefang-registry/workflows/test-generation.toml
T
Evan 7881d327a5 refactor: migrate icon fields from emoji to lucide:<name> tokens (#63)
* refactor: migrate icon fields from emoji to lucide:<name> tokens

Every TOML manifest's `icon = "<emoji>"` line is replaced with
`icon = "lucide:<kebab-name>"` — a reference to a lucide-react icon,
which the librefang.ai site and dashboard render as crisp SVG. Reasons
for the switch:

- Emoji render very differently across OS/browser/font stacks; the
  registry catalog looked inconsistent from one row to the next.
- Five manifests (clip / creator / linkedin / reddit / twitter) had
  their icons stored as literal Python-style escape strings
  ("\\U0001F3AC") because the TOML parser upstream never decoded
  them. Switching away from emoji drops that class of bug entirely.
- As a drive-by, also decode the \\uXXXX accent escapes in the
  [i18n.fr] block of hands/creator/HAND.toml so "Créateur" shows
  up correctly.

87 files touched. example manifests left untouched (still "TODO").

* fix: backfill i18n name + drop the single-member email category

- Every existing [i18n.<lang>] block now has a `name` field. 60 files
  previously translated description but kept the English name
  implicitly — which rendered as "some English some Chinese" in the
  registry UI. Fill in the missing name from the English brand (or a
  known localized equivalent: DingTalk→钉钉, Feishu→飞书, Email→
  电子邮件 / メール / E-Mail / Correo / Courriel, and a handful of
  hands that have Chinese product names like 视频剪辑 Hand).
- channels/email.toml was the only item under category="email";
  reclassify it as "messaging" so the sub-category filter chip list
  on the category page isn't littered with singletons.

* feat(i18n): localize 76 agents/integrations/plugins into 7 languages

Adds full [i18n.zh], [i18n.zh-TW], [i18n.ja], [i18n.ko], [i18n.de],
[i18n.es], [i18n.fr] blocks with name + description to every manifest
that previously shipped English-only.

Coverage:
- 32 agents (academic-researcher, analyst, architect, assistant,
  code-reviewer, coder, customer-support, data-scientist, debugger,
  devops-lead, doc-writer, email-assistant, health-tracker,
  hello-world, home-automation, legal-assistant, meeting-assistant,
  ops, orchestrator, personal-finance, planner, recipe-assistant,
  recruiter, researcher, sales-assistant, security-auditor,
  social-media, test-engineer, translator, travel-planner, tutor,
  writer)
- 33 integrations (AWS, Azure, Bitbucket, Brave Search, Discord,
  Dropbox, Elasticsearch, Exa Search, Fetch, Filesystem, GCP, Git,
  GitHub, GitLab, Gmail, Google Calendar, Google Drive, Google Maps,
  Jira, Linear, Memory, MongoDB, Notion, PostgreSQL, Puppeteer, Redis,
  Sentry, Sequential Thinking, Slack, SQLite, Teams, Time, Todoist) —
  brand names kept as-is across all locales, only descriptions
  translated.
- 11 plugins (auto-summarizer, context-decay, conversation-logger,
  episodic-memory, guardrails, keyword-memory, mempalace-indexer,
  sentiment-tracker, todo-tracker, topic-memory, user-profile)

The descriptions are one-line summaries — hand-translated rather than
machine-generated, so technical terms (MCP, PR, CI/CD, etc.) stay
consistent across locales.

* feat(i18n): close remaining per-lang gaps for channels, workflows, devteam

Third pass on i18n coverage. Every non-example manifest now carries a
full set of [i18n.zh], [i18n.zh-TW], [i18n.ja], [i18n.ko], [i18n.de],
[i18n.es], [i18n.fr] blocks.

- 44 channel adapters: added French descriptions (zh/zh-TW/ja/ko/de/es
  were already present). Brand names kept as-is in all locales so users
  recognize Discord / Slack / LINE / etc. consistently.
- 22 workflows: filled zh-TW / ja / ko / de / es / fr blocks. Each
  translation mirrors the existing zh one in structure and tone so the
  catalog reads consistently across locales.
- hands/devteam/HAND.toml: added the four langs that were missing
  (zh-TW, de, es, fr).

Only the 6 templates under examples/ are left without i18n blocks on
purpose — they still contain "TODO:" placeholders.
2026-04-17 22:04:26 +09:00

97 lines
2.9 KiB
TOML
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
id = "test-generation"
name = "Test Suite Generation"
description = "Analyse code to generate comprehensive unit tests, integration tests, and edge case coverage."
category = "engineering"
tags = ["testing", "quality", "engineering", "tdd"]
[i18n.zh]
name = "测试用例生成"
description = "分析代码,生成完整的单元测试、集成测试和边界情况覆盖。"
[[parameters]]
name = "code"
description = "Source code to generate tests for"
param_type = "string"
required = true
[[parameters]]
name = "language"
description = "Programming language and test framework to use"
param_type = "string"
required = false
default = "auto-detect"
[[steps]]
name = "code_analysis"
prompt_template = """
Analyse the following {{language}} code as a QA engineer:
1. List every public function/method and its contract (inputs → outputs)
2. Identify all branches and conditional paths
3. Note external dependencies that need mocking
4. Flag complex logic most likely to contain bugs
5. List data types and their valid/invalid ranges
Code:
{{code}}
"""
[[steps]]
name = "edge_cases"
prompt_template = """
Based on the code analysis, enumerate all edge cases and boundary conditions:
- Null/empty/zero inputs
- Maximum/minimum values
- Concurrent access scenarios
- Error propagation paths
- State machine transitions
- External dependency failures
Code analysis:
{{code_analysis}}
"""
depends_on = ["code_analysis"]
[[steps]]
name = "test_suite"
prompt_template = """
Write a complete test suite in {{language}} covering:
1. **Happy path tests** — one per public function
2. **Edge case tests** — from the edge case list
3. **Error handling tests** — each error path
4. **Integration tests** — cross-component interactions
Use descriptive test names following the pattern: `test_<function>_<scenario>_<expected_result>`.
Include setup/teardown where needed. Add a comment explaining the intent of non-obvious tests.
Code:
{{code}}
Edge cases:
{{edge_cases}}
"""
depends_on = ["code_analysis", "edge_cases"]
[i18n.zh-TW]
name = "測試套件生成"
description = "分析程式碼,產生完整的單元測試、整合測試與邊界情況覆蓋。"
[i18n.ja]
name = "テストスイート生成"
description = "コードを解析し、単体テスト・統合テスト・エッジケースを網羅したテストスイートを生成。"
[i18n.ko]
name = "테스트 스위트 생성"
description = "코드를 분석해 단위 테스트, 통합 테스트, 엣지 케이스를 포괄하는 테스트 스위트를 생성."
[i18n.de]
name = "Test-Suite-Generierung"
description = "Code analysieren und umfassende Unit-Tests, Integrationstests und Edge-Case-Abdeckung erzeugen."
[i18n.es]
name = "Generación de pruebas"
description = "Analiza el código para generar pruebas unitarias, de integración y cobertura de casos límite."
[i18n.fr]
name = "Génération de tests"
description = "Analyser le code pour générer tests unitaires, tests d’intégration et couverture des cas limites."