From 2a23eaced6a4b0f3241430fb8d9d177a482ca907 Mon Sep 17 00:00:00 2001
From: "Carol (Nichols || Goulding)" <carol.nichols@gmail.com>
Date: Sun, 20 Sep 2015 18:31:41 -0400
Subject: Add some exercises about tests!

---
 tests/tests1.rs | 44 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 44 insertions(+)
 create mode 100644 tests/tests1.rs

(limited to 'tests/tests1.rs')

diff --git a/tests/tests1.rs b/tests/tests1.rs
new file mode 100644
index 0000000..15f810a
--- /dev/null
+++ b/tests/tests1.rs
@@ -0,0 +1,44 @@
+// 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 :)
-- 
cgit v1.2.3