How to use getPanelName method of org.testng.reporters.jq.BaseMultiSuitePanel class

In java there are a lot of frameworks. For example, you don't have to use JUnit, you could use TestNG with basically just as much tool support. There are several mocking frameworks as well.

In terms of coding standards, IDEs come with that built in, as well as there being several others available (I'm most familiar with the IDE ones, so I don't know names off hand).

You have Eclipse as an IDE if you want free, as well as NetBeans and for money there is IntelliJ IDEA among others. Then there are some IDEs from big vendors intended to support their specific application servers.

In terms of building "assemblies" (jars, wars and ears in the java world), there are some built in tools in IDEs for one-man projects, and there is Ant or Maven for a full fledged build tool.

There are many options in automated testing tools. If you mean continuous integration, there is CruiseControl that is free, and TeamCity which has no cost for low usage.

In terms of code generators, in general the Java world is kind of trying to move away from them in favor of annotations, but the name that comes to mind is xdoclet. In GUI building there are a bunch of code generators strictly for building the GUI of course.

That really barely scratches the surface. For example, application servers (JBoss, Oracle (they now own two with the Sun purchase) and IBM among others) are a big decision point in many Java projects (it depends what kind of project).

None of the categories discussed are intended to be exhaustive, just enough to give you a jumping point of what to look into. There are many more in each category.

The great thing about Java is that there are so many choices. The bad thing about Java is that there are so many choices ...

Please add the below line of code in the beginning of the test which will skip your test case

throw new SkipException("Skipping the test case");

That depends on how the link is highlighted. It's probably via a CSS class. Inspect the link (right click on it, your browser will have something that lets you inspect it), then compare its CSS to the CSS of the other link.

Assuming that the difference is a class called "active", then you would do something like

assertTrue(driver.findElement(By.id(ID_OF_LINK)).getAttribute("class").contains("active"));

That's pseudocode. Your language / webdriver may have a better way of checking for a CSS class on a WebElement.

(aside: everything you want your tests to interact with should have an ID; put an ID on it or ask the page author to do that)

AssertionError is not a sub-class of Exception (it's a sub-class of Error), so the first snippet, with the catch(Exception e) handler, doesn't catch it. Therefore the test result is FAILED.

The second snippet catches the exception, so as far a TestNG is concerned, no exceptions occurred in the test of testException() and the result is PASSED.

Please try to use proper array initialization and it should work. I tried the same code just with correct array initialization and it worked.

@DataProvider(name = "testData")
    public static Object[][] testDataProvider() {
        return new Object[][] {
            new String[]{ "abc", "abcd" },
            new String[]{ "abc", "abcd", "123" }
        };
    }

    @Test(dataProvider = "testData")
    public void test(String... str) {
        System.out.println("The Length is" + str.length);

    }

Also attaching the TestNG results...

Hope this helps

In order to make such Allure features like: attachments, steps and parameters work as expected you need to correctly specify -javaagent argument. Under Windows the following notation should work:

        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <version>2.16</version>
            <configuration>
                <argLine>
                    -javaagent:"${settings.localRepository}\org\aspectj\aspectjweaver\${aspectj.version}\aspectjweaver-${aspectj.version}.jar"
                </argLine>
                <properties>
                    <property>
                        <name>listener</name>
                        <value>ru.yandex.qatools.allure.testng.AllureTestListener</value>
                    </property>
                </properties>
            </configuration>
            <dependencies>
                <dependency>
                    <groupId>org.aspectj</groupId>
                    <artifactId>aspectjweaver</artifactId>
                    <version>${aspectj.version}</version>
                </dependency>
            </dependencies>
        </plugin>

Note quotes around path. Without correct -javaagent specification your @Attachment, @Step and @Parameter annotations will be ignored by Allure.

My question is, why is @AfterTest method not run after each @Test annotation?

As the Documentation says

@AfterTest: The annotated method will be run after all the test methods belonging to the classes inside the <test> tag have run.

and

@BeforeTest: The annotated method will be run before any test method belonging to the classes inside the <test> tag is run.

taskkill is a standard Windows utility. The fact that Selenium cannot find it means that the environment variable PATH does not include the directory that contains standard system utilities. It is C:\Windows\system32 for modern Windows versions.

Add this directory to the PATH variable (follow this instruction to modify the PATH variable: http://www.computerhope.com/issues/ch000549.htm) and restart the console or IDE where you run Selenium scripts to apply this environment change.

You did everything right except the method reference to create the Object[][]. You're constructing a 2D-array with 1D-array elements holding the strings.

Change

Object[]::new

to

Object[][]::new

Once this is done, then you don't need the cast to Object[][]; remove that as well.