Battle-Testing Nx Console with E2E Tests

• vscode-test

  2 227 7.3 TypeScript

  Testing utility for VS Code extensions

  

Integration Tests combine multiple parts of your software and test them together. They are a good option for testing some behaviour of extensions. If you read the docs, they suggest using the @vscode/test-electron package and mocha. This will allow you to run tests inside an actual VSCode instance, so you avoid mocking. However, you are still constrained. The API gives limited information on many areas. For example even this very simple test is not easily realizable with the VSCode API:

• SurveyJS

  surveyjs.io featured

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• wdio-vscode-service

  2 28 7.6 TypeScript

  A service to test VSCode extensions from end to end using WebdriverIO

  

WDIO has one big advantage: The wdio-vscode-service . It’s a plugin that integrates with WDIO and handles all setup-related work for you. You won’t have to think about downloading, installing and running a VSCode instance or the matching Chromedriver. On top of that, it bootstraps page objects for many functionalities and lets you access the VSCode API via remote function execution.

• nx-console

  4 1,294 9.2 TypeScript

  Nx Console is the user interface for Nx & Lerna.

  

• WebdriverIO

  37 8,857 9.9 TypeScript

  Next-gen browser and mobile automation test framework for Node.js

  

WebdriverIO (abbreviated as WDIO) is an E2E testing framework for Node.js. It allows you to automate all kinds of web and mobile applications using the Webdriver or Chrome DevTools protocols.

• mocha

  143 22,495 7.7 JavaScript

  ☕️ simple, flexible, fun javascript test framework for node.js & the browser

  

Integration Tests combine multiple parts of your software and test them together. They are a good option for testing some behaviour of extensions. If you read the docs, they suggest using the @vscode/test-electron package and mocha. This will allow you to run tests inside an actual VSCode instance, so you avoid mocking. However, you are still constrained. The API gives limited information on many areas. For example even this very simple test is not easily realizable with the VSCode API:

• Visual Studio Code

  2,879 159,624 10.0 TypeScript

  Visual Studio Code

  

Suggest a related project