indeed

I upvote this idea, it a quite challenge to get an awesome tool to test native Mobile apps

@@alleluiaizimpamvu9971 Neste momento utilizo o Detox para testar app desenvolvida em React Native e é como o Playwright na sintaxe

What is Stale screenshots ?

@sen86sen I meant screenshots that are no longer being taken. Playwright should delete all the screenshots that weren't taken in a all-tests run, if we provide a flag for it.

@ that’s a great idea actually .. and thanks for the explanation and your time

Та Дімон сидить в ахірє

The other languages get updated usually 1-2 weeks after the normal release happens in order to pick up potential bugfixes.

@@Playwrightdev Thank you I found the changes for Java and thanks for the quick push within 2 days. I believe the quicker from Playwright will helpful in SDET's to taste the features on their IDE's and the execution. Thanks Simon Knott & Dimtry ...

@@Playwrightdev I tried snapshots with Java_Eclipse environment and it worked well for Positive scenarios but in case of failed tests I am not be able to see the error on the particular failure like you have achieved instead I got the error like below. Exception in thread "main" org.opentest4j.AssertionFailedError: Locator expected to match Aria snapshot: - banner: - heading "Playwright enables awasome end-to-end testing for modern web apps." [level=1] - link "Get started" - link "Star microsoft/playwright on GitHub" - link /[\d,.]+[bkmBKM]+\+ stargazers on GitHub/ Received: {raw=- banner: - heading "Playwright enables reliable end-to-end testing for modern web apps." [level=1] - link "Get started" - link "Star microsoft/playwright on GitHub": Star - link "67k+ stargazers on GitHub": 67k+, regex=- banner: - heading "Playwright enables reliable end-to-end testing for modern web apps." [level=1] - link "Get started" - link "Star microsoft/playwright on GitHub" - link /[\d,.]+[bkmBKM]+\+ stargazers on GitHub/} Call log: - Locator.expect with timeout 5000ms - waiting for getByRole(AriaRole.BANNER) 9 × locator resolved to <header class="hero hero--primary heroBanner_UJJx">…</header> - unexpected value "- banner: - heading "Playwright enables reliable end-to-end testing for modern web apps." [level=1] - link "Get started" - link "Star microsoft/playwright on GitHub": Star - link "67k+ stargazers on GitHub": 67k+" at com.microsoft.playwright.impl.AssertionsBase.expectImpl(AssertionsBase.java:74) at com.microsoft.playwright.impl.LocatorAssertionsImpl.matchesAriaSnapshot(LocatorAssertionsImpl.java:336) at com.microsoft.playwright.assertions.LocatorAssertions.matchesAriaSnapshot(LocatorAssertions.java:2190) at rl149.Sanpshot149.main(Sanpshot149.java:38) Can anyone encounter the same kind of error on Java_Eclipse ?

npx playwright test --config foo/bar/playwright.config.ts See here: playwright.dev/docs/test-cli#reference

Yes it should all just work! If not - please file a bug on GitHub, thanks!

you have to decide what is important to test and what should be mocked. What is important for the user to see. For example a recommended movie might always change so this could be mocked cause it doesn't matter which movie is shown just that one is shown and is clickable etc. Again it all depends on the application you are testing

The problem is not in what to mock, but how to mock cause with SSR and next Js apps there is no any api requests in the console that could be intercepted and mocked. You just get the whole page already rendered from the server

White box mocking with assumtions about json and other http parts is a dangerous practice, see my comment at the top.

I disagree on that one. You can mock the data to see if your frontend responds correctly to various scenarios, which gives you consistent/stable/quick results. Then, you can create a single test without mocking, but with intercept and validating the actual response schema is valid (and adding more tests for backend controller will give you more confidence). Once verified, it's "happy days"

@@rostyslavznachenko7472 I fully agree with your statement, but I cant see in which part you are disagree, let me rephrase my point: in my opinion the only bad think in this video is "magic string" in the assertion. Overall POC example is simple and clear.