You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore: set version to 1.11.0, improve README engagement
Version:
- Change VERSION from 1.12.0 to 1.11.0 (next release after 1.10.3.1)
- Fix CHANGELOG/UPGRADING references (Before v1.10.x, not v1.11.0)
README engagement improvements (from research):
- Add downloads badge for social proof
- Remove DeepWiki badge (noise, not social proof)
- Add "5 minutes" time estimate to Quick Start header
- Reframe prerequisites as confidence-building, not gatekeeping
- Reframe "Why this gem?" positively (what you GET, not what you AVOID)
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Stop shipping UI bugs. Take screenshots in your Capybara tests, commit baselines to git, and let CI catch visual regressions in pull requests — no cloud service, no subscription, runs entirely in your test suite.
8
8
9
-
**Why this gem?** Baselines live in git alongside your code — no external service, no account to sign up for, works offline. Unlike Percy/Chromatic (paid SaaS), this runs locally. Unlike BackstopJS, no Node required.
9
+
**Why this gem?** Baselines live in git — review UI changes in pull requests like you review code. Runs offline, works in CI, zero vendor lock-in. Unlike Percy/Chromatic (paid SaaS), nothing to sign up for. Unlike BackstopJS, no Node required.
10
10
11
-
## Quick Start
11
+
## Quick Start (5 minutes)
12
12
13
-
> **Prerequisites:** A working Capybara setup with a browser driver (e.g., selenium-webdriver + Chrome). See [Rails System Testing guide](https://guides.rubyonrails.org/testing.html#system-testing) if you don't have one yet.
13
+
> Already using Capybara for system tests? Add the gem and you're ready. New to system tests? See [Rails System Testing guide](https://guides.rubyonrails.org/testing.html#system-testing).
Copy file name to clipboardExpand all lines: docs/UPGRADING.md
+22-22Lines changed: 22 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
-
# Upgrading to v1.12.0
1
+
# Upgrading to v1.11.0
2
2
3
3
## Overview
4
4
5
-
Version 1.12.0 is a **minor release** with new features, performance improvements, and default behavior changes. This guide will help you upgrade smoothly.
5
+
Version 1.11.0 is a **minor release** with new features, performance improvements, and default behavior changes. This guide will help you upgrade smoothly.
6
6
7
7
**Estimated upgrade time:** 5-15 minutes depending on your setup
8
8
@@ -14,15 +14,15 @@ For **most users**, upgrading is as simple as:
14
14
15
15
```ruby
16
16
# In your Gemfile
17
-
gem 'capybara-screenshot-diff', '~> 1.12.0'
17
+
gem 'capybara-screenshot-diff', '~> 1.11.0'
18
18
```
19
19
20
20
```bash
21
21
bundle update capybara-screenshot-diff
22
22
bundle exec rake test# Verify tests still pass
23
23
```
24
24
25
-
**That's it!** The zero-config setup still works out of the box. Your existing screenshot comparisons will continue to work with v1.12.0.
25
+
**That's it!** The zero-config setup still works out of the box. Your existing screenshot comparisons will continue to work with v1.11.0.
26
26
27
27
---
28
28
@@ -34,8 +34,8 @@ Three settings now have different defaults. This is the most likely source of un
34
34
35
35
#### `blur_active_element` — Now defaults to `true`
36
36
37
-
**Before (v1.11.0):** Cursor blinking could delay screenshots
38
-
**After (v1.12.0):** Cursor is automatically hidden
37
+
**Before (v1.10.x):** Cursor blinking could delay screenshots
38
+
**After (v1.11.0):** Cursor is automatically hidden
39
39
40
40
**Action required:** Only if you want the old behavior
0 commit comments