-
Notifications
You must be signed in to change notification settings - Fork 318
ExtentReports - replace exisiting = false throwing nullpointerexception when trying to append to exisiting report #589
Comments
Can you share the stack-trace? Upgrade to 2.41.1 and try again? |
FAILED CONFIGURATION: @BeforeClass seleInit |
Updated to new version of extentreports still not working? |
Are there any tests in the existing report? |
one test from the last report technically its overwriting that test |
FAILED CONFIGURATION: @BeforeClass seleInit |
But its failing on initialisation |
If I tell it to replaceExisting it works/ if I tell it not to it shows that stack trace - filepath is correct |
I think this might be to do with copying testclasses as an old testclass in a different package still works |
So it works if when you change packages of your existing test class? That is strange. |
I copied the testclass over to to the new (dodgy) package and it works maybe I hadn't cleaned the cache who knows |
I will close this issue as it seems to be resolved. Feel free to reopen this or a new issue if you encounter it again. |
Hi Ansh, I am getting nullpointer exception on below line. please let me know how to resolve. |
issue :How to solve NULLPOINTEREXCEPTION while using grouping concepts in POM with Extends Reporting ? Solutions:
|
I'm using ExtentReports with selenium webdriver and have recently discovered a problem, yesterday(15th Aug 16) with ExtentReports replaceExisting variable throwing a java.lang.nullpointerexception when the report already exists
When running a testSuite or class in TestNG
Where ExtentManager.get Instance
extent = new ExtentReports(filePath,false, DisplayOrder.OLDEST_FIRST, NetworkMode.ONLINE);
Deleting the report or changing replaceExisiting to true solves the issue but I lose previous occurrences of the test =>
extent = new ExtentReports(filePath,true, DisplayOrder.OLDEST_FIRST, NetworkMode.ONLINE);
The former extent code I would like to keep as it was originally working right up until yesterday
So was wondering how could this have occurred.
I am using ExtentReports 2.40
The text was updated successfully, but these errors were encountered: