[Docs]: Component testing "best practices" or "pitfalls" - Githubissues

microsoft / playwright

Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.

https://playwright.dev

Apache License 2.0

65.65k stars 3.57k forks source link

[Docs]: Component testing "best practices" or "pitfalls" #31361

Open sand4rt opened 2 months ago

sand4rt commented 2 months ago

Page(s)

Page: https://playwright.dev/docs/next/test-components#update

I think these topics would be useful to mention:

Determine what to test
Determine what not to test (implementation details)
How to name tests
Use the appropriate locator
Emphasise emulation over mocking
Avoid nesting / describe blocks
Avoid unnecessary abstractions (Test isolation)
Ensure your test can fail

@dgozman do you have other topics/changes in mind?

Description

Suggestion from @dgozman to include a "best practices" or "pitfalls" section for component testing: https://github.com/microsoft/playwright/issues/31339#issuecomment-2174162872. I've created a ticket to track this so I don't forget.

dgozman commented 2 months ago

do you have other topics/changes in mind?

This looks like a good starting point. If anything, some of these topics might be relevant in e2e best practices as well.