Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extent Report's HTML File is not generated for LONG running tests #32

Open
kmantrala opened this issue Dec 24, 2020 · 0 comments
Open

Comments

@kmantrala
Copy link

We use ADO Pipelines to run our selenium tests written in C#. Our code has references to ExtentReport binaries and for the most part when tests (less than 50) are run on a stand alone machine or using ADO Pipeline running on ADO Agents, we do see that the HTML report is generated at the end.

However off late, our test suites size increased and we roughly run 700 tests per suite/client. These tests takes somewhere between 16 hours to 26 hours to fully run. Due to this, the HTML report after all tests have run are NOT BEING GENERATED. The ADO Pipeline Task we created is to 'Publish Build Artifacts'. This task has the following details:

  • Path to Publish: \Results

  • Artifact Name: MyResultsName

  • Artifact Publish Location: Azure Pipelines

  • Control Options:
    Enabled - checked
    Continue on Error - checked

    The XML file configured to generate Extent Reports has the following:

<?xml version="1.0" encoding="utf-8" standalone="no"?>
<test-run start-time="2020-12-14 10:28:29Z">
  <command-line><![CDATA[packages\NUnit.ConsoleRunner.3.8.0\tools\nunit3-console.exe  --out=<**Code Location**>\UiResult.txt "--result=<**Code Location**>\UiResult.xml" <**Code Location**>\Testing.dll --where "cat=**TestCategories separated by ||** "]]></command-line>
</test-run>

Can someone let me know what is the reason for the Extent Report's HTML file not getting generated?

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant