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

[BUG] Azure html viewer do not work with 1.25 #16822

Closed
daniavander opened this issue Aug 25, 2022 · 4 comments
Closed

[BUG] Azure html viewer do not work with 1.25 #16822

daniavander opened this issue Aug 25, 2022 · 4 comments

Comments

@daniavander
Copy link

Context:

  • Playwright Version: 1.25.0
  • Operating System: windows latest
  • Node.js version: '14.x'
  • Browser: chromium
    hi

I run a build under azure cicd
but when i update to @playwright/test": "^1.25.1", the html viewer does not work well

but when i use "@playwright/test": "^1.23.3"
I get a pretty html report:
image

@yury-s
Copy link
Member

yury-s commented Aug 25, 2022

What error do you see? Please share an example which we could debug otherwise it's difficult to understand what the problem is.

@Wilhop
Copy link

Wilhop commented Aug 26, 2022

@daniavander Isn't that more an Azure DevOps problem with HTML-viewer extension? I'm using the same Playwright version but instead of using an extension I publish the html report, where the html is just fine. This way you're not depending on an extension.

In Azure Pipelines we publish the report that Playwright creates (the same that you are trying to view) as an Artifact, which can be downloaded.

This is the .yaml part that is performed at the end of the .yaml.

  # Publish the playwright-report folder as an Artifact belonging to the Job
  # Note that once a job artifact has been published, it cannot be modified so eg. re-running the same job results in failed publishing
  # Whether tests succeed or not, Playwright creates a html-report of the test run in a separate folder and we need to publish it to access it from the virtual server
- publish: $(System.DefaultWorkingDirectory)/playwright-report
  displayName: 'Publish the test report folder /playwright-report'
  artifact: playwright-report
  # By default the publish will not happen if a test fails, but we need the fail report, so we need to tell the job to run it on success and failure
  condition: succeededOrFailed()

Then you can view the Artifact(s) in the Pipeline:
image

@daniavander
Copy link
Author

hi @Wilhop I also publish atrifacts it work well, just i would like to see easier mode with html publisher

@yury-s I do not tell more, just in main branch i use 1.23.3 version and the html viewer work wll, on the other branch i use the latest version and does not work this plugin

@yury-s
Copy link
Member

yury-s commented Aug 26, 2022

Since the report opens fine locally, it looks like a problem with Azure DevOps as noted above and the plugin that tries to embed the html report. You should address this question to HTML-viewer extension. I'm closing this bug but feel free to open a new one if there is something we can change in Playwright to help that extension work better.

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

3 participants