Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →For screenshot-based visual regression, add Storybook’s @chromatic-com/storybook integration, store the Chromatic project token in a GitHub Actions secret, and run the visual test in your workflow. Chromatic compares rendered stories with accepted visual baselines and reports changes for review on pull requests. This is distinct from Storybook’s Vitest and test-runner options, which execute story tests rather than serving as synonyms for pixel comparison.
Choose the kind of Storybook test you need
Start with the failure you want CI to catch. A visual comparison, an interaction assertion, and an end-to-end user journey are different tests; a repository may use more than one.
| Need | Suitable path | What it checks | Trade-off |
|---|---|---|---|
| Catch unintended appearance changes across stories | Chromatic visual testing through @chromatic-com/storybook |
Rendered pixels compared with visual baselines | Uses a cloud service and project-token setup; reviewing diffs is part of the intended workflow. See Storybook visual testing. |
| Run story render, interaction, and accessibility assertions | Storybook Vitest addon | Story tests executed through Vitest | Configure the Storybook Vitest project and its runtime/browser needs for CI. See Storybook testing in CI. |
| Run generic or custom tests against a built Storybook | Storybook test-runner | Tests against a running or published Storybook | Often requires building and serving the Storybook, then waiting for it to be ready. See Storybook test-runner. |
| Check full application journeys | A separate end-to-end tool such as Cypress or Playwright | Application flows across components and pages | Complements story-level checks and visual diffs; it does not replace them. See the Storybook GitHub Actions tutorial. |
A screenshot visual test compares what the browser rendered; a markup snapshot compares HTML output and can flag changes that do not affect visible appearance. Pick the assertion based on the regression you need to detect.
Set up Chromatic visual testing
Check the Storybook version and create a project
Storybook’s visual-testing addon documentation specifies Storybook 7.6 or higher. The separate Chromatic integration page lists Storybook 6.5 or higher among its CLI/action system requirements; these describe different parts of the stack, not a single interchangeable minimum. Check the version requirements for the exact integration path you install.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Create or select a Chromatic project during setup. The addon setup connects the project to Storybook and can add configuration such as chromatic.config.json, containing a project ID and optional build script name, debug setting, or zip option.
Install and configure the addon
From the repository root, run Storybook’s documented setup command:
npx storybook@latest add @chromatic-com/storybook
Follow the prompts to select or create the Chromatic project. Review the generated configuration and commit the project configuration, but do not put the project token in a tracked file.
Store the project token as a GitHub secret
- In GitHub, open the repository and go to Settings → Secrets and variables → Actions.
- Select New repository secret, give it a clear name such as
CHROMATIC_PROJECT_TOKEN, and enter the project token from Chromatic. - Reference that secret from the Chromatic CI step as an environment variable. Never paste the token directly into workflow YAML, a command committed to the repository, or application source.
Add the CI step
Add the Chromatic action or command to the repository’s GitHub Actions workflow and pass the token through the secret. The exact action syntax and supported inputs can change; use the current Storybook visual-testing instructions and Chromatic integration requirements when choosing the invocation. Do not treat a copied workflow example as a universal Node version, action pin, or permissions policy: match it to the project’s package manager, Storybook version, and security requirements.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Run visual checks in CI when a change is approaching merge, typically on pull requests. The resulting UI Tests check reports errors or visual changes for verification; a team can configure the provider check as required before merging. Confirm the workflow has the permissions it actually needs and does not expose secrets to untrusted code.
Review visual changes instead of accepting them automatically
- Open the UI Tests result for the pull request and inspect the stories with highlighted differences.
- Decide whether each change is intentional by comparing the rendered result with the intended design and behavior.
- Accept intentional changes as new baselines through the visual-testing review flow. The addon documentation says accepted baseline changes synchronize for CI.
- Fix unintended changes in the component, styles, fonts, assets, or test setup, then rerun the workflow and review the updated result.
Blindly accepting every diff defeats the purpose of regression testing. A baseline is the expected appearance for future comparisons, so update it only after confirming the new rendering is correct.
Run Vitest story tests in GitHub Actions instead
If the goal is to execute story assertions rather than compare screenshots, Storybook’s CI documentation shows a script shaped like this:
{
"scripts": {
"test-storybook": "vitest --project=storybook"
}
}The project name assumes the default Storybook Vitest project. If your repository renamed it, change the argument to match. The workflow shape is checkout, set up a suitable Node runtime, install dependencies, then run the script; Storybook’s example uses a Playwright container/image. Pin action and runtime versions to choices verified for the repository rather than copying an example as a lasting version policy. See Storybook’s CI guide.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Vitest story tests and Chromatic visual comparison can coexist: the former checks assertions such as rendering or interactions, while the latter catches pixel-level appearance changes.
Use the test-runner when Vitest is not suitable
Storybook describes the test-runner as a fallback when the Vitest addon cannot be used. Its local-built CI pattern checks out the source, configures Node, installs dependencies and Playwright, builds Storybook, serves the static output, waits for the server, and then runs test-storybook.
A separate documented pattern runs after a deployment-status event and targets the published Storybook URL. The cited Storybook 8 example requires that published Storybook to be publicly available. See the test-runner guide for current options.
Troubleshoot common CI failures
CI links point to localhost
A link to a local Storybook address works on a developer’s machine but not on the GitHub-hosted runner or for reviewers. For useful failure links, publish the Storybook and provide its URL; the Vitest CI guidance describes using SB_URL for this purpose.
Recommended Free Tools
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
The test-runner times out or exhausts memory
Large story counts or a low-memory CI runner can make test-runner jobs time out. The test-runner documentation suggests reducing worker parallelism, for example with --maxWorkers=2, as a diagnostic option. It is not a universal default: retry after checking runner memory and job duration, then adjust parallelism to the repository’s workload.
A “snapshot” change is not a visual regression
Markup snapshots compare generated HTML; visual tests compare rendered pixels. If a markup change has no visible effect, a pixel comparison may remain unchanged. Use the test type that corresponds to the behavior you need to protect.
The installed version does not meet requirements
The Storybook visual-testing page specifies Storybook 7.6+ for the addon, while the separate integration page lists Storybook 6.5+ for its CLI/action system requirements. Verify each component’s current compatibility information rather than applying the lower figure to the entire setup. The integration page also lists latest LTS Ubuntu, Windows Server, and macOS, and current, active, or maintenance LTS Node releases as system guidance; those details can change, so check before pinning a workflow. See Chromatic integration.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
For website screenshots outside Storybook’s baseline-review workflow, ScreenshotNeo offers a screenshot API and MCP server. A single request can return an image or PDF; its clean-shot steps can accept cookie banners and remove known consent platforms, newsletter popups, and chat widgets before capture. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status. AI agents can use its MCP tools, including take_screenshot, get_page_info, and capture_pdf.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteOne-call cURL example, using ScreenshotNeo’s API documentation:
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo is not a replacement for Chromatic’s story-baseline comparison or pull-request visual review. Its free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.
Sources and compatibility
Storybook’s linked pages span its Storybook 8 visual-testing documentation and Storybook 9 CI and test-runner documentation. Check the current documentation and the repository’s installed versions before adopting action syntax, runtime versions, or service requirements.
Frequently Asked Questions
Can I use Chromatic and Vitest in the same GitHub Actions workflow?
Yes. They address different test goals: pixel comparisons and story assertions. Run both when each provides a distinct check your team needs.
Does the Chromatic visual addon work with every Storybook release?
No. The visual-testing addon documentation specifies Storybook 7.6 or higher; verify compatibility for the precise versions in your project.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
