Avoid console.log in Typescript tests

typescript
Avoid using `console.log` statements in test files.
Bad:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    console.log(result) // Debugging statement left in the code

Install this rule for wispbit

Add this rule to wispbit and it will run when you open a pull request

Install this rule for Coderabbit

Copy the configuration below and add it to your repository as .coderabbit.yml in your project root.

reviews:
  path_instructions:
    - path: "*.spec.ts,*.test.ts"
      instructions: |
                
        Avoid using `console.log` statements in test files.
        
        Bad:
        
        ```typescript
        describe("Example test", () => {
          it("should test something", () => {
            const result = someFunction()
            console.log(result) // Debugging statement left in the code
            expect(result).toBe(expectedValue)
          })
        })
        ```
        
        Good:
        
        ```typescript
        describe("Example test", () => {
          it("should test something", () => {
            const result = someFunction()
            expect(result).toBe(expectedValue)
          })
        })
        ```

Install this rule for Greptile

Greptile rules can be added through the web interface. Please see this documentation for details on how to add custom rules and context.

Avoid using `console.log` statements in test files.
Bad:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    console.log(result) // Debugging statement left in the code
    expect(result).toBe(expectedValue)
  })
})
```
Good:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    expect(result).toBe(expectedValue)
  })
})
```

File Path Patterns:

*.spec.ts
*.test.ts

Install this rule for GitHub Copilot

Copilot instructions can be added through the interface. See the documentation for details on how to create coding guidelines.

Avoid using `console.log` statements in test files.
Bad:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    console.log(result) // Debugging statement left in the code
    expect(result).toBe(expectedValue)
  })
})
```
Good:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    expect(result).toBe(expectedValue)
  })
})
```

File Path Patterns:

*.spec.ts
*.test.ts

Install this rule for Graphite Diamond

Diamond custom rules can be added through the interface. See the documentation for details on how to create custom rules.

Avoid using `console.log` statements in test files.
Bad:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    console.log(result) // Debugging statement left in the code
    expect(result).toBe(expectedValue)
  })
})
```
Good:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    expect(result).toBe(expectedValue)
  })
})
```

File Path Patterns:

*.spec.ts
*.test.ts

Use with Cline

Copy the rule below and ask Cline to review your code using this rule

Avoid using `console.log` statements in test files.
Bad:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    console.log(result) // Debugging statement left in the code
    expect(result).toBe(expectedValue)
  })
})
```
Good:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    expect(result).toBe(expectedValue)
  })
})
```

Use with OpenAI Codex

Copy the rule below and ask OpenAI Codex to review your code using this rule

Avoid using `console.log` statements in test files.
Bad:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    console.log(result) // Debugging statement left in the code
    expect(result).toBe(expectedValue)
  })
})
```
Good:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    expect(result).toBe(expectedValue)
  })
})
```

Use with Cursor

Copy the rule below and ask Cursor to review your code using this rule

Avoid using `console.log` statements in test files.
Bad:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    console.log(result) // Debugging statement left in the code
    expect(result).toBe(expectedValue)
  })
})
```
Good:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    expect(result).toBe(expectedValue)
  })
})
```

Use with Claude Code

Copy the rule below and ask Claude Code to review your code using this rule

Avoid using `console.log` statements in test files.
Bad:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    console.log(result) // Debugging statement left in the code
    expect(result).toBe(expectedValue)
  })
})
```
Good:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    expect(result).toBe(expectedValue)
  })
})
```

Install this rule for Windsurf

To set up rules for Windsurf Reviews, please see this documentation 

Avoid using `console.log` statements in test files.
Bad:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    console.log(result) // Debugging statement left in the code
    expect(result).toBe(expectedValue)
  })
})
```
Good:
```typescript
describe("Example test", () => {
  it("should test something", () => {
    const result = someFunction()
    expect(result).toBe(expectedValue)
  })
})
```