Skip to content

Latest commit

 

History

History
77 lines (57 loc) · 4.23 KB

CONTRIBUTING.md

File metadata and controls

77 lines (57 loc) · 4.23 KB
Raw

Contributing to Test Runner for Java

Thank you for your interest in contributing to Test Runner for Java!

There are many ways in which you can contribute, beyond writing code. Please read the following document to check how you can get involved.

Questions and Feedback

Have questions or feedback? Feel free to let us know! You can share your thoughts in our Gitter channel: Gitter

Reporting Issues

You can report issues whenever:

  • Identify a reproducible problem within the extension
  • Have a feature request

Looking for an Existing Issue

Before creating a new issue, please do a search to see if the issue or feature request has already been filed.

If you find your issue already exists, make relevant comments and add your reaction:

  • 👍 - upvote
  • 👎 - downvote

Writing Good Bug Reports and Feature Requests

In order to let us know better about the issue, please make sure the following items are included with each issue:

  • The version of VS Code
  • Your operating system
  • Reproducible steps
  • What you expected to see, versus what you actually saw
  • Images, animations, or a link to a video showing the issue occurring
  • A code snippet that demonstrates the issue or a link to a code repository the developers can easily pull down to recreate the issue locally
  • Errors from the Dev Tools Console (open from the menu: Help > Toggle Developer Tools)

Contributing Fixes

If you are interested in writing code to fix issues, please check the following content to see how to set up the developing environment.

Overview

The extension has three major modules, which are listed as follow:

  • The extension client written in TypeScript - UI logic mostly
  • The Java Test Plugin written in Java - Inspect the Java project
  • The Test Runner written in Java - An executable jar to running the test cases

Setup

  1. Fork and clone the repository: git clone [email protected]:Microsoft/vscode-java-test.git
  2. cd vscode-java-test
  3. Install the node dependencies: npm install
  4. Build the Java modules: npm run build-plugin
  5. Open the directory vscode-java-test in VS Code
  6. Install the Eclipse PDE Support extension in your VS Code
  7. Open a Java file and wait until 👍 shows in the right-bottom of the status bar

    Note: Sometimes, if you find the code navigation is not working in the Java code, please reload your VS Code.

Debugging

  1. Hit F5 (or run Launch Extension in the debug viewlet) to launch the extension in debug mode

    This will open a new VS Code window as a debug session. Open a Java project folder and let the extension be activated, then you can debug it.

  2. If you want to debug the Java Test Plugin, run Debug Test Runner Java Plugin (Attach) in the debug viewlet.

Note: If the Java code is changed by you, please run npm run build-plugin before you start debugging, the output jars will be generated in the folder server/.

Debugging the Test Runner

  • The Test Runner is a normal Maven project, you can open it with whatever the development tools you prefer, for example, VS Code
  • The Test Runner is an executable jar, the main class is com.microsoft.java.test.runner.Launcher

Build Your Own Private Build

If you want to build your own private build, run npx @vscode/vsce@latest package after npm run build-plugin.

Check Lint Errors:

Run npm run lint to check lint errors.

Running the test suite

You can run tests using npm run test or by using the Launch Tests Run and Debug configurations in VS Code.

VS Code run and debug configurations

There are two test suite folders for this project. In VS Code you'll see the following run targets:

  • Launch Tests (maven junit): This will run the tests in the ./test/suite folder.
  • Launch Tests (unmanaged-folder): This will run the tests in the ./test/unmanaged-folder-suite folder.