Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: add tests to catch 2 mutants #142

Merged
merged 1 commit into from
Mar 19, 2024
Merged

test: add tests to catch 2 mutants #142

merged 1 commit into from
Mar 19, 2024

Conversation

cljoly
Copy link
Owner

@cljoly cljoly commented Mar 19, 2024

The mutants were:

MISSED   rusqlite_migration_tokio_async/src/lib.rs:2:10: replace + with * in add in 0.2s build + 0.1s test
MISSED   rusqlite_migration/src/lib.rs:535:35: replace - with + in Migrations<'m>::goto_down in 0.9s build + 1.5s test

While we are here, shard mutants to avoid waiting for too long on CI.

@coveralls
Copy link

coveralls commented Mar 19, 2024

Coverage Status

coverage: 95.808%. remained the same
when pulling 96ba69f on fix-and-shard-mutants
into 45a359b on master.

@cljoly cljoly force-pushed the fix-and-shard-mutants branch 3 times, most recently from 6d5c213 to 96ba69f Compare March 19, 2024 01:38
The mutants were:
```
MISSED   rusqlite_migration_tokio_async/src/lib.rs:2:10: replace + with * in add in 0.2s build + 0.1s test
MISSED   rusqlite_migration/src/lib.rs:535:35: replace - with + in Migrations<'m>::goto_down in 0.9s build + 1.5s test
```

While we are here, shard mutants to avoid waiting for too long on CI.
@cljoly cljoly merged commit f14e7f6 into master Mar 19, 2024
30 checks passed
@cljoly cljoly deleted the fix-and-shard-mutants branch March 19, 2024 01:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants