Showing posts with label VS Code. Show all posts
Showing posts with label VS Code. Show all posts

Monday, 12 October 2026

Mendix Testing Inside VS Code

 MendixWright: Mendix Testing Inside VS Code

MendixWright is a VS Code extension that lets Mendix teams check every environment and run Playwright regression tests without leaving the editor. Version 1.2.3 is out now, and this post walks through what it does, with annotated demo screenshots.

The problem

On most Mendix projects I work on, a simple question like "Is Acceptance up, and do the regression tests still pass?" can mean four tools. You open the Mendix Portal for environment status, a browser to sign in, a terminal for Playwright, and a spreadsheet to tie results back to requirements.

Each switch costs a few minutes and some context. Across a team running daily regression, that adds up fast. MendixWright brings it all into one VS Code panel.

What MendixWright is

MendixWright is the Mendix Testing Plugin for VS Code, published by KaizenFix. Search "Mendix" in the Extensions Marketplace, install it, and a Mendix Testing icon appears in the activity bar.


On first start, it checks for the Chromium build that its bundled Playwright uses, and for @playwright/test each Playwright project in your workspace. If anything is missing, it offers to install it for you.

Local Mendix servers

Open the panel and any Mendix app running on your machine is already listed. In the demo it picks up an app on port 8080 running Mendix 11.11.0, with no configuration.


For each local app, you get the URL, Mendix version, admin API port, response time, Java process ID, and bind address. That's everything you'd otherwise dig out of Studio Pro or Task Manager before pointing a test run at it.

Every Mendix Cloud environment in one tree

Below the local servers sits Mendix Cloud Environments: every licensed app you can see, each with its Production and Acceptance environments. A green dot means the environment is up, and each row shows its URL, response time and Mendix version.

Expand an environment, and you get two checks. Health is the platform status. Home page health checks that the app's home page is authenticating and working, so it catches an app that's "running" but serving errors.

App details holds the metadata you usually need from the Portal: App ID, technical contact, region, subdomain, licence, and whether the project is checked out on this machine. It also clearly tells you when your API key doesn't have permission to see an app's environments.

From health check to test run in one click

Click the link icon on any environment, and you get four actions: open it in a new browser window, copy the URL, run Playwright tests against this URL, or authenticate and save the session.

The last two are where the time savings are. Run Playwright Tests points your existing suite at that environment, so the same tests run against local, Acceptance or Production without editing config. Authenticate and Save Session signs you in to the Mendix app once and stores the session, so later runs skip the login step.

Beyond testing: requirements and reporting

Two more features close the loop between what the app should do and what the tests prove.

  • Documentation. MendixWright reads your app's model and generates a business requirements document (BRD): overview, user stories and acceptance criteria. Requirement IDs stay the same when you regenerate, so tests can reference them and stay valid as the app changes.
  • MendixFix Insights. Playwright runs, and BRDs are published to a shared dashboard, broken down by requirement, test runner and persona. Product owners and testers see coverage and results without opening VS Code.

Why use it

  • One place. Environment health, sign-in and regression runs all live in the editor where you already write tests.
  • Zero discovery work. Local apps and every licensed cloud environment appear without configuration.
  • Catch real outages. Home-page checks spot an app that's up but broken, not just a container that's running.
  • Same suite, any environment. Point your Playwright tests at local, Acceptance or Production from a menu.
  • Traceable quality. Stable requirement IDs and a shared Insights dashboard give stakeholders evidence, not just a green tick.

Thursday, 9 July 2026

Simple Explanation of LLM's, Coding Agents

      GitHub Copilot, Claude Code, and Cursor are not AI models!  They are Coding Agents/Assistants.

They are the developer experience layer that sits in your IDE and seamlessly accesses various Large Language Models (LLMs) such as Claud Opus/Fable/Sonnet/Haiku or GPT5.

The actual intelligence comes from the underlying Large Language Model (LLM) such as GPT-5, Claude Opus/Sonnet, Gemini, 

Naming breakdown:

  VS Code / Visual Studio /Claude Code (IDE)    

      ─────▼────

GitHub Copilot / Cursor Extension / Claude Code Extension        (Coding Agent)      

      ─────▼────

 GPT-5 / Claude Opus / Gemini (LLMs)

Local vs Premium LLMS: 

Cursor can reference online LLMs like Claude Opus and use Ollama to run Qwen3-Coder (my pref. for now), DeepSeek-Coder, Llama 3.x, Mistral.  Ollama lets me point to a local LLM and use it for free (saving on tokens; there are other advantages as well).

My Setup for local LLM usage:

VS Code                                   +
Cursor Extension                     +
Ollama                                     +
Local LLM (Qwen3-Coder)    = 🚀 AI-Powered Software Development

Saturday, 25 April 2026

VSCode with Claude Code or GitHup Copilot

Overview: I have seen people really struggling with understanding that Claude is not GitHub Copilot (GHCP).  And GitHub Copilot is not an LLM. 

Terminology: 

Claude by Anthropic is made up of various parts, and it helps to be more specific.  Calusde is amazing at providing great Large Language Models (LLMs).  There are Claude Opus (for programming the lastest us 4.7), Claud Sonnet, and Claude Haiku.  GPT-5.4 is OpenAI's current flagship LLM.  Gemini 3.1 Pro is known for UI-focused coding. I found Gemini 3.0 good, but I don't use it that often.   

