0eec95323c
This commit introduces significant enhancements and refactoring to the Task Master CLI, focusing on improved testing, integration with Perplexity AI for research-backed task updates, and core logic refactoring for better maintainability and functionality.
**Testing Infrastructure Setup:**
- Implemented Jest as the primary testing framework, setting up a comprehensive testing environment.
- Added new test scripts to including , , and for streamlined testing workflows.
- Integrated necessary devDependencies for testing, such as , , , , and , to support unit, integration, and end-to-end testing.
**Dependency Updates:**
- Updated and to reflect the latest dependency versions, ensuring project stability and access to the newest features and security patches.
- Upgraded to version 0.9.16 and usage: openai [-h] [-v] [-b API_BASE] [-k API_KEY] [-p PROXY [PROXY ...]]
[-o ORGANIZATION] [-t {openai,azure}]
[--api-version API_VERSION] [--azure-endpoint AZURE_ENDPOINT]
[--azure-ad-token AZURE_AD_TOKEN] [-V]
{api,tools,migrate,grit} ...
positional arguments:
{api,tools,migrate,grit}
api Direct API calls
tools Client side tools for convenience
options:
-h, --help show this help message and exit
-v, --verbose Set verbosity.
-b, --api-base API_BASE
What API base url to use.
-k, --api-key API_KEY
What API key to use.
-p, --proxy PROXY [PROXY ...]
What proxy to use.
-o, --organization ORGANIZATION
Which organization to run as (will use your default
organization if not specified)
-t, --api-type {openai,azure}
The backend API to call, must be `openai` or `azure`
--api-version API_VERSION
The Azure API version, e.g.
'https://learn.microsoft.com/en-us/azure/ai-
services/openai/reference#rest-api-versioning'
--azure-endpoint AZURE_ENDPOINT
The Azure endpoint, e.g.
'https://endpoint.openai.azure.com'
--azure-ad-token AZURE_AD_TOKEN
A token from Azure Active Directory,
https://www.microsoft.com/en-
us/security/business/identity-access/microsoft-entra-
id
-V, --version show program's version number and exit to 4.89.0.
- Added dependency (version 2.3.0) and updated related dependencies to their latest versions.
**Perplexity AI Integration for Research-Backed Updates:**
- Introduced an option to leverage Perplexity AI for task updates, enabling research-backed enhancements to task details.
- Implemented logic to initialize a Perplexity AI client if the environment variable is available.
- Modified the function to accept a parameter, allowing dynamic selection between Perplexity AI and Claude AI for task updates based on API key availability and user preference.
- Enhanced to handle responses from Perplexity AI and update tasks accordingly, including improved error handling and logging for robust operation.
**Core Logic Refactoring and Improvements:**
- Refactored the function to utilize task IDs instead of dependency IDs, ensuring consistency and clarity in dependency management.
- Implemented a new function to rigorously check for both circular dependencies and self-dependencies within tasks, improving task relationship integrity.
- Enhanced UI elements in :
- Refactored to incorporate icons for different task statuses and utilize a object for color mapping, improving visual representation of task status.
- Updated to display colored complexity scores with emojis, providing a more intuitive and visually appealing representation of task complexity.
- Refactored the task data structure creation and validation process:
- Updated the JSON Schema for to reflect a more streamlined and efficient task structure.
- Implemented Task Model Classes for better data modeling and type safety.
- Improved File System Operations for task data management.
- Developed robust Validation Functions and an Error Handling System to ensure data integrity and application stability.
**Testing Guidelines Implementation:**
- Implemented guidelines for writing testable code when developing new features, promoting a test-driven development approach.
- Added testing requirements and best practices for unit, integration, and edge case testing to ensure comprehensive test coverage.
- Updated the development workflow to mandate writing tests before proceeding with configuration and documentation updates, reinforcing the importance of testing throughout the development lifecycle.
This commit collectively enhances the Task Master CLI's reliability, functionality, and developer experience through improved testing practices, AI-powered research capabilities, and a more robust and maintainable codebase.
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 (done)
|
|
# 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: 1 (done)
|
|
### 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: 1 (done), 2 (pending)
|
|
### 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:
|
|
|
|
|