{
  "context": "This criteria evaluates how well the engineer uses Jest's promise testing capabilities (resolves and rejects) to test asynchronous operations. The focus is on proper usage of promise-specific matchers rather than general testing practices.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Uses .resolves matcher",
      "description": "Tests use expect(promise).resolves with appropriate matchers (e.g., .toBe(), .toEqual(), .toMatchObject()) to verify fulfilled promise values instead of using .then() or async/await with standard expect().",
      "max_score": 30
    },
    {
      "name": "Uses .rejects matcher",
      "description": "Tests use expect(promise).rejects with appropriate matchers (e.g., .toThrow(), .toMatch()) to verify rejected promise reasons instead of using .catch() or try/catch with standard expect().",
      "max_score": 30
    },
    {
      "name": "Verifies resolved data",
      "description": "Tests for successful promise resolutions verify the correct data structure is returned, checking for expected properties (id, name) and values using matchers chained after .resolves.",
      "max_score": 15
    },
    {
      "name": "Verifies rejection errors",
      "description": "Tests for promise rejections verify the correct error messages are thrown (e.g., 'Invalid user ID', 'Timeout exceeded') using matchers chained after .rejects.",
      "max_score": 15
    },
    {
      "name": "Tests multiple scenarios",
      "description": "Implements all required test cases including single user fetch (success and failure), multiple users fetch (success and failure), and timeout scenarios (success and failure).",
      "max_score": 10
    }
  ]
}