mirror of https://github.com/google/comprehensive-rust.git synced 2025-04-23 08:07:38 +02:00

Dustin J. Mitchell 9f67c9b0e7

Adjust morning-session timings downward (#1786 )

Based on feedback from @marshallpierce that mornings took about 2.5
hours, this adjusts a bunch of the morning times downward to try to
match that. In other words, this is trying to make the times in the
course more accurate, rather than reducing the amount of time available
for these slides.

This also updates the `course-schedule` tool to be able to show
per-segment timings.

2024-02-06 15:48:56 -05:00

1.0 KiB

Raw Blame History

minutes

minutes
5

Unit Tests

Rust and Cargo come with a simple unit test framework:

Unit tests are supported throughout your code.
Integration tests are supported via the tests/ directory.

Tests are marked with #[test]. Unit tests are often put in a nested tests module, using #[cfg(test)] to conditionally compile them only when building tests.

fn first_word(text: &str) -> &str {
    match text.find(' ') {
        Some(idx) => &text[..idx],
        None => &text,
    }
}

#[cfg(test)]
mod tests {
    use super::*;

    #[test]
    fn test_empty() {
        assert_eq!(first_word(""), "");
    }

    #[test]
    fn test_single_word() {
        assert_eq!(first_word("Hello"), "Hello");
    }

    #[test]
    fn test_multiple_words() {
        assert_eq!(first_word("Hello World"), "Hello");
    }
}

This lets you unit test private helpers.
The #[cfg(test)] attribute is only active when you run cargo test.

Run the tests in the playground in order to show their results.

1.0 KiB Raw Blame History

Unit Tests

1.0 KiB

Raw Blame History