[qzcx]

As someone who's also done a lot of DV and DV tools, I love to see it. This gap was something I took away from attending DVCon last year and seeing all the papers from folks reinventing in the same verif tools.

Feeling inspired after DVCon, I was sick of how annoying our test infrastructure was to interact with so I built a vscode extension as a front end to the existing mature infrastructure. Handles running tests, regressions, opening logs of all kinds, launching vendor tools, jumping to definitions, hover over documentation on all our custom config files, even breakpoints that export to verdi. I've got about 30 people using it now which is pretty neat.

My main learnings are 1) boy it would be tough to make this generic enough to my existing infra without making it lose all the benefits 2) Switching away from my editor is a huge context loss, having tools directly inside my editor keeps everything moving faster.The thought of adding yet another important web page to my browser isn't pleasant. I specifically added features to my extension so I could avoid going to our internal regression results webpage.

[pkkim]

Hey, that sounds really cool, and also sounds like it was a lot of work! As for point 2, we are planning at some point on making everything accessible via API and releasing a CLI, so a VSCode extension should definitely be possible.

[qzcx]

Honestly, way less work than you'd think. A couple of months of a few hours per week tinkering. Copilot taught me the typescript and the vscode api is very powerful and well documented. Being able to leverage other extensions already doing the heavy work is a huge benefit (such as DVT for identifying symbol definitions).