Tag
testing
The first round of tests ran jvq hundreds of times on a Go benchmark whose cost we set by hand. That showed how often it raises a false alarm and how often it catches a …
releases
A budget gate has a blind spot, and it’s built in. jvq judges each change against its base. A change that makes a benchmark 1% slower passes a 5% budget, and it …
releases
Time is a noisy thing to gate on. On our 2-core test machine the same benchmark spreads 7 to 9% from run to run, so jvq’s default budget is 5%, and a 2% slowdown …
releases
The first jvq release read one thing: the output of Go’s go test -bench. That covered Go projects and nothing else. Version 0.2 drops the limit. If your benchmark …
releases
Version 0.2 let jvq gate a benchmark in any language, by timing the whole command or reading a few lines of JSON. That still meant a little glue for projects that already …
testing
A gate that blocks merges has two ways to fail. It can cry wolf, flagging changes that did nothing, until people stop trusting it. Or it can sleep through a real …
explainers
A performance budget is a promise written into the pipeline: this change may make the code at most 5% slower, and if it’s worse, the build fails. Tests already …