melib/tests: merge integration tests in one crate #336
No reviewers
Labels
No Label
IMAP
JMAP
Maildir
Retired
User Experience
User Interface
bsd
bug
contacts
currently worked on
documentation
duplicate
easy
enhancement
help wanted
invalid
linux-gnu
macos
mbox
notmuch
question
security
wishlist
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: meli/meli#336
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "melib-merge-int-tests"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Saves about 0.5 seconds from compilation and runtime.
Signed-off-by: Manos Pitsidianakis manos@pitsidianak.is
Summary of the PR
melib/tests: merge integration tests in one crate
Requirements
Before submitting your PR, please make sure you have addressed the following requirements:
git commit -s
), and the commit has a message describing the motivation behind the change, if appropriate.unsafe
code is properly documented.rustfmt
. Runmake fmt
in the project root.clippy
. Runmake lint
in the project root.make test
in the project root. If you havecargo-nextest
installed, you can runcargo nextest run --all --no-fail-fast --all-features --future-incompat-report
instead.