
But the bottom bar status and test report show as skipped. And the test explorer recognizes integration tests as tests. If you open the test class, the green check or red x are correct.

This causes the test to run and a green (or red) status to appear in the bottom left line with how it went. Click “run test” over the class name or method name. Or at least it did until I disabled the Maven integration. it also provides a visual way to run effective pom. This provides a visual way to run Maven clean/install/etc. The left explorer view has a “Maven Projects” section.Useful when you don’t know the keyboard shortcuts or location of anything! I used it a lot for organize imports! Shift Command/Windows P – Lets you type in the name of what you want to do.I learned these when I was playing last time. And more importantly, I have a better understanding of the VS Code environment. I didn’t complete the development task I wanted to.

I tried to *only* use VS Code for the five hours of coding I did today.

The project I was working on uses Maven, Selenium and JUnit 5. This means not just dealing with my first impressions, but actually trying to get something done. I tried to code for real in Visual Studio Code for the first time.
