-
Notifications
You must be signed in to change notification settings - Fork 315
Dashboard End time-stamp is not set correctly, takes the end date of the first test. [TestNG IReporter] #926
Comments
@anshooarora If you'll allow me I can go fix it myself if you don't have time. |
That's correct, thanks for finding this issue. Please feel free to send in a pull request. I will merge. |
Dashboard End time-stamp is not set correctly (takes the end date of the first test). anshooarora#926
@anshooarora , my apologies if i'm being pushy on this... but can you please let me know when you'll be able to release this hotfix on Maven? it's really critical and it has a breaking effect on anyone using the listener's reports. |
@MohabMohie On |
Summary
Dashboard End time-stamp is not set correctly (takes the end date of the first test).
As you can see from the three screenshots below, the time-stamp is correct for the start date but not the end date
dashboard:



first test:
second test:
Expected Behavior
It should take the smallest start time of all the tests, and the largest end time of all the tests
Current Behavior
It takes the smallest start time of all the tests. and the smallest end time of all the tests
I believe that this should be "less than" not "greater than"

Sample
I'm using the TestNG IReporter with setReportUsesManualConfiguration(true);
There was also a problem with the test time stamp, as it should be the end time stamp for that test, yet it was something else... I fixed it by manually overriding the end time stamp for each step.
Environment Details
The text was updated successfully, but these errors were encountered: