diff --git a/assignment/blackbox_testing.md b/assignment/blackbox_testing.md
index 708d6d5cad49d71727c9ee7f3596a6230073be1c..21b806ea53a1d2c0333dd56f8805a36bf29b4b8f 100644
--- a/assignment/blackbox_testing.md
+++ b/assignment/blackbox_testing.md
@@ -1,6 +1,6 @@
 # Blackbox Testing
 
-Due: February 3, 2020 at 9:30am
+Due: June 18, 2020 at 11:00am (CDT, UTC-5)
 
 ## Overview
 
@@ -128,6 +128,13 @@ stack. For example:
 
 1.  Complete your test plan for the `Calculator.calculate()` method.
 
+    -   You do not need to look at `Calculator`'s source code to develop your
+        tests. That's the point of blackbox testing. If you do look at
+        `Calculator`'s source code, be warned that it has some bad design in
+        it; this is intentional for discussion purposes later. Bear in mind
+        that these bad design aspects would make it more error-prone and harder
+        to  maintain.
+
     1.  Complete developing the testing requirements. The testing requirements
         should be traceable to `Calculator.calculate()`'s  functional
         requirements (listed after the assignment instructions).
@@ -167,6 +174,13 @@ stack. For example:
 
     1.  Do *not* attempt to fix the faults revealed by your tests.
 
+    -   There are bugs that are intentionally included in `Calculator`. If
+        a test fails, do the due diligence to make sure that your test
+        isn't faulty, but otherwise it's okay that you found a bug. On a
+        real project, finding a bug is a good thing because it means that
+        you can fix it and that bug won't get shipped. (Again, do not attempt
+        to fix the bugs that you find in this assignment.)
+
 1.  Produce a test report. Normally you wouldn't commit an auto-generated test
     report to the repository; however, for grading purposes we will require
     that you do so.