What’s Easier than Clicking “Run Test”? Not Clicking It.

Dan Miller
May 22, 2018 · 2 min read

Have you ever been banging your head against the wall, trying to get that one test to pass? It can be frustrating to make a small tweak in your editor and then have to switch to a terminal to run the test, over and over again. VS Code makes this easier by offering CodeLenses to run tests right in the editor.

But it’s not live. It’s not responsive. We believe your tools should know what you’re working on. They should give you relevant feedback before you ask for them.

Windmill is running some small experiments on how to make your existing devtools more alive. We’re starting with Go testing in VSCode.

Autotest for Go

Introducing Go Autotest for VS Code! Go Autotest automates the running of your Go tests so you can spend less time turning the crank and more time building things. It does this through two features: autorun and test pinning.

Autorun is simple: every time you open a Go file that contains tests the extension will run those tests in the background and provide the result as a CodeLens atop the test function.

Test pinning allows you to focus on just one test and see the new result immediately on save of any file. This is useful when you’re just trying to get that one pesky test to pass.

Become a fan

At Windmill Engineering we want to make developer tools (build, source, and test) cloud-based, simple, and easy. We don’t entirely know what that means yet! We’re still building it. Go Autotest is the first of several experiments we will run aimed at improving developers workflows. If this mission excites you, or you want to try future experiments, consider becoming a fan!

Tilt Blog

Kubernetes for Prod, Tilt for Dev

Tilt Blog

Kubernetes for Prod, Tilt for Dev https://tilt.dev/

Dan Miller

Written by

Software engineer @windmill_eng. Trumpet player. Explorer of the world and subcultures.

Tilt Blog

Kubernetes for Prod, Tilt for Dev https://tilt.dev/