Monday March 19-Wednesday March 21: Regular classes: Testing
Friday March 23: No regular class, instructor meets with teams as needed
I will send email to all students listing teams that I want to consult with.
Monday March 26: Dr. Brandi Frisby: Technical writing
Wednesday March 28: Regular class: Coding
Friday March 30: No regular class, instructor meets with teams as needed
I will send email to all students listing teams that I want to consult with.
April 2-6: Testing review with instructor
April 9-13: Code review/project status meeting with instructor
April 16-20: Final presentation practice in Marksbury Auditorium
April 23-27: Final presentations in Marksbury Auditorium
You have one meeting as a team to discuss your test plan April 2-6 during the regular class periods. It is the same week day (Mon/Wed/Fri) and section time as your midterm presentation (except for Team 18).
By 7 AM April 2 have your test plan available:
as a link from your project web page, OR
in your Github repository
that describes your test plan for the test categories:
1. Unit testing
2. Integration/function testing
3. System testing
4. Customer/user testing
These are the generic test case categories. Each project will have specific requirements to match the project. Testing will be covered in class. See examples from previous semesters here.
Send me email by 7 AM April 2 with instructions to access your test plan. If on your web page, that is sufficient. If in Github, what folder it is in. Verify that I will have access (public access, or if private, give paulp@cs.uky.edu access.
Code/Project Status Review with Instructor (held in classroom)
You have one meeting as a team for a code review and status meeting April 9-13 during the regular class periods. It is the same week day (Mon/Wed/Fri) and section time as your midterm presentation (except for Team 18). By 7 AM April 9, make your code accessible to the instructor. Email the instructor instructions on how to access your code. A popular method is to give the instructor access to your online repository. Do not assume that the instructor will be familiar with your repository. Provide instructions. Make it clear what modules that should be inspected. Provide a list in your email. For some projects, the best method is to zip the changed modules and send it to the instructor.