test: use in-memory database for e2e and kittest tests

[lklimek]

Summary

Tests were using the production database (~/.config/dash-evo-tool/data.db), risking data corruption and creating implicit dependencies on prior app setup.

Details

• Add testing feature flag to Cargo.toml
• Gate AppState::new() with #[cfg(not(feature = "testing"))] for production, and provide a #[cfg(feature = "testing")] variant that uses an in-memory SQLite database via the existing create_test_database() helper
• Widen test_helpers module visibility from #[cfg(test)] to #[cfg(any(test, feature = "testing"))]
• Zero test file changes — --all-features (already standard) enables the testing feature automatically

Test plan

• cargo build — production build works (no testing feature)
• cargo build --features testing — compiles with testing feature
• cargo test --test e2e --all-features — 10 tests pass with in-memory DB
• cargo test --test kittest --all-features — 42 tests pass with in-memory DB
• cargo clippy --all-features --all-targets -- -D warnings — clean
• cargo clippy --all-targets -- -D warnings — clean (without testing feature)

_{🤖 Co-authored by Claudius the Magnificent AI Agent}

[coderabbitai]

Warning

Rate limit exceeded

@lklimek has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 1 minutes and 26 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 5a13ded and b6dadcc.

📒 Files selected for processing (3)

• Cargo.toml
• src/app.rs
• src/database/mod.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch test/use-in-memory-db-for-tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR introduces a testing feature flag to ensure e2e and kittest tests use an in-memory SQLite database instead of the production database (~/.config/dash-evo-tool/data.db), preventing data corruption and eliminating implicit dependencies on prior application setup.

Changes:

• Added testing feature flag to separate test and production database initialization
• Gated AppState::new() with conditional compilation to use in-memory database for tests
• Widened test_helpers module visibility to support the testing feature
• Updated lint configuration to recognize the new feature flag

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
Cargo.toml	Adds testing feature flag and updates check-cfg lint to recognize it
src/database/mod.rs	Widens test_helpers visibility from #[cfg(test)] to #[cfg(any(test, feature = "testing"))] for use in e2e/kittest
src/app.rs	Splits AppState::new() into production and testing variants using conditional compilation, with testing variant using in-memory database via create_test_database()

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.