The Wayback Machine - https://web.archive.org/web/20220604040319/https://github.com/topics/e2e-testing
Skip to content
#

e2e-testing

Here are 324 public repositories matching this topic...

playwright
alexeyr-c
alexeyr-c commented May 18, 2022

When a BrowserContext is not obtained from a Playwright Test fixture, but from browser.newContext() in a test or when using Playwright Library, it should be closed once no longer needed (according to @mxschmitt at https://stackoverflow.com/questions/72284057/do-playwright-browser-contexts-opened-manually-need-to-be-closed?noredirect=1#comment127709001_72284057). Similarly pages from `context/b

good first issue
cypress
sync-by-unito[bot]
sync-by-unito[bot] commented May 31, 2022

Summary

Really small test difference with 9.x, for the settings page we confirm that the panels are collapsed by default in 9.x.

The panels are closed by default in the implementation, but there is no test confirming this behavior.

Acceptance Criteria

  • Write a test to ensure the panels are closed by default.

Resources

9.x Settings page

<img width="912" alt="Sc

good first issue unification jira-migration epic:testing-quality
pactum
emfomy
emfomy commented Sep 23, 2021

Describe the bug
Most expect methods print the request and response when the assertion fails.
However, the custom expect handler does not show these objects.

To Reproduce
Steps to reproduce the behavior:

const spec = pactum.spec();
spec.get(url);
await spec.toss();
await spec.response().to.have._((ctx) => {
  assert.fail('error');
});

*Expected behavior

enhancement good first issue

Improve this page

Add a description, image, and links to the e2e-testing topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the e2e-testing topic, visit your repo's landing page and select "manage topics."

Learn more