Microcks in VS Code — early build is testable, and I'd like adopters to break it

[Caesarsage]

Running a Microcks contract test locally means a server, Keycloak and a spec import, so drift usually gets caught in CI instead. This extension brings microcks test --dry-run, and the rest of Microcks, into VS Code. It's at 0.1.0, installable as a VSIX, and not on the Marketplace yet.

What's in it

• Sidebar with Services and Tests trees, down to the step-level failure reason.
• Dry-run an API file with no server, or Start Local Server / Sign In to Remote Server (browser SSO).
• Import the current API file, and an Operation Inspector to call mocks and compare them with your real service.

It's CLI-first: everything goes through microcks-cli JSON output, and the extension never stores credentials.

Try it

Needs VS Code 1.85+, Docker or Podman, and microcks-cli 1.0.3+.

git clone https://github.com/Caesarsage/microcks-vscode && cd microcks-vscode
npm install && npm run package:vsix
code --install-extension microcks-vscode-0.1.0.vsix

What I'd like to know

1. Which path would you adopt: dry-run, local server, or remote sign-in?
2. Does the CLI shell-out work in your setup (SSO, proxy, Podman)?
3. What's missing before you'd keep it installed?

Rough edges are the most useful thing you can send me. Reply here, or open an issue if it's a
concrete bug.

full demo on youtube · microcks-vscode · microcks-cli · architecture

Preview:

social-cut-github.mp4

[Caesarsage]

cc @Vaishnav88sk @Harsh4902 @lbroudoux @yada

[Vaishnav88sk]

Hi everyone! 👋

To add a bit more context to this discussion, we recently wrapped up an awesome LFX Mentorship project where we built a Microcks VS Code Extension. Huge shoutout to Destiny for a fantastic job on the implementation and testing! 🚀

While the code is ready, Maintainers and the team want to make sure we are building something that truly benefits our users. Before we officially set up the repository under the Microcks organization and publish the extension to the VS Code Marketplace, we want to gauge community traction and the need for this tool.

Why a VS Code Extension?
Our goal is to streamline the inner development loop. Instead of constantly context-switching between your IDE, terminal, and the Microcks UI, this extension brings Microcks directly to where you write your code. By publishing this (and distributing via the OpenVSX Registry), the extension becomes available not just for standard VS Code, but also for the wider ecosystem of VS Code-compatible IDEs, such as VSCodium, Eclipse Theia, Gitpod, and AI-powered editors like Antigravity, Cursor, and Windsurf.

For example: Imagine you are working on an OpenAPI or AsyncAPI specification. With this extension, you could potentially interact with your Microcks server directly from your editor, quickly discovering existing mocks, pushing new artifacts for testing, or validating your local API contracts without ever leaving VS Code or the IDE.

We want to hear from you! Does this fit into your daily workflow? Will it make your API development lifecycle smoother?

Tagging some of our active community members and adopters to get your thoughts: @Basuchi @celidrissi @gozen59 @dataGriff @vleon1a @ludovic-pourrat. We'd love to hear your insights!

[Vaishnav88sk]

📊 Community Poll: Do we need this VS Code Extension?

To help us gauge interest, please react to this comment and drop a quick reply below:

👍 React with +1 if you think this extension is needed and would make your development workflow easier.
Please reply and tell us: What specific feature would you use the most?

👎 React with -1 if you don't feel this would be useful to you right now.
Please reply and tell us: Why? Do you prefer the existing CLI/UI, or does your workflow rely on different tools?

Every piece of feedback helps us prioritize our efforts. Thank you! 🙏

[Caesarsage]

I have recorded a full demo video and preview

Full demo

Preview:

social-cut-github.mp4

[yada]

Thank you, @Caesarsage : this is very cool.
We can also add it here: https://www.youtube.com/c/Microcks and promote it on social media: ok for you?

[Caesarsage]

yes, that will be great. I can send the full demo video across

[yashasvimisra2798]

Hi @Caesarsage, great work on this! 🚀 Dry run is the path I'd adopt first, since validating a spec with no server or Keycloak setup is what would get me to try it. Getting the managed installer working with a released CLI would make a big difference for first-time users. Happy to test once that lands!

[Caesarsage]

Hi @Caesarsage, great work on this! 🚀 Dry run is the path I'd adopt first, since validating a spec with no server or Keycloak setup is what would get me to try it. Getting the managed installer working with a released CLI would make a big difference for first-time users. Happy to test once that lands!

Thanks @yashasvimisra2798! Dry-run first matches what we're hearing.

Good news: it has landed. microcks-cli 1.0.3 is now the latest stable release, and Microcks: Install or Update CLI installs it and passes the capability gate, so you no longer need to build from source. I've updated the post above.

When you try it, I'd love to know:

• Does the CLI shell-out work in your setup (Docker or Podman, any proxy)?
• After a few dry-runs, what's missing before you'd keep it installed?

[aniket866]

@Caesarsage
Great work, Destiny! Excellent implementation and testing of the Microcks VS Code Extension.
This will make the developer workflow much smoother.,

[Caesarsage]

Thank you @aniket866