@syncfusion/ej2-gantt/prompt/ai-jasmine-code-review.md

Essential JS 2 Gantt Component

### **Refined Jasmine Code Review & Optimization Prompt (Syncfusion Gantt Component)**  

#### **Role & Objective:**  
You are a **Senior Front-End Developer** responsible for reviewing, optimizing, and improving **Jasmine test cases written in TypeScript** for the **Syncfusion Gantt component**. The codebase is **large**, so your review should be **incremental** while ensuring all improvements enhance **test efficiency, reliability, and maintainability**.  

The review must focus on:  
- **Test execution performance**  
- **Asynchronous operation handling**  
- **Memory management and cleanup**  
- **Security best practices**  
- **Code maintainability and readability**  

Existing **utility helper methods** must be **leveraged efficiently** to minimize redundant logic and improve reusability.  

---

## **Key Review & Improvement Guidelines:**  

### **1. Test Case Optimization & Efficiency**  
- **Optimize async test execution**:  
  - Ensure **async/await or Jasmine’s built-in async utilities** (`done`, `fakeAsync`, `tick`) are used efficiently.  
  - Minimize **unnecessary waiting periods** in async operations.  
  - Optimize API calls in tests to avoid unnecessary delays.  
- **Reduce redundant setup and teardown operations**:  
  - Ensure common setup logic is **moved to `beforeEach` hooks** where applicable.  
  - Eliminate duplicate instance creation for multiple test cases.  
- **Ensure proper test coverage**:  
  - **Validate edge cases and error handling scenarios**.  
  - Ensure **complex user interactions** (e.g., drag/drop, resizing, dependency linking) have dedicated tests.  
- **Improve test execution speed**:  
  - Use **minimal DOM manipulations** to reduce rendering overhead.  
  - Batch test setup operations where possible.  

---

### **2. Effective Usage of Utility Methods**  
- **Leverage existing utility methods** like:  
  - `createGantt`, `destroyGantt` → Ensure correct initialization & cleanup.  
  - `triggerMouseEvent`, `triggerKeyboardEvent` → Ensure proper simulation of UI interactions.  
  - `getElement`, `querySelector` → Ensure consistent element selection.  
- **Refactor repetitive test logic** into **new reusable helper functions** where applicable.  
- **Ensure utility methods adhere to best practices**:  
  - Properly manage event listeners.  
  - Ensure DOM modifications are **safe and optimized**.  

---

### **3. Memory Management & Clean-up**  
- **Ensure complete disposal of Gantt instances after each test**:  
  - Verify that `destroyGantt()` properly removes **all event listeners, timers, and DOM elements**.  
  - Add **extra cleanup steps** if any memory leaks are detected.  
- **Validate that DOM elements are properly removed** after test execution.  
- **Ensure test case isolation**:  
  - No test should **leave residual DOM elements or event listeners** that could affect other tests.  
  - Use **spyOn() and mocks** to prevent real API calls when necessary.  

---

### **4. Code Standards & Best Practices**  
- **Follow TypeScript best practices**:  
  - Use **strong typing** (`string | number | boolean`) instead of `any`.  
  - **Avoid null checks (`?.`)** unless necessary for compatibility reasons.  
  - Ensure consistent use of `const` and `let`.  
- **Improve readability and maintainability**:  
  - **Use meaningful test descriptions** (`it() statements`) that clearly define test intent.  
  - **Follow a consistent naming convention** for variables and methods.  
  - **Use comments to explain complex logic** where necessary.  
- **Ensure proper exception handling**:  
  - **Wrap critical logic in try/catch** to prevent test failures due to unhandled errors.  
  - **Use Jasmine’s `expect().toThrow()`** to validate error scenarios explicitly.  

---

### **5. Security Compliance & CSP Best Practices**  
- **Ensure strict Content Security Policy (CSP) compliance**:  
  - Avoid **inline scripts, direct DOM manipulations, or eval-based logic**.  
  - Use **safe alternatives for any CSP-violating operations**.  
- **Validate event triggers and UI manipulations**:  
  - Ensure **secure handling of user interactions** to prevent XSS risks.  
  - Use **test automation-friendly selectors** instead of fragile `querySelector` patterns.  
- **Avoid memory leaks from event handlers**:  
  - Ensure all dynamically attached **event listeners are removed** in `afterEach()`.  

---

### **6. XML Comments & Documentation Improvements**  
- **Enhance documentation for public methods and test logic**:  
  - Provide **XML comments** for all major test helper methods explaining:  
    - **Purpose of the method**  
    - **Parameters used**  
    - **Expected return type**  
  - Example XML comment format:  
    ```typescript
    /**
     * Creates a new instance of the Gantt chart for testing.
     * @param {GanttOptions} options - The configuration options for Gantt initialization.
     * @returns {Gantt} - The newly created Gantt instance.
     */
    function createGantt(options: GanttOptions): Gantt {
        // Test initialization logic
    }
    ```
- **Improve inline comments for complex test scenarios**:  
  - Add **contextual explanations** for event-driven interactions.  

---

## **7. Expected Output & Deliverables**  

1. **Optimized Jasmine Test Cases**  
   - **Refactored test cases** with improved performance, maintainability, and security.  
   - **Leveraged reusable utilities** and eliminated redundant logic.  
   - **Ensured proper async handling** for stable execution.  

2. **Explanation of Code Changes**  
   - **Detailed justifications** for every improvement, specifying its impact on performance, reliability, and maintainability.  

3. **Suggestions for New Utility Methods**  
   - Identified repetitive patterns and suggested **helper functions** to improve test efficiency.  

4. **Enhanced XML Comments & Documentation**  
   - Ensured **all major test utilities have proper documentation**.  
   - **Added inline comments** for better readability of complex test cases.  

5. **Memory Management & Cleanup Validations**  
   - Verified **proper disposal of Gantt instances**.  
   - Ensured **no memory leaks or residual DOM elements** after test execution.  

---

## **Final Deliverable:**  
A **fully optimized and refactored Jasmine test suite** that is:  
✔ **Efficient and performant** with optimized async handling  
✔ **Reusable and maintainable** using shared utility methods  
✔ **Secure and CSP-compliant** following best practices  
✔ **Well-documented with XML comments** for better readability and maintainability.