{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

EvaluationReport.doc - Project Name Encounter Test...

Info icon This preview shows pages 1–6. Sign up to view the full content.

View Full Document Right Arrow Icon
Project Name: Encounter Page 1 of 16 Test Evaluation Report ENCOUNTER TEST EVALUATION REPORT Lekha Nair Richard Kennerly Len Smith MET CS 773 – Spring 2001 April 17, 2001
Image of page 1

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Project Name: Encounter Page 2 of 16 Test Evaluation Report CONTENTS 1. GENERAL INFORMATION ............................................................................................................. 3 1.1 S UMMARY 3 1.2 E NVIRONMENT 3 1.3 R EFERENCES 4 2. TEST RESULTS AND FINDINGS .................................................................................................... 5 F UNCTIONAL D EFECT D ISTRIBUTION R EPORT 5 P ERCENT D EFECTS BY F UNCTIONALITY 7 D EFECT R EPORT BASED ON S EVERITY 8 S EVERITY D EFECT BY F UNCTION T YPE R EPORT 9 3. ANALYSIS SUMMARY ................................................................................................................... 10 4. RECOMMENDATIONS ................................................................................................................... 11 5. FUNCTION TEST MATRIX ........................................................................................................... 12 6. BUG TRACKING REPORT ............................................................................................................ 15
Image of page 2
Project Name: Encounter Page 3 of 16 Test Evaluation Report 1. General Information 1.1 Summary This report provides an overall evaluation of the Quality Assurance activities performed over a period of 10 weeks to support the testing and validation of Encounter . It involves planning, designing, testing and analyzing the software from the user’s perspective. Four deliverables have been produced in this effort – 1) Test Plan document, 2) Test Procedures document, 3) Actual Testing Results document, 4) Evaluation Report. Encounter is a video game application that was developed as a case study for the textbook “Software Engineering: An Object Oriented Perspective” by E Braude (Wiley, 2000). Since Encounter is not a fully developed product, many of its limitations are obvious to the first time user. One of its major drawbacks at this time is that it does not have any documentation or help files to inform the user how the game is to be played. It assumes some degree of familiarity on the part of the user with playing similar video games. 1.2 Environment This software, being a video game, will most likely be installed on home personal computers. The computers used for testing were also similar in configuration to home PCs. It requires Java Runtime Environment version 2.0 or later, which if not available on the computer, can be downloaded. This may be a problem for users who do not have access to the Internet.
Image of page 3

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Project Name: Encounter Page 4 of 16 Test Evaluation Report 1.3 References “Software Engineering – An Object Oriented Approach” Eric Braude (Wiley, 2000) “Encounter Quality Assurance Test Plan” – Lekha Nair, Richard Kennerly, Len Smith (February, 2001) “Encounter Quality Assurance Test Procedure” – Lekha Nair, Richard Kennerly, Len Smith (March, 2001) “Encounter Quality Assurance Actual Testing” – Lekha Nair, Richard Kennerly, Len Smith (April, 2001) “Bugs_Encounter.xls” - (Bugs database) – Lekha Nair, Richard Kennerly, Len Smith (April, 2001)
Image of page 4
Project Name: Encounter Page 5 of 16 Test Evaluation Report 2. Test Results and Findings The major areas of functionality in Encounter have been broken down into six categories: 1) Start Game, 2) Get Status, 3) Set Qualities, 4) Move using links, 5) Display of graphics, 6) End Game.
Image of page 5

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 6
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern