1 Status pane testing guidlines.

     2 

     3 

     4 Introduction:

     5 

     6 This document describes the testing procedure for the status pane uikon component.

     7 The testing procedure uses the test application, "TSpane." This application allows

     8 users to carry out manual tests and run automatic tests, through visible status

     9 pane components and the application menu.

    10 

    11 

    12 Automatic Tests:

    13 

    14 Start the TSpane application.

    15 Use the auto.all menu option and wait for "complete" to appear on the screen.

    16 Exit TSpane.

    17 There should be no Leaves or Panics.

    18 

    19 

    20 Manual Tests:

    21 

    22 This section describes the functions available in TSpane to manually test the

    23 status pane. It also gives a set of things that should be done to test the

    24 application manually.

    25 

    26 The controls available to the user are:

    27 1) A status pane. There is always a main status pane available to the application. 

    28 This may consist of one or more panes, which may contain buttons or other controls.

    29 This status pane can be altered using the manual menu options.

    30 2) "Swap vis" on the manual menu. This makes the main status pane visible or

    31 invisible.

    32 3) "Swap dim" on the manual menu. This switches the dim state of the main status

    33 pane. The controls inside the status pane should go dim, and stop responding to

    34 user events.

    35 4) "Swap fade" on the manual menu. This doesn't do anything yet, as cone does not

    36 support faded controls.

    37 5) "State" on the manual menu. This reports the visible, dimmed and faded state of

    38 the main status pane. It displays an info message containing "vis", "dim" and 

    39 "fade". If an "!" appears before any of these words, that state is set false.

    40 6) "Layout" on the manual menu. This switches the layout of the status pane.

    41 There are six valid and one invalid layouts that this command cycles through.

    42 7) "Control" on the manual menu. This changes the content of one of the status

    43 pane sub panes. It cycles through four different contents: an label, an editable

    44 text field, a clock and a button.

    45 8) "Window" on the manual menu. This creates a stand alone status pane in its

    46 own window group. If you can switch application, this status pane should hang over

    47 all the other applications. The status pane contains a "kill" button which must

    48 be pressed to delete the status pane and its window group and contents.

    49 

    50 The tester should try the following manual tests:

    51 1) At application start, try clicking on each of the buttons in the main status

    52 pane. They should all press down ok.

    53 2) Use the switch vis, dim, fade and state menu options to test that the status

    54 pane correctly responds to these state changes. Each time you change the state,

    55 try clicking on the status pane controls to see if they respond as expected for

    56 the state.

    57 3) Use the layout menu option to cycle through the seven layout options. There

    58 should be six different layouts shown and one "not found" leave message. Each

    59 the layout changes, the applications main rectangle changes. This rectangle is

    60 grey with a white border. Look for the white border between the status pane and

    61 the grey rectangle.

    62 4) Use the control menu option to change the content of one of the panes. Each

    63 different content should respond to user events in a different way. In particular,

    64 the edit field should be editable. The control menu option will work with any 

    65 of the status pane layouts. Try changing the layout and control in combination.

    66 5) Use the "window" menu option to create a floating status pane in a high 

    67 priority window group. This should float over all application that you can switch

    68 to. Dismiss the floating status pane by clicking its kill button.

    69 6) Run the automatic test using the auto.all menu option, then retry some manual

    70 tests.

    71 7) Turn on random memory failure using ctrl-alt-shift-P, and try some more manual

    72 tests.

    73 8) Exit the TSpane application. It should exit cleanly, without any panics or

    74 exceptions.

    75 

    76 

    77