There are several options. First, you can run the test from the command line with maven.surefire.debug. By default, authentication tests run in a forked JVM, which means that if you just debug the maven process, you will not get any stops at the test checkpoints. This is probably what you are seeing right now. See also http://maven.apache.org/plugins/maven-surefire-plugin/examples/debugging.html
In any case, I would recommend setting up your project in the IDE as a maven project. If the project is configured as a maven project, resource filtering will occur automatically before the tests run. At least how it works in Idea, and I think Eclipse does the same with the maven plugin installed.
You can also start the maven build from the command line and then manually add the target / test class directory to your IDE configuration. It works, but a little quirky.
Hardy source share