Storybook 8.1
Storybook is the industry standard workshop for building, testing, and documenting UI components. Thousands of developers use it every day, including teams at BBC, Etsy, and Dropbox. Over the past year we’ve focused on quality of life maintenance work. This culminated in the March launch of Storybook 8.0, our most performant and stable release yet. Now in 8.x, we’re back on the hunt to improve you
2024-06-03のJS: vitest v2.0.0-beta.5(browser mode)、Rspack v0.7、ESLint Migrator
JSer.info #695 - Vitest v2.0.0-beta.5がリリースされました。 Release v2.0.0-beta.5 · vitest-dev/vitest --merge-reportsがカバレッジをサポート、Promiseベースのmockに対するAssertionの追加、ブラウザモードの改善などが含まれています。 VitestのBrowser Modeは、jsdomやhappy-domを置き換える形で、コンポーネントテストのための仕組みとして作られています。 開発中のVitest 2.0ではCommands APIとmodule mockingが追加されています。 次のIssueに、VitestのBrowser Modeの目的や方向性についての解説が書かれています。 Vitest Browser Mode · vitest-dev/vitest · Discus
Vitest Browser Mode · vitest-dev/vitest · Discussion #5828
It's been some time since we gave any update on the Browser Mode, and Vitest 2.0 seems like a good time to explain how we feel about it. And we have a lot of plans! The initial purpose of Vitest was to allow running tests without a complex Jest setup but with the battle-tested Jest API everyone is already familiar with. This also meant faking the browser environment (with jsdom or happy-dom). With
Top Website Accessibility Testing Tools For Inclusive Web Design
In an increasingly digital age, the internet serves as a vital resource for information, communication, commerce, and entertainment. However, for the millions of people living with disabilities, navigating the web can present significant challenges. Web accessibility addresses these challenges by ensuring that websites, tools, and technologies are designed and developed to be usable by everyone, r
Release v2.0.0-beta.5 · vitest-dev/vitest
🚨 Breaking Changes --merge-reports to support coverage - by @AriPerkkio in #5736 (b7438) Add promise-based return assertions, do not auto-resolve returned promises - by @sheremet-va in #5749 (5f710) Do not exit process if global setup has failed - by @sheremet-va in #5726 (ddb09) 🚀 Features Add browser.ui option - by @sheremet-va in #5771 (a5033) Add median to --output-json - by @Joris
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.
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
power-assert-monorepo/packages/node at main · twada/power-assert-monorepo
Amazon.co.jp: テスト自動化実践ガイド 継続的にWebアプリケーションを改善するための知識と技法: 末村拓也: 本
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/