Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Can we test other databases?

Open
#34 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
mysql, postgresql, ruby, sqlite
Domain
databases, testing

Research direction

Start by comparing the repository's existing tests for SQLite, MySQL, and PostgreSQL with the ActiveRecord repository's approach to testing its adapters. Identify which additional databases are in scope and define done as equivalent coverage running successfully against them.

Written by the indexing model from the issue text.

Description

AR has adapters for a lot more than Sqlite, MySQL, and PostgreSQL. Can we test our code that works against those, too? What does the AR repo do about this?

Dominant language
Ruby
Stars
76
Forks
76
PR merge metrics
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DatabaseCleaner/database_cleaner-active_record

All issues in DatabaseCleaner/database_cleaner-active_record

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.