Repository navigation
fix: say spec, not requirement, in the file-anchor warnings - #15
Merged
Merged
Conversation
Tiden renamed its requirements to specs. The jest, playwright and vitest reporters' file_path warnings now say a test cannot be linked to a spec, and an escaping file_path is replaced from the test file (not "the spec file", which would now read as a Tiden spec). READMEs follow. Wording only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The jest, playwright and vitest reporters'
file_pathwarnings say spec: "this test cannot be linked to a spec by file anchor", and an absolute or escapingfile_path"could never match a spec anchor", so the path is derived from "the test file" (was "the spec file", which would now read as a Tiden spec). jest/vitest READMEs follow;Unreleasedchangelog entries added to the three packages. Wording only;fields.file_pathand the warning conditions are unchanged. Ships with the next lockstep release.Test plan
npm run build --workspaces --if-presentnpm run test -w jest(79),-w playwright(107),-w vitest(111),-w commons(514) — all passnpm run lint -w jest|playwright|vitest— 0 errors (pre-existing warnings only)Part of the product-wide rename of requirements → specs. Users already keep requirements in Jira, Linear and Notion, and Tiden calling its own record "requirements" kept raising the same questions (are these my Jira requirements? do I re-type them? which one is the truth?). Tiden's noun is now spec; "requirements" means only a team's own, which Tiden reads and turns into specs.
Rules applied in every repo:
/v1/…/requirements), JSON fields (requirementId), proto, DB, i18n keys, activity codes, agent keys./…/requirementsweb URLs redirect to/specs;tiden requirement …and its old flags stay as aliases.Sibling PRs: qase-tms/tiden-app#623 (web app + backend), qase-tms/tiden-cli#175 (CLI + skills), qase-tms/tiden-mcp-server#26 (MCP tools), qase-tms/tiden-docs#11 (customer docs), qase-tms/tiden-web#33 (tiden.ai), qase-tms/tiden-promo#6 (promo), qase-tms/tiden-connect#30 (connector help), #15 (JS reporters), qase-tms/tiden-phpunit-reporter#9 (PHPUnit reporter), qase-tms/tiden-benchmark#13 (eval scorers), qase-tms/tiden-workspace#133 (GTM vocabulary rules)
Tiden intent branch: intent/2026-10-13-rename-the-user-facing-product
🤖 Generated with Claude Code