<!-- This page will be updated a few days before each labtest. -->

• The test is 80-min long and will be held in CSEB-3057.
• You will login to one of machine in the lab using your 8-character cs username.
• Bring a photo ID.
• No questions are allowed during the test.
• You may not communicate with anyone, inside or outside the lab, by any mean during the test.
• There may be several test versions, and network traffic may be monitored.
• The test is open-book and you will have full access to your home directory, the course web site, and all the resources linked to from the course site.

The test scope include everything covered in class with the exception of CGI and Perl.

The test involves adding features to Project #2. You will first be asked to submit your implementation of of Project 2. Next, you will be asked to add a feature to the project or to modify a functionality in it. You are expected analyze the required change, design a solution, implement it, and then submit it.

Your work is marked based on correctness and on meeting the various software engineering guidelines, design patterns, and best practices.

The best way to prepare for the test involves:

• Reviewing the posted material
• Reviewing your own implementation of Project 2

<!-- ===== Lab Test #1 =====   ==== Policies ====   * The test is 80-min long and will be held in **CSEB-3057**. * You will login to one of machine in the lab using your 8-character ''cs'' username. * Bring a photo ID. * No questions are allowed during the test. * You may not communicate with anyone, inside or outside the lab, by any mean during the test. * There may be several test versions, and network traffic may be monitored. * The test is open-book and you will have full access to your home directory, the course web site, and all the resources linked to from the course site.   ==== Scope ====   The test will cover projects 0 and 1.   ==== Format ====   The test involves adding features to the projects. You are expected to analyze the requirement, design a solution, implement it, and then submit it. You can base your development on our posted //reference implementations// or on your own implementations of the projects.   Your work is marked based on correctness and on meeting the various software engineering guidelines, design patterns, and best practices.   ==== Preparation ====   The best way to prepare for the test involves:   * Reviewing the posted implementations * Reviewing the posted notes * Reviewing the posted variations * Familiarization with the posted resources   -->