Blog post Leaderboard MCP Deploy agents
Back to all reviewers

Write comprehensive test cases

vuejs/core
Based on 6 comments
TypeScript

Tests should thoroughly cover all code paths and edge cases. Each test case should: 1. Test distinct scenarios in separate test cases 2. Cover all logical branches and code paths

Testing TypeScript

Reviewer Prompt

Tests should thoroughly cover all code paths and edge cases. Each test case should:

  1. Test distinct scenarios in separate test cases
  2. Cover all logical branches and code paths
  3. Use clear, specific test names that describe the scenario being tested
  4. Include both positive and negative test cases

Example:

// ❌ Incomplete test coverage
test('isRef check', () => {
  expect(isRef(computed(() => 1))).toBe(true)
})

// ✅ Comprehensive test coverage
describe('isRef', () => {
  test('returns true for computed values', () => {
    expect(isRef(computed(() => 1))).toBe(true)
  })

  test('returns false for primitive values', () => {
    expect(isRef(0)).toBe(false)
    expect(isRef(1)).toBe(false)  // Test truthy primitive
    expect(isRef('')).toBe(false) // Test falsy primitive
  })
  
  test('returns true for ref values', () => {
    expect(isRef(ref(1))).toBe(true)
    expect(isRef(ref(null))).toBe(true)
  })
})
6
Comments Analyzed
TypeScript
Primary Language
Testing
Category

Source Discussions