Test with PostgreSQL too #309
No reviewers
Labels
No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#309
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "postgres-tests"
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?
The coverage is still only reported with SQLite, but it should be the same anyway.
You can probably add 'test' to the stages, so they are run in a logical order (test before code cov), or maybe we should calculate code coverage with both postgres and sqlite, and change the name of the
code coverage
stage, so it's more symmetricalCodecov Report
96% <93.75%> (+0.54%)
35% <0%> (+1.66%)
34.61% <0%> (+3.24%)
Continue to review full report at Codecov.
I don't know how Codecov will react if we send two different coverage reports for the same commit…
They "add" the two report, a line caught by at least one test is considered covered, lines caught by no tests are considered missed
OK, great! I will try to get coverage for Postgres too then.
I've nothing more to add, I think this can be merged
Oh thanks for your commit!