ros/claude-task-master
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
4357af3f13859d90bca8795215e5d5f1d94abde5
claude-task-master/tests
History
Ralph Khreish 4357af3f13 fix(expand-task): include parent task context in complexity report variant (#1094) 
- Fixed bug where expand task generated generic authentication subtasks
- The complexity-report prompt variant now includes parent task details
- Added comprehensive unit tests to prevent regression
- Added debug logging to help diagnose similar issues

Previously, when using a complexity report with expansionPrompt, only the
expansion guidance was sent to the AI, missing the actual task context.
This caused the AI to generate unrelated generic subtasks.

Fixes the issue where all tasks would get the same generic auth-related
subtasks regardless of their actual purpose (AWS infrastructure, Docker
containerization, etc.)

Co-authored-by: Sadaqat Ali <32377500+sadaqat12@users.noreply.github.com>
2025-08-06 21:00:32 +02:00
..
e2e
fix(core): Implement Boundary-First Tag Resolution (#943)
2025-07-20 00:51:41 +03:00
fixture
feat: Add --append flag to parsePRD command - Fixes #207 (#272)
2025-04-19 23:49:50 +02:00
fixtures
refactor(init): Improve robustness and dependencies; Update template deps for AI SDKs; Silence npm install in MCP; Improve conditional model setup logic; Refactor init.js flags; Tweak Getting Started text; Fix MCP server launch command; Update default model in config template
2025-04-28 04:08:10 -04:00
integration
fix(profiles): fix vscode profile generation (#1027)
2025-07-21 21:17:57 +02:00
manual/prompts
feat: Centralize AI prompts into JSON templates (#882)
2025-07-10 09:52:11 +02:00
unit
fix(expand-task): include parent task context in complexity report variant (#1094)
2025-08-06 21:00:32 +02:00
README.md
chore: run npm run format
2025-04-09 00:30:05 +02:00
setup.js
chore: rename log level environment variable to TASKMASTER_LOG_LEVEL (#417)
2025-05-15 01:09:41 +02:00

README.md

Task Master Test Suite

This directory contains tests for the Task Master CLI. The tests are organized into different categories to ensure comprehensive test coverage.

Test Structure

  • unit/: Unit tests for individual functions and components
  • integration/: Integration tests for testing interactions between components
  • e2e/: End-to-end tests for testing complete workflows
  • fixtures/: Test fixtures and sample data

Running Tests

To run all tests:

npm test

To run tests in watch mode (for development):

npm run test:watch

To run tests with coverage reporting:

npm run test:coverage

Testing Approach

Unit Tests

Unit tests focus on testing individual functions and components in isolation. These tests should be fast and should mock external dependencies.

Integration Tests

Integration tests focus on testing interactions between components. These tests ensure that components work together correctly.

End-to-End Tests

End-to-end tests focus on testing complete workflows from a user's perspective. These tests ensure that the CLI works correctly as a whole.

Test Fixtures

Test fixtures provide sample data for tests. Fixtures should be small, focused, and representative of real-world data.

Mocking

For external dependencies like file system operations and API calls, we use mocking to isolate the code being tested.

  • File system operations: Use mock-fs to mock the file system
  • API calls: Use Jest's mocking capabilities to mock API responses

Test Coverage

We aim for at least 80% test coverage for all code paths. Coverage reports can be generated with:

npm run test:coverage