c5738a2513
This commit introduces a comprehensive set of skipped tests to both and . These skipped tests serve as a blueprint for future test implementation, outlining the necessary test cases for currently untested functionalities.
- Ensures sync with bin/ folder by adding -r/--research to the command
- Fixes an issue that improperly parsed command line args
- Ensures confirmation card on dependency add/remove
- Properly formats some sub-task dependencies
**Potentially addressed issues:**
While primarily focused on adding test coverage, this commit also implicitly addresses potential issues by:
- **Improving error handling coverage:** The addition of skipped tests for error scenarios in functions like , , , and highlights areas where error handling needs to be robustly tested and potentially improved in the codebase.
- **Enhancing dependency validation:** Skipped tests for include validation of dependencies, prompting a review of the dependency validation logic and ensuring its correctness.
- **Standardizing test coverage:** By creating a clear roadmap for testing all functions, this commit contributes to a more standardized and complete test suite, reducing the likelihood of undiscovered bugs in the future.
**task-manager.test.js:**
- Added skipped test blocks for the following functions:
- : Includes tests for handling valid JSON responses, malformed JSON, missing tasks in responses, Perplexity AI research integration, Claude fallback, and parallel task processing.
- : Covers tests for updating tasks based on context, handling Claude streaming, Perplexity AI integration, scenarios with no tasks to update, and error handling during updates.
- : Includes tests for generating task files from , formatting dependencies with status indicators, handling tasks without subtasks, empty task arrays, and dependency validation before file generation.
- : Covers tests for updating task status, subtask status using dot notation, updating multiple tasks, automatic subtask status updates, parent task update suggestions, and handling non-existent task IDs.
- : Includes tests for updating regular and subtask statuses, handling parent tasks without subtasks, and non-existent subtask IDs.
- : Covers tests for displaying all tasks, filtering by status, displaying subtasks, showing completion statistics, identifying the next task, and handling empty task arrays.
- : Includes tests for generating subtasks, using complexity reports for subtask counts, Perplexity AI integration, appending subtasks, skipping completed tasks, and error handling during subtask generation.
- : Covers tests for expanding all pending tasks, sorting by complexity, skipping tasks with existing subtasks (unless forced), using task-specific parameters from complexity reports, handling empty task arrays, and error handling for individual tasks.
- : Includes tests for clearing subtasks from specific and multiple tasks, handling tasks without subtasks, non-existent task IDs, and regenerating task files after clearing subtasks.
- : Covers tests for adding new tasks using AI, handling Claude streaming, validating dependencies, handling malformed AI responses, and using existing task context for generation.
**utils.test.js:**
- Added skipped test blocks for the following functions:
- : Tests for logging messages according to log levels and filtering messages below configured levels.
- : Tests for reading and parsing valid JSON files, handling file not found errors, and invalid JSON formats.
- : Tests for writing JSON data to files and handling file write errors.
- : Tests for escaping double quotes in prompts and handling prompts without special characters.
- : Tests for reading and parsing complexity reports, handling missing report files, and custom report paths.
- : Tests for finding tasks in reports by ID, handling non-existent task IDs, and invalid report structures.
- : Tests for verifying existing task and subtask IDs, handling non-existent IDs, and invalid inputs.
- : Tests for formatting numeric and string task IDs and preserving dot notation for subtasks.
- : Tests for detecting simple and complex cycles in dependency graphs, handling acyclic graphs, and empty dependency maps.
These skipped tests provide a clear roadmap for future test development, ensuring comprehensive coverage for core functionalities in both modules. They document the intended behavior of each function and outline various scenarios, including happy paths, edge cases, and error conditions, thereby improving the overall test strategy and maintainability of the Task Master CLI.
78 lines
3.9 KiB
Plaintext
78 lines
3.9 KiB
Plaintext
# Task ID: 22
|
|
# Title: Create Comprehensive Test Suite for Task Master CLI
|
|
# Status: in-progress
|
|
# Dependencies: 21
|
|
# Priority: high
|
|
# Description: Develop a complete testing infrastructure for the Task Master CLI that includes unit, integration, and end-to-end tests to verify all core functionality and error handling.
|
|
# Details:
|
|
Implement a comprehensive test suite using Jest as the testing framework. The test suite should be organized into three main categories:
|
|
|
|
1. Unit Tests:
|
|
- Create tests for all utility functions and core logic components
|
|
- Test task creation, parsing, and manipulation functions
|
|
- Test data storage and retrieval functions
|
|
- Test formatting and display functions
|
|
|
|
2. Integration Tests:
|
|
- Test all CLI commands (create, expand, update, list, etc.)
|
|
- Verify command options and parameters work correctly
|
|
- Test interactions between different components
|
|
- Test configuration loading and application settings
|
|
|
|
3. End-to-End Tests:
|
|
- Test complete workflows (e.g., creating a task, expanding it, updating status)
|
|
- Test error scenarios and recovery
|
|
- Test edge cases like handling large numbers of tasks
|
|
|
|
Implement proper mocking for:
|
|
- Claude API interactions (using Jest mock functions)
|
|
- File system operations (using mock-fs or similar)
|
|
- User input/output (using mock stdin/stdout)
|
|
|
|
Ensure tests cover both successful operations and error handling paths. Set up continuous integration to run tests automatically. Create fixtures for common test data and scenarios. Include test coverage reporting to identify untested code paths.
|
|
|
|
# Test Strategy:
|
|
Verification will involve:
|
|
|
|
1. Code Review:
|
|
- Verify test organization follows the unit/integration/end-to-end structure
|
|
- Check that all major functions have corresponding tests
|
|
- Verify mocks are properly implemented for external dependencies
|
|
|
|
2. Test Coverage Analysis:
|
|
- Run test coverage tools to ensure at least 80% code coverage
|
|
- Verify critical paths have 100% coverage
|
|
- Identify any untested code paths
|
|
|
|
3. Test Quality Verification:
|
|
- Manually review test cases to ensure they test meaningful behavior
|
|
- Verify both positive and negative test cases exist
|
|
- Check that tests are deterministic and don't have false positives/negatives
|
|
|
|
4. CI Integration:
|
|
- Verify tests run successfully in the CI environment
|
|
- Ensure tests run in a reasonable amount of time
|
|
- Check that test failures provide clear, actionable information
|
|
|
|
The task will be considered complete when all tests pass consistently, coverage meets targets, and the test suite can detect intentionally introduced bugs.
|
|
|
|
# Subtasks:
|
|
## 1. Set Up Jest Testing Environment [done]
|
|
### Dependencies: None
|
|
### Description: Configure Jest for the project, including setting up the jest.config.js file, adding necessary dependencies, and creating the initial test directory structure. Implement proper mocking for Claude API interactions, file system operations, and user input/output. Set up test coverage reporting and configure it to run in the CI pipeline.
|
|
### Details:
|
|
|
|
|
|
## 2. Implement Unit Tests for Core Components [pending]
|
|
### Dependencies: 22.1
|
|
### Description: Create a comprehensive set of unit tests for all utility functions, core logic components, and individual modules of the Task Master CLI. This includes tests for task creation, parsing, manipulation, data storage, retrieval, and formatting functions. Ensure all edge cases and error scenarios are covered.
|
|
### Details:
|
|
|
|
|
|
## 3. Develop Integration and End-to-End Tests [pending]
|
|
### Dependencies: 22.1, 22.2
|
|
### Description: Create integration tests that verify the correct interaction between different components of the CLI, including command execution, option parsing, and data flow. Implement end-to-end tests that simulate complete user workflows, such as creating a task, expanding it, and updating its status. Include tests for error scenarios, recovery processes, and handling large numbers of tasks.
|
|
### Details:
|
|
|
|
|