Mockito Reviews

Playwright Reviews

Mockito mentions (14)

• I build CRUDS as an intern. My boss told me my tests were ok, but too slow, so he modified them to run in a specific order to reuse the app context on all tests. Is that a good practice though?

  I would say no. Mocking is generally creating a mock object. Like with Mockito. https://site.mockito.org. Source: about 1 year ago

• Instancio 2.2.0 released

  Could you explain how this relates to Mockito? Could it be used together perhaps for more advanced mocking? Source: over 1 year ago

• Testing JSch SFTP Code

  You could use mocks, but you'd basically be implementing JSch. I'm not mocking a framework, and recently learned my misgivings have a name: the soviet police station anti-pattern. Source: over 1 year ago

• Create and use a result captor in Mockito

  In Mockito it exists the possibilty to use ArgumentCaptor to allow developers to verify the arguments used during the call of mocked method, but not the result itself. Indeed, in the current release of Mockito it's not possible to capture it and my solution to do that is to build a ResultCaptor class which implements the Answer interface and generify it for more conveniance. - Source: dev.to / about 2 years ago

• Reverse engineering Mockito. Part 1. Single use case

  So I am building my own little project, which you can read about HERE and I have made the decision to use as few libraries as possible. Now that I am doing some testing I need some mock objects, which means I have to try to recreate Mockito. So this series will be me recreating Mockito the best I can. This post will be about creating a simple single use case implementation that gets our annotation working. It... - Source: dev.to / about 2 years ago

Playwright mentions (232)

• Cypress vs. Playwright for Node: A Head-to-Head Comparison

  Playwright is an end-to-end testing framework developed by Microsoft and available in multiple programming languages. Its focus is on cross-browser testing, using Chromium as the default browser. To perform the test logic on a Chromium-based browser, it controls and instructs a browser instance to perform desired actions via the DevTools Protocol. - Source: dev.to / 11 days ago

• Typed E2E test IDs

  We start with a project that was bootstrapped with npx create-next-app. For the E2E test we use Playwright and set it up as described in the testing guide provided by Next.js. - Source: dev.to / about 2 months ago

• Playwright Scraping infinite loading & pagination

  Playwright is a powerful tool developed by Microsoft, it allows developers to write reliable end-to-end tests and perform browser automation tasks with ease. What sets Playwright apart is its ability to work seamlessly across multiple browsers (Chrome, Firefox, and WebKit), it provides a consistent and efficient way to interact with web pages, extract data, and automate repetitive tasks. Moreover, it supports... - Source: dev.to / about 2 months ago

• Sometimes things simply don't work

  The consensus I could gather is either use playwright or use a workaround to solve it in the puppeteer layer. The root cause of the bug is a websocket size limitation on the CDP protocol for chromium. - Source: dev.to / about 2 months ago

• The best testing strategies for frontends

  With the advent of tools like Puppeteer and now Playwright, end-to-end testing has become much easier and more reliable. For anyone who's used Selenium in the past, you know what I'm talking about. Puppeteer has opened the way in terms of E2E tooling, but Playwright has taken it to the next level and made it easier to await for certain selectors or conditions to be fulfilled (via locators), thus making tests... - Source: dev.to / about 2 months ago