Claude also offers other services beyond supplying LLMs like Claude Code and Claude CLI.  These are the key ones for me:

  • Claude in Chrome — a browsing agent
  • Cowork — a desktop tool for non-developers to automate file and task management, rival to Microsoft 365 Copilot.
  • GitHub Copilot for VS Code is the equivalent of Claude Code for VS Code

    Developing in VS Code:

    In the screen below, I am using both Claude Code and GitHub Copilot in the VS Code IDE.

    Here I have some C# code that creates and deploys an Azure Function. I can use either option until I run out of credits with my monthly (GHCP) or hourly (Claude) subscription allowance.  When I go over my GHCP allowance, I have it set up to use my Azure Credits.

    Friday, 31 October 2025

    Playwright Agents in VS Code

    I started looking at the latest version of Playwright late last night. The Agents add-in for VS Code is amazing.  I can't stop improving my code, my tests, and my automation.  It is highly addictive.

    Playwright 1.56.1 includes the new Playwright CLI, which has the test agents as shown in VS Code above:

    Node: v22.21.0
    npx: 11.6.2
    Playwright test package: ^1.56.1

    Wednesday, 30 July 2025

    AI for developers and Architects

    The cost of prototypes is unbelievably low using AI. 

    Rapidly creating a prototype, especially with new or less well-known technology, is where I derive significant benefits from AI.

    How to build application prototypes?

    1. Write /reverse prompt/Adjust instructions into md file
    2. Agentic AI (specialising in Doc Extraction) to extract and refine from md file
    3. Run using IDE-based copilot (VS Code with GitHub Copilot) (AmazonQ) (Cursor, Windsurf, Steamlit) 
    Thoughts: Developers are adjusting to using Ai to support software solutions.  The developer role will continue the trend of making technical implementation more accessible, allowing knowledgeable IT engineers or domain experts to build faster and better than citizen/amateur developers.  Ai assists in complex decisions!  

    What needs to improve?
    • Knowledge is key.  AI needs to have narrow expertise at the right time. i.e. only domain knowledge, not influenced by other data.  Quality of input data used to train.  Allows for dynamic reasoning.
    • Session/long-term contact agreement/understanding to improve the understanding between your IDE and me.  Remember how I prompt and provide feedback on how I digest information.  Context between the human developer and Ai is Paramount.
    • Control of IDE integration with coding copilots, clear return to the user developer to make better decisions.  Context is Paramount.
    • Governance & Data (Connectors, API's, code complex processes (MCP maybe), quality of data).

    Retrieval Augmentation Generate (RAG)


    AI needs to be able to connect to my existing Tool Landscape:
    I use Azure, C#, Playwright, and GitLab.  I want my IDE to work with these tools and many more.  MCP servers publish their functionality, and I can connect my Copilot/Agent to use multiple MCP servers.  This is what GHCP does for VS Code, allowing you to add MCP clients dynamically to use existing MCP Servers. 

    Model Context Protocol (MCP)

    MCP is a protocol (created by Anthropic) that allows an MCP client to connect to an MCP server, which in turn provides specialist knowledge. Authentication should use OAuth to secure access.

    My Applications/Agents use the MCP to ask the MCP Server, 'What can you do?' so they know how to use it.  The MCP server allows you to interact with a system.  It is often referred to as the "Arms and Legs" of AI.

    The MCP Server, when built, informs the client of its capabilities and then performs actions, such as updates, via an API.  

    Summary: Use MCP to enable the client to communicate with other resources/tools.

    NB: An Agent can utilise multiple MCP Servers.

    Agents-to-agent (A2A) 

    A2A allows agents to work together.  So two agents can leverage each other; the other agent solves the issue and returns the answer for the first agent to use.  Whereas MCP allows any agent to speak to a source.  Agents complete a task and give it back to the calling agent. 
     
    Summary: Use A2A to talk to specialised Agents, and the agent returns the calling agent's answers.


    Tuesday, 13 August 2024

    Pulumi to create App Insights on Azure with VS Code

    Overview: Provision Azure App Insights using Pulumi on VS Code using TypeScript, code generate by Pulumi's AI web code engine.  It is so lovely. 


    Series on Pulumi:

    Introduction and setup Pulumi on VS Code

    Pulumi to create App Insights on Azure with VS Code (This post)


    Sunday, 10 November 2019

    OpenAPI Tooling working with WebAPI and APIM Notes

    Editor.swagger.io is a great tool for building OAS files.  The Swagger editor is easy to use and has a preview for changes.

    VS Code is a great IDE for working with OpenAPI  specification 2.0 and 3.0 files (also know and Swagger specification).  These 3 extensions are a good idea for working with a OpenAPI specification file.


    Spotlight also has an editor which is nice.  Takes a little bit of getting use to, but make complex API design first easier.

    Sunday, 17 June 2018

    Azure Powershell from VS Code

    Overview:  I am moving over to using Visual Studio code for everything including PowerShell.  Historically, I would use PowerGUI as it was the best IDE for PS for many years but PS ISE is excellent and I don't see a material difference these days.  Basically, I use VS code for my ISE for JS, SPFx, C# unless the full versions of Visual Studio speed up my delivery rate, this allows me to remain in VS code without going to PowerGUI or 1 of the Windows PS consoles/IDE.

    Get the VS code debugger working: 

    Get the IDE (VS Code) ready
    On a new VS Code install, add the VS Extension "PowerShell", the VSIX has the description "Develop PowerShell scripts in Visual Studio Code!"



    Run and Verify PS is working and output returned is working

    Add the Azure Account Extension
    Sign into Azure
    A notification pops up to authenticate the machine/laptop with you Miscrofot credentials.  Run the popup and sign in to authenticate the local dev IDE.

     Open the Cloud Shell
    Verify you are signed in



    Sunday, 20 May 2018

    Visual Studio Code - IDE Tips

    VS Code - Short cuts
    Ctrl + S = Save the current page
    Alt+ Shift + A = Comment out multiple lines
    Ctrl + / = Comment out a single line of code, same cmd to toggle the comment off

    VS Code is perfect for comparing two files.  Select the two source file, right click > Select to Compare >