docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
{
"context": "This criteria evaluates how well the engineer understands and utilizes metro-memory-fs's reset() method for managing filesystem state isolation between tests. The focus is on proper usage of the reset functionality to ensure clean filesystem state.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses reset() method",
"description": "Implementation calls the reset() method on the metro-memory-fs instance to clear filesystem state",
"max_score": 40
},
{
"name": "Filesystem instance creation",
"description": "Creates a metro-memory-fs instance using the MemoryFs constructor or appropriate creation pattern",
"max_score": 20
},
{
"name": "Reset timing placement",
"description": "Places reset() calls at appropriate times (in cleanup/teardown methods) to ensure isolation between tests",
"max_score": 25
},
{
"name": "Filesystem exposure",
"description": "Provides access to the filesystem instance for tests through the manager's interface (e.g., getFs method)",
"max_score": 15
}
]
}