Differences

This shows you the differences between two versions of the page.

--- course_outline [2021/03/12 22:25] – bil
+++ course_outline [2021/03/31 18:26] (current) – bil
@@ Line 5: / Line 5: @@
 Study materials and lab tasks will be posted here.
-https://www.linkedin.com/learning/programming-foundations-software-testing-qa
+--></html>
-.Bug Reporting
-https://www.linkedin.com/learning/nail-your-software-tester-interview/solution-bug-reporting
+====== Week 11 (to be completed by Wednesday, April 7) ======
+==== Due ====
+The only due item this week is your Peer Assessment 4 feedback on the design documents you have received, due on Wednesday, April 7.
+You should of course be working towards completing your project so you can present all its features at the last progress report meeting that will take place this week.
+There is no lab task, but the TAs will be available for any make up lab tasks necessary.
+==== Study material ====
+Our topic this week is refactoring. As everybody is certainly busy, it is an optional topic.
+If you do not know how to rename variables in Eclipse using the refactoring facilities, I highly recommend watching the first part of this [[https://www.linkedin.com/learning/eclipse-essential-training/refactoring-code|short video]].
+For more on refactoring, you can watch this [[https://echo360.ca/media/8cd73b73-479e-433e-bd76-aa1f09d0098b/public|instructor video]] on it. Feel free to do this after the term is finished.
+==== Lab task ====
+There is no lab task, but the TAs will be available for any make up lab tasks necessary.
+==== Weekly goals ====
+  - Learn about refactoring
+  - Provide feedback on the design documents you received before the deadline
+  - Prepare for the last progress report meeting with the customer
+  - All requirements must be implemented and tested
+  - Documents are being finalized
+====== Week 10 (to be completed by Wednesday, March 31) ======
+==== Due ====
+There are two things due this week:
+  - Peer Assessment 4 will be posted on Thursday (Mar 25). You will be submitting your design document on Wednesday, March 31 to receive feedback. As usual, you will be graded for the feedback you will provide.
+  - For the lab task, you will demonstrate how you debugged one of the bugs you team received last week.
+==== Study material ====
+Our topic this week is debugging. Start by watching these two videos on debugging in Eclipse: 1. [[https://www.linkedin.com/learning/eclipse-essential-training/using-breakpoints|Breakpoints]] 2. [[https://www.linkedin.com/learning/eclipse-essential-training/debugging-a-java-app|Debugging]]
+When using Gradle, the process is a bit more involved, so next watch this [[https://echo360.ca/media/ed2cfa05-2782-4350-a872-827244b208c5/public|instructor video]] on how to set up Gradle for debugging. The code in the video is in the JavaFXSample project in [[https://github.com/biltzerpos/TeachingCode|this github repository]].
+==== Lab task ====
+Your team should divide the bug reports you received last week among the team members. You should respond to all the bug reports assigned to you on github.
+Choose one of the bug reports assigned to you. Use the debugging facilities of Eclipse (set breakpoints, step through etc) to trace the source of the bug and fix it.  Demonstrate the above process to the TA (revert to a commit that still has the bug to demonstrate if necessary).
+==== Weekly goals ====
+  - Learn about debugging
+  - Produce a complete draft of your design document and submit it by the deadline
+  - Ensure other documents are also being worked on
+  - All requirements must be implemented and ready for testing/debugging
+====== Week 9 (to be completed by Wednesday, March 24) ======
+==== Due ====
+There are two things due this week that are both related to bug reporting:
+  - For Peer assessment 3, you are required to submit 3 bug reports for each of the two projects you are evaluating. See the PeerScholar link for more details.
+  - For the lab task, you will choose one of these bug reports and demonstrate the bug to the TA.
+==== Study material ====
+Our topic this week is bug reporting. Start by watching Section 4 (Bug Reporting) of this [[https://www.linkedin.com/learning/programming-foundations-software-testing-qa|online course]].
+For the bug reports that you will create this week, use the list of sections in this [[https://www.linkedin.com/learning/nail-your-software-tester-interview/solution-bug-reporting|video]]. You should also add the input you tested with as an attachment, and list which MusicXML viewer(s) you tested with.
+If you'd like to learn more about bug reports, this is a great but longer [[https://www.linkedin.com/learning/software-testing-foundations-bug-writing-and-management|online course]]. If you have time for only one video from it, watch [[https://www.linkedin.com/learning/software-testing-foundations-bug-writing-and-management/common-bug-reporting-issues|this one]].
+==== Lab task ====
+Choose one of the bug reports you created this week, demonstrate to the TA the incorrect behaviour, and present the bug report.
+==== Weekly goals ====
+  - Learn about bug reporting
+  - Produce constructive bug reports for peer systems
+  - Implementation on all new requirements must be underway
+  - Your system must be able to handle simple tabs for all three instruments by now
---></html>
 ====== Week 8 (to be completed by Wednesday, March 17) ======