summaryrefslogtreecommitdiff
path: root/old_curriculum/tests/tests1.rs
diff options
context:
space:
mode:
Diffstat (limited to 'old_curriculum/tests/tests1.rs')
-rw-r--r--old_curriculum/tests/tests1.rs49
1 files changed, 49 insertions, 0 deletions
diff --git a/old_curriculum/tests/tests1.rs b/old_curriculum/tests/tests1.rs
new file mode 100644
index 0000000..959ed85
--- /dev/null
+++ b/old_curriculum/tests/tests1.rs
@@ -0,0 +1,49 @@
+// tests1.rs
+// Tests are important to ensure that your code does what you think it should do.
+// Tests can be run on this file with the following command:
+// rustc --test tests1.rs
+
+// This test has a problem with it -- make the test compile! Make the test
+// pass! Make the test fail! Scroll down for hints :)
+
+#[cfg(test)]
+mod tests {
+ #[test]
+ fn you_can_assert() {
+ assert!();
+ }
+}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+// You don't even need to write any code to test -- you can just test values and run that, even
+// though you wouldn't do that in real life :) `assert!` is a macro that needs an argument.
+// Depending on the value of the argument, `assert!` will do nothing (in which case the test will
+// pass) or `assert!` will panic (in which case the test will fail). So try giving different values
+// to `assert!` and see which ones compile, which ones pass, and which ones fail :)