IntelliJ IDEA creates a Maven project with the pom.xml file that includes compiler and target versions of Java, the dedicated Maven tool window, and all the necessary dependencies to start your work. In Advanced Settings, specify the following Maven coordinates that are added to the pom.xml file:įor more information about Maven coordinates, refer to Maven naming conventions. The selected Add sample code option will create a file with a basic code sample. Specify project's SDK (JDK) or use the default one. Select Maven in the list of Build system. Click if you want to add other languages available via plugins. Select a language that you want to use in your project. You will be able to do it later at any time. Select the Create Git repository to place the new project under version control. Name the new project and change its location if necessary. Otherwise, select File | New | Project from the main menu. If no project is currently open in IntelliJ IDEA, click New Project on the Welcome screen. If you want to use a custom Maven version that is not bundled with IntelliJ IDEA, you need to install it locally. For more information, refer to the WSL section. You can also create a Maven project and store it in the WSL environment or open it from the WSL file system. You can easily create a new Maven project, open and sync an existing one, add a Maven support to any existing IntelliJ IDEA project, configure and manage a multi-module project. The final build.IntelliJ IDEA supports a fully-functional integration with Maven that helps you automate your building process. We need to tell Gradle to use the JUnit Platform when running the tests, by adding useJUnitPlatform() to the test section. There’s one last step we need to do for Gradle in order to correctly use JUnit 5. Once the Gradle dependency changes have been loaded, we can see the junit-jupiter dependencies in the External Libraries section of our project window. You must load the Gradle changes if you want IntelliJ IDEA to apply them.Ĭlick on the icon, or use ⇧⌘I, or Ctrl+Shift+O on Windows and Linux, to load the changes.

You should see an icon in the top right of the Gradle build file when it has been changed. NOTE: if you try to search for a dependency and you don’t get the results you expect (either no results, or the versions seem out of date), make sure IntelliJ IDEA has an updated Maven Repository via the settings.

Use the right arrow to open up the version options for this dependency, and choose version 5.6.2 (the most recent production version at the time of writing). Use Tab to jump into the dependencies list and use the down arrow until :junit-jupiter is selected. Typing 'junit' in the artifact search box should give a list of possible dependencies. Given a Gradle build file, use ⌘N (macOS) or Alt+Insert (Windows/Linux) to add a new dependency. This tutorial uses Gradle, for information on how to add JUnit 5 via Maven take a look at our blog and video on Migrating to JUnit 5 from JUnit 4. This provides an easy way for people to skim the content quickly if they prefer reading to watching, and to give the reader/watcher code samples and links to additional information. This blog post covers the same material as the video. All code in this tutorial can be found in this GitHub repository. In this tutorial we’re going to look at features of JUnit 5 that can make it easier for us to write effective and readable automated tests.

Intellij idea