lemmy/crates/db_views/src/lib.rs

#[cfg(test)]
extern crate serial_test;

pub mod comment_report_view;
pub mod comment_view;
pub mod local_user_view;
pub mod post_report_view;
pub mod post_view;
pub mod private_message_view;
pub mod site_view;
Support plain `cargo test` and disable unused doctests for speed Since DB tests execute diesel migrations automatically, concurrent execution causes flaky failures from simultaneous migrations. This can be worked around using `cargo test --workspace -- --test-threads=1`, which is what the CI config does, but this is not intuitive for newcomer developers and unnecessarily slows down the test suite for the majority of tests which are safe to run concurrently. This fixes this issue by integrating with the small test crate `serial_test` and using it to explicitly mark DB tests to run sequentially while allowing all other tests to run in parallel. Additionally, this greatly improves the speed of `cargo test` by disabling doc-tests in all crates, since these are aren't currently used and cargo's doc-test pass, even when no doc-tests exist, has significant overhead. On my machine, this change significantly improves test suite times by about 85%, making it much more practical to develop with tools like `cargo watch` auto-running tests. 2021-02-25 14:43:39 -05:00			`#[cfg(test)]`
			`extern crate serial_test;`

Adding report views. 2020-12-16 22:03:03 -05:00			`pub mod comment_report_view;`
Beginning to add new comment_view. 2020-12-15 10:28:25 -05:00			`pub mod comment_view;`
A first pass. 2021-03-10 23:43:11 -05:00			`pub mod local_user_view;`
Adding report views. 2020-12-16 22:03:03 -05:00			`pub mod post_report_view;`
Starting to add post_view. 2020-12-10 15:53:49 -05:00			`pub mod post_view;`
Adding private message view. 2020-12-16 17:16:48 -05:00			`pub mod private_message_view;`
Starting on siteview. 2020-12-02 14:32:47 -05:00			`pub mod site_view;`