Comments (3)
dgozman
commented on May 30, 2024
1
@justinteixeira Sounds good. I'll close this issue for now, but let us know if there would be new information and we should take a look.
from playwright.
dgozman
commented on May 30, 2024
@justinteixeira This does not look like an issue in Playwright, but rather in ADO Pipelines. I'd recommend filing an issue against ADO.
Just looking at the screenshots, perhaps the issue is somewhere in the relative paths? Try replacing reporter: [['junit', { outputFile: 'test-results/junit-results.xml' }]] with reporter: [['junit', { outputFile: 'results.xml' }]] as in the blog post, maybe that's going to help?
from playwright.
justinteixeira
commented on May 30, 2024
@dgozman Thank you for the reply. Unfortunately the solution did not work so I opened an issue with Azure DevOps.
from playwright.
Related Issues (20)
- [Bug]: .env file bypassed in debug mode 1.1.1 HOT 3
- [Feature]: Trace viewer: When using multiple browsers, I would like to see which browser is making which HTTP request HOT 1
- Video testing is not working on playwright HOT 4
- [Bug]: JUnit report contains invalid character in logs HOT 2
- [Bug]: Running issues in debug does not work and ends up in multiple different situations. HOT 4
- [Bug]: 1.44.0 automatically closes the browser on test end (even with reuseBrower:true) HOT 2
- Can't run tests in debug mode HOT 11
- [Bug]: Test info attached in html report in wrong format HOT 1
- [Feature]: receive parameters in `test.describe()` HOT 1
- Target page, context or browser has been closed HOT 1
- [Bug]: Unable to view the right context on Traces and Videos
- [Bug]: Playwright Extension Test Explorer cannot find setup.ts files HOT 2
- [Bug]: Updated to Playwright Test for VSCode v1.1.1 and all test except one dissappeared from Test Explorer view HOT 10
- [Bug]: Can't run tests with the extension (no Browser will be opend) HOT 3
- [Bug]: Setting a different locale does not work as expected HOT 4
- [Regression]: Playwright Test for VSCode can't find *.spec.ts files HOT 8
- [Bug]: "waitForResponse" always fails on firefox HOT 1
- [Bug]: Using force:true to click on an element overlapped by another element will not click or error out HOT 1
- [Bug]: Using test.fail() does not actually fail the test HOT 2
- [Bug]: Locators are in Playwright provided is not Detecting when we run same Scripts again HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from playwright.