A mature testing framework for Go designed to help you write expressive specs
97
Pending
Does it follow best practices?
Impact
97%
1.12xAverage score across 10 eval scenarios
Pending
The risk profile of this skill
{
"context": "This evaluation assesses the engineer's ability to use Ginkgo v2's progress reporting and test metadata capabilities. It focuses specifically on proper usage of CurrentSpecReport() for retrieving test information and By() for documenting test progress.",
"type": "weighted_checklist",
"checklist": [
{
"name": "CurrentSpecReport() Usage",
"description": "Uses CurrentSpecReport() function to retrieve the current test's report object within test execution",
"max_score": 25
},
{
"name": "Test Description Access",
"description": "Accesses the FullText() method or LeafNodeText field from the spec report to get the test description",
"max_score": 15
},
{
"name": "File Location Access",
"description": "Accesses the LeafNodeLocation or FileName() method from the spec report to get the test file path",
"max_score": 15
},
{
"name": "Line Number Access",
"description": "Accesses the LineNumber field or LineNumber() method from the spec report to get the test line number",
"max_score": 10
},
{
"name": "By() Function Usage",
"description": "Uses By() function to add descriptive progress markers during test execution",
"max_score": 25
},
{
"name": "Multiple Progress Steps",
"description": "Demonstrates By() usage with multiple distinct progress steps within test cases",
"max_score": 10
}
]
}docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10