Microsoft Playwright Testing | Microsoft Azure
Explore Azure Get to know Azure Discover secure, future-ready cloud solutions—on-premises, hybrid, multicloud, or at the edge Global infrastructure Learn about sustainable, trusted cloud infrastructure with more regions than any other provider Cloud economics Build your business case for the cloud with key financial and technical guidance from Azure Customer enablement Plan a clear path forward fo
Release v2.3.0 · mswjs/msw
Warning This release changes how MSW treats unhandled exceptions in response resolvers. Previously, they were treated as request errors. Starting with this release, unhandled resolver exceptions will be coerced to 500 Unhandled Exception mocked error responses produced by the library. Please note that you must not intentionally throw errors in your resolvers. Please use Response.error() to mock re
Automating a11y testing: Part 1 — Axe
Earlier this year I gave a talk at the John Lewis Partnership Tech Profession Conference 2023 on the topic of automating web accessibility (a11y) testing. In this series I will cover the contents of this talk, kicking off with insights into the Axe suite of tools, followed by articles covering the wider a11y testing landscape: from visual regression testing for magnification and visual deficiencie
Release v1.6.0 · vitest-dev/vitest
🚀 Features Support standalone mode - by @sheremet-va in #5565 (bdce0) Custom "snapshotEnvironment" option - by @sheremet-va in #5449 (30f72) benchmark: Support comparing benchmark result - by @hi-ogawa and @sheremet-va in #5398 (f8d3d) browser: Allow injecting scripts - by @sheremet-va in #5656 (21e58) reporter: Support includeConsoleOutput and addFileAttribute in junit - by @hi-ogawa i
Broad integration tests | Technology Radar | Thoughtworks
While we applaud a focus on automated testing, we continue to see numerous organizations over-invested in what we believe to be ineffective broad integration tests. As the term "integration test" is ambiguous, we've taken the broad classification from Martin Fowler's bliki entry on the subject which indicates a test that requires live versions of all run-time dependencies. Such a test is obviously
Migrating away from Jest and achieving over 90% reduction in running time
Unfortunately, I’ve been using Jest since 2019. No offense to the Jest team – I’m pretty sure they’re awesome and way smarter than I am, but I wish I had made this move earlier in this project. I’m not talking about UI testing here, so assume everything I’m saying is about server-side JS. If you’re happy with Jest, don’t switch! I’m not trying to convince anyone. I’m just sharing my experience bec
Flaky Tests In React: Detection, Prevention and Tools - Semaphore
In the context of React, testing is a non-negotiable process to maintain code quality and a smooth user experience. However, there’s one frustrating bad news that is commonly faced when running tests in React. And that is flaky tests. In the simplest of words, flaky tests are tests that seem to pass most of the time but fail sometimes, all without changes to the code or test — just for no reason.
2024-03-19のJS: Storybook 8、Nuxt 3.11、Cloudflare Workers + Vitest
JSer.info #685 - Storybook 8.0がリリースされました。 Storybook 8 Storybook: UI component explorer for frontend developers 破壊的な変更として、storiesOf APIの削除、*.stories.mdxの削除、StoryShots addonの削除、Yarn v1のサポート終了などが行われています。 詳細はマイグレーションガイドを参照してください。 Migration guide for Storybook 8.0 • Storybook docs 機能追加として、Chromaticとの連携機能の実装、MSWを使ったReact Server Component(RSC)のサポート。 そのほかには、SWCを使うことでビルドパフォーマンスの改善、react-docgenがデフォルトとなるように変
Best Practices for Writing Tests with React Testing Library
React Testing Library has become the de facto standard for testing React components. Focus on testing from the user's perspective and avoidance of implementation details in tests are some of the main reasons for its success. Properly written tests not only help prevent regressions and buggy code, but in the case of React Testing Library, they also improve the accessibility of components and the ov
Improved Cloudflare Workers testing via Vitest and workerd
Improved Cloudflare Workers testing via Vitest and workerd03/15/2024 This post is also available in Español. Today, we’re excited to announce a new Workers Vitest integration - allowing you to write unit and integration tests via the popular testing framework, Vitest, that execute directly in our runtime, workerd! This integration provides you with the ability to test anything related to your Work
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Monitor Third-Party Resources that Impact UX with Playwright
GitHub - wayfair-incubator/gqmock: Project generated via @wayfair-incubator oss-template
GitHub - tokopedia/gripmock: gRPC Mock Server
Differences Between Faking, Mocking and Stubbing | Baeldung on Computer Science
Release v10.4.0 · mochajs/mocha
https://www.uber.com/en-JP/blog/simplifying-developer-testing-through-slate/
GitHub - graphql-kit/graphql-faker: 🎲 Mock or extend your GraphQL API with faked data. No coding required.
Testing Playground
Vitest
privateメソッドのテストって書かない方がいいんだっけ？
