Management Dynamics, Inc.

GUI Testing Checklist Instructions

Overview:

Phase One release testing verifies GUI integration, functional buttons and the absence of program aborts, system error messages or other abnormal results. The scope of testing in Phase One is purposely limited to these mechanical functions to more quickly pave the way for effective Phase Two and Phase Three testing. For more information, see the document “Testing Policies and Procedures”, found on the intranet link “Testing Documentation / Test_Procedures.doc”.

Phase One screen testing is assigned to each engineer in an Excel worksheet. The worksheet is also used as a checklist to document each program function tested. The worksheet is named for each engineer and is found on the ‘Development on “netsrv”’ network drive in the Issues folder / current release subfolder (e.g. IssuesV83).

Checklist Testing Instructions:

Note: All columns are mandatory entry except for Column H (Brief Error Description), which should be left blank when there are no errors found.

All test result columns should contain one of the following values:

  • Ok – function is okay (also enter name of function for generic columns)
  • *Err – function is in error (also enter name of function for generic columns)
  • na – function is not applicable
  • see special values below for Column AV (Help)

Column A – DSPF Name: (e.g. RW001FM)

This contains the display file (screen) object name assigned for testing. For assistance in finding the menus and navigation paths needed to test the screen, refer to the Navigation Model. It may be found on the intranet link titled ‘Testing Documentation’.

Column B – Program Name: (e.g. RW001)

This contains the program object name using the assigned display file. Where the display file is shared by more than one program, test each program separately and enter each program on its own row with the display file name. For assistance in finding the programs object names using shared display files, refer to the Navigation Model and see worksheet ‘DSPF to Program Association’. It may be found on the intranet link titled ‘Testing Documentation’.

Column C – Screen Title: (e.g. Report Writer - Tariff Listing)

Paste the screen title for easy reference.

Column D – Application Tab: (e.g. Rate Analyzer/Report Writer)

Enter the menu Application Tab and the menu option name for ease of reference.

Column E – Test Date: (e.g. 10/11/02)

Enter the testing date (mm/dd/yy).

Column F – Signoff Date: (e.g. 11/11/02)

Enter the date when all issues logged for the screen (if any) have been corrected and satisfactorily re-tested.

Column G – Mode (Add, Update, View, etc.):

Enter the mode used to test the screen. Where more than one mode is tested (which may involve a different navigation path) it is okay to log test results on more than one worksheet row.

Column H – Brief Error Description: (e.g. PageDown past end of list does not display message.)

Enter a brief description of all errors found. If the issue is related to an error in another column of the worksheet (e.g. Column AZ – Page Up / Page Down), that column’s entry should contain ‘*Err’ in red color for easy identification. Each issue should also be logged in the tester’s Issues worksheet, along with required supporting documentation.

Column I – BR (Functions)

As each column’s function is tested, log either ‘ok’ or ‘na’ (not applicable) or ‘*Err’ (Error -- in red color) depending on the result. Where the column heading is generic (e.g. Columns AI – AS ‘Other Function Key’), also enter the name of the tested function (e.g. Rules).

Column AV (Help)

Log any problems with browser based Help text for the screen. The Help button at the top right corner of the display panel should be selected.

If the browser error “Page not found” is displayed, then look at the URL in the Address bar at the top of the browser page.

  • If the URL address only contains “.htm”

then enter “.htm” in the worksheet column.

  • If the URL contains a valid address

(e.g.

then enter the last section of the address following “help/”

(e.g. RCSDSPFM.htm).

Column BB - BC (Cursor Top Row / Cursor Bottom Row)

For clarification, these columns require comparing the GUI screen list panels to the subfile as displayed on the emulation screen. There should be no space on the GUI panel between the top or bottom list row and the borders. To verify that the cursor is positioned at the top and at the bottom of the list, use the emulation display to position the cursor and then verify the GUI screen. For access to the emulation display, right click on the GUI display title bar and select the function ‘Show Emulator’.

Column BS – Engr (engineer’s initials)

Enter your (the testing engineer’s) initials.

- 1 -