How to use Interface IFileParser class of org.testng.xml package

You shouldn't see a NPE as a test failure. You should actually assert it is not null and provide an error message,

assertNotNull(someVal, "Some descriptive message saying why value should not be null");

I just tried to hit it and looks like it's working fine:

curl -v https://plugins.gradle.org/api/gradle/2.14.1/plugin/use/com.github.johnrengelman.shadow/1.2.3
*   Trying 104.25.173.23...
* Connected to plugins.gradle.org (104.25.173.23) port 443 (#0)
* found 173 certificates in /etc/ssl/certs/ca-certificates.crt
* found 704 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_ECDSA_AES_128_GCM_SHA256
*    server certificate verification OK
*    server certificate status verification SKIPPED
*    common name: ssl277771.cloudflaressl.com (matched)
*    server certificate expiration date OK
*    server certificate activation date OK
*    certificate public key: EC
*    certificate version: #3
*    subject: OU=Domain Control Validated,OU=PositiveSSL Multi-Domain,CN=ssl277771.cloudflaressl.com
*    start date: Sat, 06 Aug 2016 00:00:00 GMT
*    expire date: Sun, 05 Feb 2017 23:59:59 GMT
*    issuer: C=GB,ST=Greater Manchester,L=Salford,O=COMODO CA Limited,CN=COMODO ECC Domain Validation Secure Server CA 2
*    compression: NULL
* ALPN, server accepted to use http/1.1
> GET /api/gradle/2.14.1/plugin/use/com.github.johnrengelman.shadow/1.2.3 HTTP/1.1
> Host: plugins.gradle.org
> User-Agent: curl/7.47.0
> Accept: */*
> 
< HTTP/1.1 200 OK
< Date: Wed, 24 Aug 2016 09:24:42 GMT
< Content-Type: application/json
< Transfer-Encoding: chunked
< Connection: keep-alive
< Set-Cookie: __cfduid=d0c64c916428b3abd24c29d0578251d2d1472030681; expires=Thu, 24-Aug-17 09:24:41 GMT; path=/; domain=.gradle.org; HttpOnly
< Via: 1.1 vegur
< Server: cloudflare-nginx
< CF-RAY: 2d75c0b211512378-FRA
< 
{
  "id" : "com.github.johnrengelman.shadow",
  "version" : "1.2.3",
  "implementation" : {
    "gav" : "com.github.jengelman.gradle.plugins:shadow:1.2.3",
    "repo" : "https://plugins.gradle.org/m2"
  },
  "implementationType" : "M2_JAR",
  "legacy" : true
* Connection #0 to host plugins.gradle.org left intact

Try that and see what happens.

--- edit

Just added it to a sample project and the file gets downloaded fine. I also used jcenter() repository for dependencies.

Download https://jcenter.bintray.com/com/github/jengelman/gradle/plugins/shadow/1.2.3/shadow-1.2.3.jar

Add that to your build.gradle file and try

buildscript {
    repositories {
        jcenter()
    }
}

You shouldn't see a NPE as a test failure. You should actually assert it is not null and provide an error message,

assertNotNull(someVal, "Some descriptive message saying why value should not be null");

From Javadoc:

Some virtual machines may, under some circumstances, omit one or more stack frames from the stack trace. In the extreme case, a virtual machine that has no stack trace information concerning this throwable is permitted to return a zero-length array from this method.

So, the only guaranteed way to do this is to use aspects, or collect stack trace with some other custom way. But you can combine this approach with fallback to some way of getting current method's name (for case when your logTitle method will be inlined). It can be found here, for example. Again, no guarantee, but better chance.

The answer is to create a shutdown hook via Runtime's addShutdownHook method, like this:

static volatile boolean cleanedUp = false;
static final Object lock = new Object();

@BeforeClass
public static void setup() {
    Runtime.getRuntime().addShutdownHook(new Thread(new Runnable() {
        public void run() {
            MyTestClass.tearDown();
        }
    }
}

@AfterClass
public static void tearDown() {
    synchronized (lock) {
        if (cleanedUp) return;
        // do clean up
        cleanedUp = true; 
    }         
}

Using the synchronization ensures the clean up is only executed once.

I really don't get why IDEA must break up one test run's console outs to so many places in the tree, seems kind of silly.

The intent is so you can see output relevant to a specific test. This way, when running dozens, or hundreds, of tests, you can focus on the relevant output and not a lot of "noise" that is irrelevant to the the particular test you are focusing on.

However I don't see a post anywhere explaining how to actually log all of this to one log file.

This is typically done via your logging framework, not the IDE. (But there is a way to do this in IDEA w/o a logging framework, which I discuss below.) As an aside, Logback is ideal for this since it automatically looks for a test specific configuration file. Of course, with other frameworks, you can set a test specific configuration file.

If you create a run/debug configuration for running your test, you can add the log file's output to a tab in the run output tool window. In your run/debug configuration, click on the Logs tab and add the log that your logging framework writes to. You can also set it up so that only new/fresh output is shown in the tab preventing you from seeing logging from previous runs.

You can also select the "Save Console Output to File" option.

Finally, you can combine the above two settings, so that console output is logged to a file, and the output is shown in a second tab.

If you want either of the settings to to be the default, you can set it in the default "unit test" configuration. Expand the "Default" section in the Run/Debug configuration window (Run > Edit Configurations). When set there, any new run/debug unit test configurations (even temporary ones created on the fly via Ctrl+Shift+F10) will have those settings. Note that defaults only apply to the current project. If you want to make the setting a global default for all future projects, From the Welcome Screen (i.e. close all projects) go to "Configure" > "Project Defaults" > "Run Configurations" and make the setting there.

Actually I think that the bad feeling in your gut against has more to do with Annotations like this mixing configuration with code.

Personally I feel the same way as you do, I would prefer to leave configuration (such as transaction definitions, path elements, URLs that a controller should be mapped to, etc.) outside of the code base itself and in external Spring XML context files.

I think though that the correct approach here comes down to opinion and which method you prefer - I would predict that half the community would agree with the annotations approach and the other half would agree with the external configuration approach.

As you are using Selenium 3.14.0 as per the FirefoxDriver Class the valid constructors are:

• FirefoxDriver()
• FirefoxDriver(FirefoxOptions options)
• FirefoxDriver(GeckoDriverService service)
• FirefoxDriver(GeckoDriverService service, FirefoxOptions options)
• FirefoxDriver(XpiDriverService service)
• FirefoxDriver(XpiDriverService service, FirefoxOptions options)

So, as per your code attempts the following is not a valid option to invoke FirefoxDriver()

WebDriver driver = new FirefoxDriver(profile);

Solution

To invoke invoke FirefoxDriver() with the default profile you need to use the setProfile(profile) method to set the FirefoxProfile through an instance of FirefoxOptions() and you can use the following code block:

• Code Block:

  import org.openqa.selenium.WebDriver;
  import org.openqa.selenium.firefox.FirefoxDriver;
  import org.openqa.selenium.firefox.FirefoxOptions;
  import org.openqa.selenium.firefox.FirefoxProfile;
  import org.openqa.selenium.firefox.ProfilesIni;
  import org.testng.annotations.Test;
  
  public class A_FirefoxProfile {
  
        @Test
        public void seleniumFirefox() {
          System.setProperty("webdriver.gecko.driver", "C:/Utility/BrowserDrivers/geckodriver.exe");
          ProfilesIni profileIni = new ProfilesIni();
          FirefoxProfile profile = profileIni.getProfile("default");
          FirefoxOptions options = new FirefoxOptions();
          options.setProfile(profile);
          WebDriver driver = new FirefoxDriver(options);
          driver.get("http://www.google.com");
          System.out.println(driver.getTitle());
        }
  
  }
  

• Console Output:

  [RemoteTestNG] detected TestNG version 6.14.2
  1537775040906   geckodriver INFO    geckodriver 0.20.1
  1537775040923   geckodriver INFO    Listening on 127.0.0.1:28133
  Sep 24, 2018 1:14:30 PM org.openqa.selenium.remote.ProtocolHandshake createSession
  INFO: Detected dialect: W3C
  Google
  PASSED: seleniumFirefox
  
  ===============================================
      Default test
      Tests run: 1, Failures: 0, Skips: 0
  ===============================================
  
  
  ===============================================
  Default suite
  Total tests run: 1, Failures: 0, Skips: 0
  ===============================================
  

Your errors come from this part:

<properties>
    <sl4j.version>1.7.7</sl4j.version>
    <suiteFile>${suiteFile}</suiteFile>
    <environment>${environment}</environment>
    <port>${port}</port>
</properties>

When you use ${port} Maven looks for the value in <port>X</port> which here X=${port} and so on... So that's why you get a recursive issue here