datacharmer/test_db

A sample MySQL database with an integrated test suite, used to test your applications and database servers

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 10 minutes ago
Added to GitGenius on September 15th, 2026
Created on August 30th, 2015
Open Issues & Pull Requests: 2 (+0)
GitHub issues: Enabled
Number of forks: 2,704
Total Stargazers: 4,441 (+1)
Total Subscribers: 147 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.1 hours
Mean response time: 12.6 hours
90th percentile: 45.2 hours
Tracked items: 9

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • changes for 2.0 (1)
  • enhancement (1)
  • help wanted (1)
  • invalid (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

test_db is a sample MySQL database with an integrated test suite designed for testing applications and database servers.

The project addresses the need for a realistic, pre-built database environment when developing and validating database-dependent applications. Rather than constructing test databases from scratch, test_db provides a complete schema with sample data and accompanying tests that exercise the database functionality. This approach allows developers to quickly set up a consistent testing environment without manual schema creation.

Developers should adopt this tool when they need a standardized database for integration testing, performance benchmarking, or validating database server behavior. It suits projects that require a non-trivial schema with multiple tables and relationships to properly exercise database code paths. The integrated test suite means validation logic is already present, reducing the setup burden for new test environments.

The project maintains an active development cycle with regular updates to both the database schema and test coverage. Contributions are accepted and reviewed, indicating ongoing community engagement. The codebase receives periodic maintenance addressing compatibility and test improvements.