Bump test runner to v2?

Next month, I’m toying with the idea of bumping the test runner to v2. Vader (our testing framework) provides g:vader_report which stores the contents of Vader’s test results buffer, and g:vader_errrors which stores the list of failed tests. So we could identify which tests failed and retrieve it from g:vader_report. To grab the test code, Vader’s parser exposes a parse function that retrieves dictionaries representing each test without running them. So between these three things, we could report out a v2 JSON without a lot of fuss.

2 Likes

Small update - I’m pretty close to a working prototype for review. :)

1 Like

PR merged.

Two minor hiccups in the v2 output.

( 1/11) [EXECUTE] (X) 1 should be equal to 0 should be dedented. It’s not showing up correctly here but there’s four spaces before the (.

The other one is a readability issue surfaced in this output above. The actual value is on the left and the expected value on the right. But if you look at the tested code below, the expected value is actually on the left side so the apparent flipped sides might be confusing.

let g:list = [6]
let g:value = 6
let g:expected = 0
AssertEqual g:expected, Find(g:list, g:value)