thanh-kit 2.5.0 → 2.5.2

package/templates/skills/tasks-test-generation/SKILL.md

@@ -1,433 +0,0 @@
----
-name: test-generation
-description: Use for DEVELOPER-focused unit/integration test code with xUnit (C#) and Jest (Angular) patterns. Provides ready-to-use test templates for commands, queries, entities, and components. Best for implementing actual test code. NOT for QA test specifications (use test-generation instead).
-allowed-tools: Read, Write, Edit, Grep, Glob, Bash
----
-
-# Test Generation Workflow
-
-## When to Use This Skill
-
-- Creating unit tests for new code
-- Adding tests for bug fixes
-- Integration test development
-- Test coverage improvement
-
-## Pre-Flight Checklist
-
-- [ ] Identify code to test (command, query, entity, component)
-- [ ] Find existing test patterns: `grep "Test.*{Feature}" --include="*.cs"`
-- [ ] Determine test type (unit, integration, e2e)
-- [ ] Identify dependencies to mock
-
-## File Locations
-
-### Backend Tests
-
-```
-tests/
-└── {Service}.Tests/
-    ├── UnitTests/
-    │   ├── Commands/
-    │   │   └── Save{Entity}CommandTests.cs
-    │   ├── Queries/
-    │   │   └── Get{Entity}ListQueryTests.cs
-    │   └── Entities/
-    │       └── {Entity}Tests.cs
-    └── IntegrationTests/
-        └── {Feature}IntegrationTests.cs
-```
-
-### Frontend Tests
-
-```
-src/PlatformExampleAppWeb/apps/{app}/src/app/
-└── features/
-    └── {feature}/
-        ├── {feature}.component.spec.ts
-        └── {feature}.store.spec.ts
-```
-
-## Pattern 1: Command Handler Unit Test
-
-```csharp
-public class SaveEmployeeCommandTests
-{
-    private readonly Mock<IPlatformQueryableRootRepository<Employee, string>> _employeeRepoMock;
-    private readonly Mock<IPlatformApplicationRequestContextAccessor> _contextMock;
-    private readonly SaveEmployeeCommandHandler _handler;
-
-    public SaveEmployeeCommandTests()
-    {
-        _employeeRepoMock = new Mock<IPlatformQueryableRootRepository<Employee, string>>();
-        _contextMock = new Mock<IPlatformApplicationRequestContextAccessor>();
-
-        // Setup default context
-        var requestContext = new Mock<IPlatformApplicationRequestContext>();
-        requestContext.Setup(x => x.UserId()).Returns("test-user-id");
-        requestContext.Setup(x => x.CurrentCompanyId()).Returns("test-company-id");
-        _contextMock.Setup(x => x.Current).Returns(requestContext.Object);
-
-        _handler = new SaveEmployeeCommandHandler(
-            Mock.Of<ILoggerFactory>(),
-            Mock.Of<IPlatformUnitOfWorkManager>(),
-            Mock.Of<IServiceProvider>(),
-            Mock.Of<IPlatformRootServiceProvider>(),
-            _employeeRepoMock.Object
-        );
-    }
-
-    [Fact]
-    public async Task HandleAsync_CreateEmployee_ReturnsNewEmployee()
-    {
-        // Arrange
-        var command = new SaveEmployeeCommand
-        {
-            Name = "John Doe",
-            Email = "john@example.com"
-        };
-
-        _employeeRepoMock
-            .Setup(x => x.CreateAsync(It.IsAny<Employee>(), It.IsAny<CancellationToken>()))
-            .ReturnsAsync((Employee e, CancellationToken _) => e);
-
-        // Act
-        var result = await _handler.HandleAsync(command, CancellationToken.None);
-
-        // Assert
-        Assert.NotNull(result.Employee);
-        Assert.Equal("John Doe", result.Employee.Name);
-        _employeeRepoMock.Verify(x => x.CreateAsync(
-            It.Is<Employee>(e => e.Name == "John Doe"),
-            It.IsAny<CancellationToken>()), Times.Once);
-    }
-
-    [Fact]
-    public async Task HandleAsync_UpdateEmployee_UpdatesExisting()
-    {
-        // Arrange
-        var existingEmployee = new Employee { Id = "emp-1", Name = "Old Name" };
-        var command = new SaveEmployeeCommand
-        {
-            Id = "emp-1",
-            Name = "New Name"
-        };
-
-        _employeeRepoMock
-            .Setup(x => x.GetByIdAsync("emp-1", It.IsAny<CancellationToken>()))
-            .ReturnsAsync(existingEmployee);
-
-        _employeeRepoMock
-            .Setup(x => x.UpdateAsync(It.IsAny<Employee>(), It.IsAny<CancellationToken>()))
-            .ReturnsAsync((Employee e, CancellationToken _) => e);
-
-        // Act
-        var result = await _handler.HandleAsync(command, CancellationToken.None);
-
-        // Assert
-        Assert.Equal("New Name", result.Employee.Name);
-        _employeeRepoMock.Verify(x => x.UpdateAsync(
-            It.Is<Employee>(e => e.Name == "New Name"),
-            It.IsAny<CancellationToken>()), Times.Once);
-    }
-
-    [Fact]
-    public async Task HandleAsync_InvalidCommand_ReturnsValidationError()
-    {
-        // Arrange
-        var command = new SaveEmployeeCommand
-        {
-            Name = ""  // Invalid: empty name
-        };
-
-        // Act & Assert
-        var result = command.Validate();
-        Assert.False(result.IsValid);
-        Assert.Contains(result.Errors, e => e.Contains("Name"));
-    }
-}
-```
-
-## Pattern 2: Query Handler Unit Test
-
-```csharp
-public class GetEmployeeListQueryTests
-{
-    private readonly Mock<IPlatformQueryableRootRepository<Employee, string>> _repoMock;
-    private readonly GetEmployeeListQueryHandler _handler;
-
-    [Fact]
-    public async Task HandleAsync_WithFilters_ReturnsFilteredResults()
-    {
-        // Arrange
-        var employees = new List<Employee>
-        {
-            new() { Id = "1", Name = "Active", Status = EmployeeStatus.Active },
-            new() { Id = "2", Name = "Inactive", Status = EmployeeStatus.Inactive }
-        };
-
-        _repoMock.Setup(x => x.CountAsync(It.IsAny<Expression<Func<Employee, bool>>>(), It.IsAny<CancellationToken>()))
-            .ReturnsAsync(1);
-
-        _repoMock.Setup(x => x.GetAllAsync(It.IsAny<Func<IPlatformUnitOfWork, IQueryable<Employee>, IQueryable<Employee>>>(), It.IsAny<CancellationToken>(), It.IsAny<Expression<Func<Employee, object>>[]>()))
-            .ReturnsAsync(employees.Where(e => e.Status == EmployeeStatus.Active).ToList());
-
-        var query = new GetEmployeeListQuery
-        {
-            Statuses = [EmployeeStatus.Active],
-            SkipCount = 0,
-            MaxResultCount = 10
-        };
-
-        // Act
-        var result = await _handler.HandleAsync(query, CancellationToken.None);
-
-        // Assert
-        Assert.Single(result.Items);
-        Assert.Equal("Active", result.Items[0].Name);
-    }
-}
-```
-
-## Pattern 3: Entity Validation Test
-
-```csharp
-public class EmployeeEntityTests
-{
-    [Fact]
-    public void UniqueExpr_ReturnsCorrectExpression()
-    {
-        // Arrange
-        var employees = new List<Employee>
-        {
-            new() { CompanyId = "c1", UserId = "u1" },
-            new() { CompanyId = "c1", UserId = "u2" },
-            new() { CompanyId = "c2", UserId = "u1" }
-        }.AsQueryable();
-
-        // Act
-        var expr = Employee.UniqueExpr("c1", "u1");
-        var result = employees.Where(expr).ToList();
-
-        // Assert
-        Assert.Single(result);
-        Assert.Equal("u1", result[0].UserId);
-    }
-
-    [Fact]
-    public async Task ValidateAsync_DuplicateCode_ReturnsError()
-    {
-        // Arrange
-        var repoMock = new Mock<IPlatformQueryableRootRepository<Employee, string>>();
-        repoMock.Setup(x => x.AnyAsync(It.IsAny<Expression<Func<Employee, bool>>>(), It.IsAny<CancellationToken>()))
-            .ReturnsAsync(true);  // Duplicate exists
-
-        var employee = new Employee { Id = "new", Code = "EMP001", CompanyId = "c1" };
-
-        // Act
-        var result = await employee.ValidateAsync(repoMock.Object, CancellationToken.None);
-
-        // Assert
-        Assert.False(result.IsValid);
-        Assert.Contains(result.Errors, e => e.Contains("already exists"));
-    }
-
-    [Fact]
-    public void ComputedProperty_IsActive_CalculatesCorrectly()
-    {
-        // Arrange
-        var activeEmployee = new Employee { Status = EmployeeStatus.Active, IsDeleted = false };
-        var inactiveEmployee = new Employee { Status = EmployeeStatus.Inactive, IsDeleted = false };
-        var deletedEmployee = new Employee { Status = EmployeeStatus.Active, IsDeleted = true };
-
-        // Assert
-        Assert.True(activeEmployee.IsActive);
-        Assert.False(inactiveEmployee.IsActive);
-        Assert.False(deletedEmployee.IsActive);
-    }
-}
-```
-
-## Pattern 4: Angular Component Test
-
-```typescript
-describe('FeatureListComponent', () => {
-    let component: FeatureListComponent;
-    let fixture: ComponentFixture<FeatureListComponent>;
-    let store: FeatureListStore;
-    let apiMock: jasmine.SpyObj<FeatureApiService>;
-
-    beforeEach(async () => {
-        apiMock = jasmine.createSpyObj('FeatureApiService', ['getList', 'delete']);
-
-        await TestBed.configureTestingModule({
-            imports: [FeatureListComponent],
-            providers: [FeatureListStore, { provide: FeatureApiService, useValue: apiMock }]
-        }).compileComponents();
-
-        fixture = TestBed.createComponent(FeatureListComponent);
-        component = fixture.componentInstance;
-        store = TestBed.inject(FeatureListStore);
-    });
-
-    it('should create', () => {
-        expect(component).toBeTruthy();
-    });
-
-    it('should load items on init', () => {
-        // Arrange
-        const items = [{ id: '1', name: 'Test' }];
-        apiMock.getList.and.returnValue(of({ items, totalCount: 1 }));
-
-        // Act
-        fixture.detectChanges();
-
-        // Assert
-        expect(apiMock.getList).toHaveBeenCalled();
-        expect(component.vm()?.items).toEqual(items);
-    });
-
-    it('should delete item', fakeAsync(() => {
-        // Arrange
-        store.updateState({ items: [{ id: '1', name: 'Test' }] });
-        apiMock.delete.and.returnValue(of(void 0));
-
-        // Act
-        component.onDelete({ id: '1', name: 'Test' });
-        tick();
-
-        // Assert
-        expect(apiMock.delete).toHaveBeenCalledWith('1');
-        expect(component.vm()?.items.length).toBe(0);
-    }));
-
-    it('should show loading state', () => {
-        // Arrange
-        apiMock.getList.and.returnValue(new Subject()); // Never completes
-
-        // Act
-        fixture.detectChanges();
-
-        // Assert
-        expect(store.isLoading$('loadItems')()).toBe(true);
-    });
-});
-```
-
-## Pattern 5: Angular Store Test
-
-```typescript
-describe('FeatureListStore', () => {
-    let store: FeatureListStore;
-    let apiMock: jasmine.SpyObj<FeatureApiService>;
-
-    beforeEach(() => {
-        apiMock = jasmine.createSpyObj('FeatureApiService', ['getList', 'save', 'delete']);
-
-        TestBed.configureTestingModule({
-            providers: [FeatureListStore, { provide: FeatureApiService, useValue: apiMock }]
-        });
-
-        store = TestBed.inject(FeatureListStore);
-    });
-
-    it('should initialize with default state', () => {
-        expect(store.currentVm().items).toEqual([]);
-        expect(store.currentVm().pagination.pageIndex).toBe(0);
-    });
-
-    it('should load items', fakeAsync(() => {
-        // Arrange
-        const items = [{ id: '1', name: 'Test' }];
-        apiMock.getList.and.returnValue(of({ items, totalCount: 1 }));
-
-        // Act
-        store.loadItems();
-        tick();
-
-        // Assert
-        expect(store.currentVm().items).toEqual(items);
-        expect(store.currentVm().pagination.totalCount).toBe(1);
-    }));
-
-    it('should update state immutably', () => {
-        // Arrange
-        const initialItems = store.currentVm().items;
-
-        // Act
-        store.updateState({ items: [{ id: '1', name: 'New' }] });
-
-        // Assert
-        expect(store.currentVm().items).not.toBe(initialItems);
-    });
-
-    it('should handle API error', fakeAsync(() => {
-        // Arrange
-        apiMock.getList.and.returnValue(throwError(() => new Error('API Error')));
-
-        // Act
-        store.loadItems();
-        tick();
-
-        // Assert
-        expect(store.getErrorMsg$('loadItems')()).toContain('Error');
-    }));
-});
-```
-
-## Test Naming Convention
-
-```
-[MethodName]_[Scenario]_[ExpectedBehavior]
-
-Examples:
-- HandleAsync_ValidCommand_ReturnsSuccess
-- HandleAsync_InvalidId_ThrowsNotFound
-- UniqueExpr_MatchingValues_ReturnsTrue
-- LoadItems_ApiError_SetsErrorState
-```
-
-## Anti-Patterns to AVOID
-
-:x: **Testing implementation, not behavior**
-
-```csharp
-// WRONG - testing internal method calls
-Assert.True(handler.WasValidateCalled);
-
-// CORRECT - testing observable behavior
-Assert.Equal("Expected", result.Value);
-```
-
-:x: **Not mocking dependencies**
-
-```csharp
-// WRONG - using real repository
-var handler = new Handler(new RealRepository());
-
-// CORRECT - using mock
-var repoMock = new Mock<IRepository>();
-var handler = new Handler(repoMock.Object);
-```
-
-:x: **Missing edge cases**
-
-```csharp
-// WRONG - only happy path
-[Fact] public void Save_ValidData_Succeeds() { }
-
-// CORRECT - include edge cases
-[Fact] public void Save_EmptyName_ReturnsError() { }
-[Fact] public void Save_DuplicateCode_ReturnsError() { }
-[Fact] public void Save_NullInput_ThrowsException() { }
-```
-
-## Verification Checklist
-
-- [ ] Unit tests cover happy path
-- [ ] Edge cases and error conditions tested
-- [ ] Dependencies properly mocked
-- [ ] Test naming follows convention
-- [ ] Assertions are specific and meaningful
-- [ ] No test interdependencies
-- [ ] Tests are deterministic (no random, no time-dependent)

package/templates/skills/test-generation/SKILL.md

@@ -1,203 +0,0 @@
----
-name: test-generation
-description: Use for QA-focused BDD test specifications (Given/When/Then) with traceability matrices, coverage analysis, and comprehensive test case documentation. Best for QA teams, acceptance testing, and feature documentation with test cases. NOT for writing unit test code (use tasks-test-generation instead).
-allowed-tools: Read, Write, Edit, Bash, Grep, Glob, Task, TodoWrite
----
-
-# Test Case Generation
-
-You are to operate as an expert full-stack QA engineer and SDET to analyze features and generate comprehensive test cases (Given...When...Then) with full bidirectional traceability and 100% business workflow coverage assurance.
-
-**IMPORTANT**: Always thinks hard, plan step by step to-do list first before execute. Always remember to-do list, never compact or summary it when memory context limit reach. Always preserve and carry your to-do list through every operation.
-
----
-
-## Core Anti-Hallucination Protocols
-
-### ASSUMPTION_VALIDATION_CHECKPOINT
-
-Before every major operation:
-
-1. "What assumptions am I making about [X]?"
-2. "Have I verified this with actual code evidence?"
-3. "Could I be wrong about [specific pattern/relationship]?"
-
-### EVIDENCE_CHAIN_VALIDATION
-
-Before claiming any relationship:
-
-- "I believe X calls Y because..." → show actual code
-- "This follows pattern Z because..." → cite specific examples
-- "Service A owns B because..." → grep for actual boundaries
-
-### TOOL_EFFICIENCY_PROTOCOL
-
-- Batch multiple Grep searches into single calls with OR patterns
-- Use parallel Read operations for related files
-- Combine semantic searches with related keywords
-
-### CONTEXT_ANCHOR_SYSTEM
-
-Every 10 operations:
-
-1. Re-read the original task description from the `## Metadata` section
-2. Verify the current operation aligns with original goals
-3. Update the `Current Focus` in `## Progress` section
-
----
-
-## PHASE 1: EXTERNAL MEMORY-DRIVEN TEST ANALYSIS
-
-Build a structured knowledge model in `ai_task_analysis_notes/[feature-name].ai_task_analysis_notes.md`.
-
-### PHASE 1A: INITIALIZATION AND DISCOVERY
-
-1. **Initialize** the analysis file with standard headings
-2. **Discovery searches** for all feature-related files
-3. Prioritize: **Domain Entities, Commands, Queries, Event Handlers, Controllers, Background Jobs, Consumers, front-end Components**
-
-### PHASE 1B: SYSTEMATIC FILE ANALYSIS FOR TESTING
-
-**IMPORTANT: MUST DO WITH TODO LIST**
-
-For each file, document in `## Knowledge Graph`:
-
-- Standard fields plus testing-specific:
-- `coverageTargets`: Specific coverage goals
-- `edgeCases`: Edge cases and boundary conditions
-- `businessScenarios`: Business scenarios supported
-- `detailedFunctionalRequirements`: Business logic and functional requirements
-- `detailedTestCases`: Business logic test cases (Given...When...Then)
-
----
-
-## PHASE 2: OVERALL ANALYSIS
-
-Write comprehensive summary showing:
-
-- Complete end-to-end workflows discovered
-- Key architectural patterns and relationships
-- All business logic workflows
-- Integration points and dependencies
-
----
-
-## PHASE 3: APPROVAL GATE
-
-**CRITICAL**: Present test plan with coverage analysis for explicit approval. **DO NOT** proceed without it.
-
----
-
-## PHASE 4: EXECUTION
-
-Write comprehensive feature requirements document, test cases, and coverage analysis into `ai_spec_docs/[feature-name].ai_spec_doc.md`.
-
-Generate test cases in **4 priority groups**: Critical, High, Medium, Low.
-
-### MANDATORY DOCUMENT STRUCTURE
-
-```markdown
-# [Feature Name] - Comprehensive QA Test Cases
-
-## Table of Contents
-
-1. [Feature Overview](#1-feature-overview)
-2. [Entity Relationship Diagram](#2-entity-relationship-diagram)
-3. [Detailed Test Cases](#3-detailed-test-cases)
-4. [Traceability Matrix](#4-traceability-matrix)
-5. [Coverage Analysis](#5-coverage-analysis)
-
-## 1. Feature Overview
-
-**Epic:** [Epic Name]
-
-- **Summary (The Why):** As a [user type], I want to [action], so that [benefit].
-
-**User Story 1:** [Story Title]
-
-- **ID:** US-XXX-001
-- **Story:** As a [role], I want to [action], so that [benefit].
-- **Acceptance Criteria:**
-    - AC 1: GIVEN [context] WHEN [action] THEN [result]
-    - AC 2: ...
-
-**Business Requirements:**
-
-- [Each business requirement]
-
-**Roles/Permission Authorization:**
-
-- [Each role and permission]
-
-### 1-A. Cross Services Business Logic Overview
-
-[Cross Service Consumer Producer Business Logic]
-
-## 2. Entity Relationship Diagram
-
-### Core Entities and Relationships
-
-[Entity descriptions with properties and relationships]
-
-### Mermaid Diagram
-
-[Entity relationship mermaid diagram]
-
-## 3. Detailed Test Cases
-
-### [Priority Level (Critical/High/Medium/Low)]:
-
-#### TC-001: [Test Case Name]
-
-**Feature Module:** [Module]
-**Business Requirement:** BR-XXX
-**Priority:** Critical/High/Medium/Low
-
-**Given** [initial context]
-**And** [additional context]
-**When** [action performed]
-**Then** the system should:
-
-- [Expected outcome 1]
-- [Expected outcome 2]
-
-**Component Interaction Flow:**
-```
-
-Frontend → Controller → Command/Query → Repository → Event → Consumer
-
-```
-
-**Test Data:**
-- [Required test data]
-
-**Expected Outcomes:**
-- [Detailed outcomes]
-
-**Edge Cases to Validate:**
-- [Edge case 1]
-- [Edge case 2]
-
-## 4. Traceability Matrix
-[Bidirectional mapping between tests and business components]
-
-## 5. Coverage Analysis
-[Multi-dimensional coverage validation with percentages]
-```
-
----
-
-## PHASE 5: Review Table of Contents
-
-Update `## Table of Contents` with detailed sub-section links.
-
----
-
-## Test Case Guidelines
-
-- **Evidence-based testing**: Base test cases on actual code behavior
-- **Complete coverage**: Cover all conditional logic paths
-- **Component tracing**: Include workflow between components
-- **Priority classification**: Critical (P0), High (P1), Medium (P2), Low (P3)
-- **BDD format**: Use Given/When/Then consistently
-- **Traceability**: Link test cases to requirements bidirectionally