vesuvius sm functional test report

Upload: jody-murphy

Post on 05-Apr-2018

216 views

Category:

Documents


0 download

TRANSCRIPT

  • 7/31/2019 Vesuvius SM Functional Test Report

    1/4

    Dell HTML Functional Test ReportVersion 11

    Last Revised Date: February 2004

    Overview

    Scope

    Testing includes:

    Verifying that the HTML files display and function correctly under Internet Explorer.

    Verifying the HTML requirements documented in the Test Case.

    Testing does not include:

    Proofing the documents text for grammar, spelling, readability, word usage, technical accuracy,

    etc.

    Making discretionary changes to the html code in order to improve the appearance of the code (for

    example, adding or trimming white space, or indenting table rows and list items).

    Correcting code validation errors that are not affecting the display or functionality of the

    document (for example, inconsequential nesting errors).

    Quality Goals

    To achieve zero functional defects and to display high-quality HTML.

    Test Matrix

    Any computer system can be used to complete the testing.

    Issue Reporting

    All issues should be logged on the report. Statements should include specific descriptions for each issueincluding the filename and the line number in the html code where the error is found. (Use the Show line

    numbers button in Homesite to identify line numbers.) .

    Test Report

    The testing organization will provide a final test report to the HTML development manager.

    Contact

    If you have questions about this test report, contact [email protected], Dell Information

    Development.

    Test Document Information

    Section I must be filled in by the company developing the document.

    Section II must be filled in by the test house, or self-certified supplier.

    Section I: Document Supplier

    Document title as it appears in

    the document:

    Dell OptiPlex GX270 Service Manual

    Point of contact: Eliza Cunningham at 512-728-1993 or [email protected]

    Date document is submitted for

    testing:

    5/27/04

    Required browsers: Internet Explorer

    05/20/12

    1

  • 7/31/2019 Vesuvius SM Functional Test Report

    2/4

    Scope of Testing. Supplier place check mark next to one of these two options:

    Document issues and make essential corrections.(Do not make nonessential corrections. See Scope in the beginning of this document.)

    Document issues only. Do not make corrections.(Dell writers: use this option for in-house WebWorks conversions.)

    Section II: Test House or Self-Certified Supplier

    Tested by (name): Amit Manikoth

    Document title as it appears in

    the document:

    Dell OptiPlex GX270 Service Manual

    Date tested: 5/28/2004

    Estimate setup time for test:

    Estimated test case time:

    Test Case

    Test Steps Pass Fail Comments

    1. Verify that the contents page is named index.htm X

    2. Verify that the contents page is in the specified language X3.Verify that each HTML file contains the appropriate character setmeta tag in the section.NOTE: The first meta tag in each group is the default tag. Only one

    character set meta is needed. Do not put multiple character set meta

    tags in files.

    Dutch, English, Finnish, French, German, Italian, Norwegian,

    Portuguese, Spanish, Swedish

    Hebrew

    Japanese

    Korean

    Polish, Czech, Hungarian

    Russian

    X

    05/20/12

    2

  • 7/31/2019 Vesuvius SM Functional Test Report

    3/4

    S Chinese

    T Chinese

    Thai

    Turkish

    4. For all files, ensure that the following HTML tag appears

    somewhere between the and the tag near the top

    of the file:

    For all files, ensure that the following HTML tags appear immediatelyafter the

  • 7/31/2019 Vesuvius SM Functional Test Report

    4/4

    such as vlink= or link=, or link color=.

    11. Verify that each HTML file contains the correct body tag ().

    X

    12. Verify that each HTML file (page) is displayed properly in each ofthe required browsers (correct formatting in one browser may

    be incorrect in another.). Specify the resolution(s) tested in the

    comments column.

    X

    13. Ensure that each page is in the correct language. X

    14. Verify that a title.txt file is part of the directory, and is in the

    correct language. The text string should not be longer than 40

    characters, and should not contain , , \, or /.

    X No title.txt file

    was present.

    Results:

    Issues fixed during Functional Test :

    Test Case 4:

    index.htm had an extra set of footer tags:

    (line numbers 72 and 73 in the code)

    These were deleted.

    Test Case 7:

    chsintr.htm, cntrlpnl.htm, iopnl.htm, pwrsply.htm, and safety.htm had instances of