Fixed the exception view which was not displaying the results properly

[email2vimalraj]

• Fixed the exception view which was not displaying the results properly
• Removed the duplicated exception for the parent node if the exception was raised by the child node
• Minor enhancement in the style and the nav template
• Updated the version number in the report template

[email2vimalraj]

The report now looks like as follows:

The code used to test is as follows:

// start reporters
        ExtentHtmlReporter htmlReporter = new ExtentHtmlReporter("extent.html");

        // create ExtentReports and attach reporter(s)
        ExtentReports extent = new ExtentReports();
        extent.attachReporter(htmlReporter);

        ExtentTest feature1 = extent.createTest("Feature 1");
        ExtentTest scenario1 = feature1.createNode(Scenario.class, "Scenario 1");
        scenario1.createNode(Given.class, "Step 1").pass("Passed");
        scenario1.createNode(When.class, "Step 2").fail(new IllegalStateException("Second test failed"));

        ExtentTest feature2 = extent.createTest("Feature 2");
        ExtentTest scenario2 = feature2.createNode(Scenario.class, "Scenario 2");
        scenario2.createNode(Given.class, "Step 1").pass("Passed");
        scenario2.createNode(When.class, "Step 2").pass("Passed");

        ExtentTest scenario3 = feature2.createNode(Scenario.class, "Scenario 3");
        scenario3.createNode(Given.class, "Step 1").pass("Passed");
        scenario3.createNode(When.class, "Step 2").fail(new IllegalStateException("Fail message"));

        extent.flush();

[anshooarora]

The 2 methods:

copyNodeAttributeInfoToAttributeContext
copyNodeExceptionInfoToExceptionContext

were not sharing the code because one points to the test's attributes and the other for exception. Attributes of the test are author, category etc. Exception isn't a test's attribute because it is not something that you can assign, but it occurs due to an event, so its more of a runtime binding.

We can change the method name so its more clear to the user that here the test is computing all attributes and runtime events..