Parameterised tests for Jest that enable running the same test multiple times with different data sets using arrays or tagged template literals
85
Pending
Does it follow best practices?
Impact
85%
1.10xAverage score across 10 eval scenarios
Pending
The risk profile of this skill
{
"context": "This criteria evaluates how well the engineer uses Jest's timeout configuration features to handle tests with different execution durations. The focus is on proper use of timeout parameters and functions to manage async operations that take varying amounts of time.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Default timeout usage",
"description": "Uses Jest's default timeout behavior for the quick operation test without explicit timeout configuration, demonstrating understanding of when timeouts aren't needed",
"max_score": 15
},
{
"name": "Per-test timeout parameter",
"description": "Uses the third parameter to test() or it() to set timeout values (e.g., test('name', async () => {...}, 5000)) for at least one slow operation test",
"max_score": 25
},
{
"name": "Extended timeout configuration",
"description": "Configures timeout to at least 4000ms for the slow operation test (3-second operation) and at least 13000ms for the very slow operation test (12-second operation)",
"max_score": 25
},
{
"name": "Timeout failure test",
"description": "Creates a test that intentionally sets a timeout shorter than the operation duration to demonstrate timeout failure behavior, showing understanding of timeout constraints",
"max_score": 20
},
{
"name": "Async test handling",
"description": "Uses async/await pattern or returns promises in tests to properly handle asynchronous operations with Jest",
"max_score": 15
}
]
}docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10