Struct cargo_culture_kit::PassesMultipleTests [−][src]
pub struct PassesMultipleTests;
Rule that asserts a good Rust project: "Should have multiple tests which pass."
Justification
Some degree of automated testing is necessary for nearly all code,
and Rust makes adding tests nearly painless. The exact number
of tests is highly situational, but there should be more than
one, as even brand-new cargo
library projects are supplied with
a dummy test by default.
Caveats
This rule will actually attempt to run a project's tests through
cargo test
. If this Rule
is executed before the project has
been built or tested at all, the process of acquiring dependencies
and building them may take a while.
Trait Implementations
impl Default for PassesMultipleTests
[src]
impl Default for PassesMultipleTests
fn default() -> PassesMultipleTests
[src]
fn default() -> PassesMultipleTests
Returns the "default value" for a type. Read more
impl Debug for PassesMultipleTests
[src]
impl Debug for PassesMultipleTests
fn fmt(&self, f: &mut Formatter) -> Result
[src]
fn fmt(&self, f: &mut Formatter) -> Result
Formats the value using the given formatter. Read more
impl Rule for PassesMultipleTests
[src]
impl Rule for PassesMultipleTests
fn description(&self) -> &'static str
[src]
fn description(&self) -> &'static str
The central tenet of this Rule
. Serves as a unique identifier for Rule instances, as well as a human-readable summary of what this Rule
means for a given project. Read more
fn evaluate(
&self,
cargo_manifest_file_path: &Path,
verbose: bool,
_: &Option<Metadata>,
print_output: &mut Write
) -> RuleOutcome
[src]
fn evaluate(
&self,
cargo_manifest_file_path: &Path,
verbose: bool,
_: &Option<Metadata>,
print_output: &mut Write
) -> RuleOutcome
Does the Rust project found at cargo_manifest_path
uphold this Rule
, as summarized in the description
? Read more
Auto Trait Implementations
impl Send for PassesMultipleTests
impl Send for PassesMultipleTests
impl Sync for PassesMultipleTests
impl Sync for PassesMultipleTests