Writing specs for complex validations is annoying. AcceptValuesFor makes it easy to test your validations with real world values, asserting which values should be accepted by your model and which should not.
Read the original blog post.
describe User do
describe "validation" do
subject(:user) { User.new }
it { should accept_values_for(:email, "john@example.com", "jane@example.org") }
it { should_not accept_values_for(:email, nil, " ", "john", "john@example") }
end
end
group :test do
gem "accept_values_for"
end
Like AcceptValuesFor?
FAQs
Unknown package
We found that accept_values_for demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
CISA’s 2025 draft SBOM guidance adds new fields like hashes, licenses, and tool metadata to make software inventories more actionable.
Security News
A clarification on our recent research investigating 60 malicious Ruby gems.
Security News
ESLint now supports parallel linting with a new --concurrency flag, delivering major speed gains and closing a 10-year-old feature request.