SE 101 Freshman Seminar
Week 9 - Testing Software
|
Class Plan:
· Submit your completed Test Plans to the dropbox at the end of this period.
Instructions: This session you will be helping out students from the Software Engineering I course (that you will take next year) by testing their project and providing them feedback. You are serving as an "independent test team" - it is often hard for developers to find all the bugs in software, because they are so used to the software that they only use it in certain set ways. Hence it is useful for them to get an independent team of people to try out the software and provide feedback on bugs and improvement areas. Remember that you are testing a work-in-progress: what you see is more like a beta version than a release. Your goal is to provide constructive inputs to the development team on bugs that need fixing and areas for improvement, rather than to criticize the software. You are also welcome to use this as an opportunity to interact with them and learn more about the Software Engineering I course and project! Download the 361 project assigned to your team by your instructor. This is to be found in the corresponding SE361 team's website under a URL of the format: http://www.se.rit.edu/~f361-XXy/ where XX represents the corresponding section number (e.g. 02) and y is the team's letter (e.g. a ). Don't forget to also download their requirements document and the test documents. [Note: some teams may have provided a README file or chosen to wrap their entire release into a .zip file to help you get what you need]. You may also reference the project's Statement of Needs for more information. If you still have questions ask the project's team representative for help. Save the excel spreadsheet containing the Test Plan into a file named "SE101 Test Form.xls" and execute the tests filling out the appropriate cell. Follow the instructions and document the results of your testing (see Instructions tab within the spreadsheet or, if omitted, from sample template at: Empty Test Tracker). Read the requirements document and check if the software satisfies the requirements. You are welcome to do additional tests and report on them as well, just add them at the bottom of the test plan or include a separate file with your comments. In addition to emailing the report back to the 361 team, submit a copy to the "Week 9 Activity - 361 Project Test Report" myCourses drop box. Homework for Next Week:
|
|