mirror of
https://github.com/photoprism/photoprism.git
synced 2026-03-02 22:57:18 -05:00
Use a SQL mock driver to test database interactions #74
Labels
No labels
ai
android
api
auth
awesome
bug
bug
ci
cli
config
database
declined
deprecated
docker
docs 📚
documents
duplicate
easy
enhancement
enhancement
enhancement
epic
faces
feedback wanted
frontend
hacktoberfest
help wanted
idea
in-progress
incomplete
index
invalid
ios
labels
live
live
low-priority
macos
member-feature
metadata
mobile
nas
needs-analysis
no-coding-required
no-coding-required
observability
performance
places
please-test
plus-feature
priority
pro-feature
question
raspberry-pi
raw
released
released
released
research
resolved
security
sharing
tested
tests
third-party-issue
thumbnails
upgrade
upstream-issue
ux
vector
video
waiting
won't fix
won't fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/photoprism#74
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lastzero on GitHub (Dec 20, 2018).
Originally assigned to: @lastzero on GitHub.
As a developer, I want to test database interactions without needing a real database connection to improve reliability and performance of my tests.
We'll still need a real test database like TiDB or MySQL for (most) integration and acceptance tests, see #60.
Acceptance Criteria:
@mingh168 commented on GitHub (Aug 10, 2019):
@lastzero can i have a go at this one please, Thanks
@lastzero commented on GitHub (Aug 10, 2019):
Yes, please :)
I've been on vacation, will be more active in September again to work on the remaining issues...
@lastzero commented on GitHub (Jan 5, 2020):
After a lot of discussions, we decided to use a real db for testing since this causes least overhead and we have limited resources (we're aware about the tradeoffs). Database fixtures will be put in
assets/resources/examples/fixtures.sqland must be maintained manually for now.