microsoft / microsoft/playwright-dotnet
[Question]: Visual comparisons Feature Parity
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3k
- Forks
- 304
- Avg merge
- 20h 47m
- Merged PRs (30d)
- 6
Description
Your question
Hi Just wanted to check what the approach will be in terms of feature parity with the JavaScript version of playwright.
I was looking for some basic visual testing and noticed the JS version offers this via Pixelmatch
test-snapshots
Is the plan that the dotnet version will have feature parity with JS version or do we need to look at other implementations to try achieve the same feature of the Java script version.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files or tests are identified in the question. Start by reviewing the linked JavaScript test-snapshots documentation and the .NET project's current visual-testing support, then determine whether feature parity is planned and define the required scope before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, javascript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100