Comments (10)
Please let me know if this repository is still maintained
yep, it is still maintained)
but unfortunately I don't have enough time for this feature
if I shall do a PR
I'm really will be appreciated for you work
if it should be backward compatible
yes please let it be backwards compatible because many people won't want to upgrade
from playwright-azure-reporter.
Hello, sorry but I don't think I will be able to do such a pull request quickly, I realized the time I need to do it, and I think it would be better used by putting those features in an AzureDevOps or VSCode extension directly, especially since the API seems to give some alternatives that I would like to explore
from playwright-azure-reporter.
@Az8th I got you
Let me write this feature
from playwright-azure-reporter.
Hi ! Just a remember that keeping test title clean seems to be encouraged since 1.42 update, as tags and annotations can now be added outside of it.
Could the same be applied here ? Without decorators, it could appear like so
test("Title", {
tag: ['@tag1', '@tag2'],
annotation: [{ type: 'azureTestPlanID', description: '42' }]
}, async ({ page }) => {
//perform actions
});
Please let me know if this repository is still maintained, and if you can envisage to do it by yourself or if I shall do a PR (in this case, I need to know if it should be backward compatible)
from playwright-azure-reporter.
Just realized that using the same method for test plan/suite ID could also permit to add support for multiple plans, as annotations can also be made in test.describe()
To ensure backwards compatibility, the test plan ID should still be present in the playwright.config.ts and act as a default, that can be overrided when an azureTestPlanID is precised.
Example:
...
annotation: [
{ type: 'azureTestPlanID', description: '1' },
{ type: 'azureTestSuiteID', description: '34' },
{ type: 'azureTestCaseID', description: '42' },
// { type: 'azureSharedStepID', description: '255' }
]
...
from playwright-azure-reporter.
@Az8th I had published beta version this this feature, try it
npm i @alex_neo/[email protected]
Also you can read README about version
from playwright-azure-reporter.
Nice ! Can't at the moment, but will definitely try by tomorrow ;)
I see that you have chosen to use tags over annotations, aren't they exposed ?
from playwright-azure-reporter.
@Az8th any updates?
from playwright-azure-reporter.
Tested it in CI for a week, while I encountered no bugs, I think that tags are even worse than titles for ID specifying (titles are somewhat unique, while tags should be used to pack test by categories)
We should definitely go for test annotations here ! I don't know if they are exposed in the Playwright API, I will check this later today !
from playwright-azure-reporter.
Seems it is : https://playwright.dev/docs/api/class-testcase#test-case-annotations
Can adapt your PR to support annotations instead of tags if you want.
Unless you also want to support tags, but I would suggest to add a "id-mode" parameter that could be either title, tag or annotation to avoid unwanted collisions, which defaults to "title" to maintain backwards compatibility
from playwright-azure-reporter.
Related Issues (20)
- Cannot set automated status from the testRunConfig HOT 9
- Doesnโt reset the status to pass once it is fail or blocked HOT 4
- Inconsistency in updating test case status in ADO HOT 9
- getting error azure: Failed to create test run. Reporting is disabled on azure pipeline HOT 1
- Question: System.AccessToken usage HOT 1
- SyntaxError when catching error HOT 1
- Trouble using testPointMapper HOT 1
- not able to find the attachment, which folder is it looking ? HOT 4
- [Question] How to correctly links test with complex configurations ? HOT 1
- [Bug/Suggestion] Entire report publishing skipped if only one ID is invalid HOT 7
- [Suggestion] Add a token rights section in the docs HOT 3
- [Question] Test plan is in project A, pipeline is in project B. Can i get cross project pipelineReference? HOT 2
- configurationIds: Error logs when test case does not have proper assigned configurations in Azure HOT 3
- Test Run Data - Execution History, not showing up HOT 13
- [Question] Possible to continue to see console output with playwright-azure-reporter enabled? HOT 6
- [Question] Associate test cases HOT 1
- SyntaxError: Unexpected token 'R', "Request ti"... is not valid JSON HOT 9
- Publish test results only for specific test suites HOT 9
- [Bug] Azure DevOps pipeline always succeed when missing permissions to publish test results. HOT 3
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-azure-reporter.