microsoft / microsoft/roosterjs
End-to-end testing for rooster
Open
Nobody has claimed this yet.
backlog
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 190
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 16
Description
Hello,
Do we have any plan to add end-to-end testing? For example, leveraging https://github.com/microsoft/playwright to build testing pipelines using Chromium, Firefox and WebKit.
This can validate browser support automatically.
Contributor guide
No contributing guide indexed for this repository
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
Start by reviewing the proposed Playwright approach and how it would fit the roosterjs project. Define an end-to-end testing pipeline covering Chromium, Firefox, and WebKit; done means browser support can be validated automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- playwright, typescript
- Domain
- frontend, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100