Test Case

Published on January 2017 | Categories: Documents | Downloads: 37 | Comments: 0 | Views: 231
of 650
Download PDF   Embed   Report

Comments

Content

NOTE: Update the catalog whenever you update the test cas

Test Cases
Functionality
1 2 Content Mapping 3 4 5 6 7 8 9 10 11 12

Coverage Details
Course structure, Navigation, Hyperlinks, Popup/windows, Progress tracking, Keyword interactions, CYU functionality, Sniffer functionality Text Mapping, Graphic Mapping Audio Mapping, Quality, Synchronization, and Controls Graphic clarity, integrity, read-through, animation, and grab-based graphics/Demos/Try-Its Language, Content Relevance, Spacing, Instructional design Layout and scrollbars File naming convention, Formatting, Functionality Bookmarking and Completion Status Response time ADA compliance Opening animation, Help, Glossary ILT standard checks

Audio Testing Graphic Testing Read-through Layout Testing Platform Testing LMS Testing Performance Testing
ADA Compliance Global Elements ILT_PPTs

Release Note: First Release

Name of person updating

Addition

Addition Addition Addition Addition Addition Nitin Kumar Anjali Ahuja

Addition

Amita Mujoo

Addition

Sachin Malhotra

Addition

Priti Sibal

Addition

Priyanka

ver you update the test cases.

# Test Cases
100 11 27

37 22 9 15 13 1 5 37 28 305

Date of Update 20-Aug-08

Location and name of the test case updated

What triggered this update

Notes, Print,Search test cases 31-Oct-08 added in Global Elements. (1) LMS Testing: Securing Risk (CS_1 to CS_6, Con_1) (2) Functionality-> Navigation: 20-May-09 Auto advance feature (Nav_16) Test case SB_4 added for 4-Jun-09 testing Scroll bar functionality 30-Sep-09 Included MCQ_3 and MMCQ_5 Included Scroll Bar_4 and 13-Jan-10 Print_7 -Audio synching 14-Jan-10 updation of generic test cases. -Multiple audio

Addition of sniffer testcases: Functionality<Sniffer 10-Mar-10 functionality Addition of graphic content/relevance test case under Graphic Testing tab. 13-May-10 (GRT_3) Addition of the test case: Links 6 under the Functionality tab 1-Jul-10 Addition of the test case: Audio Mapping_4 under the Audio 30-Aug-10 Testing tab

Based on the client feedback for Salesforce. ITT Courses--Lesson Presentation in Questa during Live Server testing Laureate - University of Liverpool courses - during audio testing

Test #

Test Case Summary

Functionality Course Structure (7)
CS_1 The course structure follows the correct naming convention. All file names are in lowercase without any spaces in between.

CS_2

CS_3

There are no extra or backup files.

CS_4

All basic necessary files are present.

CS_5

The attributes of the files are correct. <CT to provide the correct expected attributes of the files> The course launches smoothly.

CS_6

CS_7

All modules are present and clicking on menu items opens the correct module.

Navigation (18)
Nav_1 Navigation buttons work correctly.

Nav_2

Navigation buttons work correctly.

Nav_3

Navigation buttons on the first and last pages work correctly

Nav_4

Page counter works correctly.

Nav_5

Navigation buttons work correctly.

Nav_6

Navigation buttons work correctly.

Nav_7 Nav_8 Nav_9 Nav_10

Navigation buttons work correctly. Navigation buttons work correctly. Navigation buttons work correctly. Navigation buttons work correctly.

Nav_11

Navigation buttons work correctly..

Nav_12

Navigation buttons work correctly.

Nav_13 Nav_14

Navigation buttons work correctly. States of the buttons are consistent.

Nav_15

Branch page navigation works correctly.

Nav_16

Components that are not available in a version display an appropriate message.

Nav_17

Auto advance feature is set to off in case of any interaction on the page

Nav_18

Text disappears on selection

Hyperlinks (5)
Links_1 All links work correctly.

Links_2

All links are accessible.

Links_3

All links are consistent in treatment.

Links_4

Hotspots on the links are correctly placed.

Links_5

The cursor changes to the hand cursor only where required.

Links_6

The hot area of the page should be correct for all the resolutions

Pop-ups/Windows (11)
Pop_1 Pop_2 Course window is titled correctly. Pop-ups are smaller than the course window. Pop-up windows are not resizable.

Pop_3

Pop_4

Pop-up windows are titled correctly.

Pop_5

Pop-up windows are consistent in style.

Pop_6

Pop-up windows open at a fixed place.

Pop_7

Pop-up windows can be closed smoothly.

Pop_8

Pop-up windows close automatically on moving away from the page.

Pop_9

Pop-up windows do not hide the link they open from or overlap any other text. Any link / interaction beneath a popup is not activated.

Pop_10

Pop_11

Popups disappearing when clicking close should not stop on click. Esp. springbok

Progress Tracking (3)
Prog_1 Progress tracking works correctly.

Prog_2

Course Home tracking is working correctly.

Prog_3

Course Home tracking is working correctly.

Keyboard Interactions (3)
Key_1 Scroll bar is synchronized with the Tab action.

Key_2

Tab action follows the correct order.

Key_3

Tab action follows the correct order.

CYU Functionality Generic (11)

CYU_1 CYU_2

Submit button works correctly. Submit button works correctly.

CYU_3 CYU_4

Submit button works correctly. Submit button works correctly.

CYU_5

Appropriate feedback is displayed on attempting the CYU.

CYU_6

Number of attempts are as per design.

CYU_7

Quiz questions have correct functionality. (Scored component)

CYU_8

Scoring works correctly (0-100 test).

CYU_9

Media controller works correctly on CYU pages.

CYU_10

CYU_11

The certificate appears correctly and prints as visible on the screen with correct scores. Bookmarking works correctly on the CYU pages.

Fill In The Blanks (6)
FIB_1 Fill In The Blank questions work correctly.

FIB_2

Fill In The Blank questions work correctly.

FIB_3

Fill In The Blank questions work correctly. Fill In The Blank questions work correctly. Fill In The Blank questions work correctly. Fill In The Blank answers have consistent look and feel.

FIB_4

FIB_5

FIB_6

Match The Following (4)
MTF_1 Match The Following questions work correctly.

MTF_2 MTF_3

Match The Following questions work correctly. Match The Following questions work correctly.

MTF_4

Match The Following questions work correctly. Drag and Drop questions work correctly.

Drag and Drop (10)
DnD_1

DnD_2 DnD_3 DnD_4 DnD_5

Drag and Drop questions work correctly. Drag and Drop questions work correctly. Drag and Drop questions work correctly. Drag and Drop questions work correctly.

DnD_6 DnD_7

Drag and Drop questions work correctly. Drag and Drop questions work correctly. Drag and Drop questions work correctly. Drag and Drop questions work correctly.

DnD_8

DnD_9

DnD_10

Submit button for Drag and Drop questions works correctly.

Multiple Choice Question (MCQ) (3)
MCQ_1 MCQ_2 Multiple Choice (MC) questions use the correct template. Multiple Choice (MC) questions work correctly.

MCQ_3

Multiple Choice (MC) questions work correctly.

Multiple-Multiple Choice Question (MMCQ) (5)
MMCQ_1 MMCQ_2 MMCQ_3 Multiple Choice (MMC) questions use the correct template. Multiple Choice (MMC) questions work correctly. Multiple Choice (MMC) questions work correctly. Multiple Choice (MMC) questions work correctly.

MMCQ_4

MMCQ_5

Multiple Multiple Choice (MC) questions work correctly.

Ordering (2)
ORD_1 ORD_2 Order of the options is not a giveaaway. Ordering questions work correctly.

Sniffer Functionality (11)
SF_1 Check requirement of IE 6, 7 and 8 on Windows Check requirement of Firefox subversions on Windows and Mac Check requirement of Safari and Opera on Mac Check requirement of Shockwave Flash Player v8, 9, and 10.

SF_2

SF_3

SF_4

SF_5

Check requirement of Java Runtime.

SF_6

Requirement check result

SF_7

Bandwidth detection requirement

SF_8

Check for operating system - XP, Mac, Vista Message text if either one or all parameter fails

SF_9

SF_10

Check requirement of Windows Media Player .

SF_11

Check requirement of Quick Time on Mac.

Note: Check the file sizes if there are any such client specification.

Test Case Description

Expected Result

Actual Result

In the Course folder, check the course structure and file names against the client specifications. <Add client specs> In the Course folder, check the file names and extensions for uppercase characters and blank spaces.. <Add client specs, if any> (1) In the Course folder, check the files present. (2) Look for any .bak or .bk files (3) Look for any source files. <Add client specs, if any>

The file names are as per the client specs. (1) The file names do not have uppercase characters and blank spaces. (2) The file names are as per client specs, if any. (1) There should not be any extra files present in the folder. (2) There should not be any .bak or .bk files present in the folder. (3) There should not be any source files present in the folder. All basic files should be present.

In the Course folder, look for basic necessary files (e.g. imsmainifest.xml necessary for running the course on an LMS). <Add client specs, if any>

In the Course folder, check the attributes of the files The attributes of the files should be against the list provided by CT. correct as per the list provided by CT.

Click the launch/Start file for the course.

(1) The course should launch in a new window. (2) The window should not be blank.

(1) From the Home page/Course Home, click all the The module names match the ones on modules one-by-one. the Home page/Course Home. (2) Check the name of the module that you are taken to. (1) Click Next to navigate through the module/course. (2) Check the Page counter. (1) The course progresses to the next page and displays it. (2) Page numbers increase by 1. (3) The maximum page number shown should be the same as the actual number of pages in the module/course. (1) The course progresses to the previous page and displays it. (2) Page numbers decrease without any jumps or do not go into negative numbers.

(1) Click Previous to navigate through the module/course. (2) Check the Page counter.

(1) Go to the first page of the course / module. (2) Check the Previous button on this page. (3) Go to the last page of the course / module. (4) Check the Next button on this page. (1) Click Next very quickly without a pause to navigate through the module/course. (2) Check the Page counter. (3) Click Previous very quickly without a pause to navigate through the module/course. (4) Check the Page counter. Click Menu/Home/Course Map.

Buttons in both instances should be disabled or absent.

(1) The page counter should not throw up any number beyond the maximum number of pages. (2) The page counter should not throw up zero or negative number. Menu/Home/Course Map page opens. <in a new window> (1) Help window opens. (2) In case Help is not integrated in the current version, a pop-up with a relevant message is displayed. <in a new window> Resources page opens. <in a new window> Job Aids page opens. <in a new window> Glossary page opens. <in a new window> (1) If there is audio, the state is toggled. (2) If there is no audio, the link/button is disabled or a pop-up with a relevant message is displayed. Incase audio is not there in the current version.) <in a new window>

Click Help.

Click Resources. Click Job Aids. Click Glossary. Click Audio On/Off.

Click next/back while listening to the audio. Multiple Only one audio should play. audio should not be heard.

Click Exit.

(1) A message is displayed confirming that the learner wants to exit the course. (2) On clicking Yes, the course is closed. (3) On clicking No, the course remains open at the same page.

Click Bookmark. (1) Check the disabled state of the buttons / links. (2) Check the normal state of the buttons / links. (3) Check the rollover / mouse over state of the buttons / links. (1) Navigate through all the branch pages. (2) Click Next on the last branch page.

A popup asking to specify Book mark name is displayed. The state of the buttons / links should be consistent.

(1) The main page from which the branch started should be displayed. (2) Branch page numbering should be correct. (1) The appropriate component should open. (2) If the component is not integrated in the current version, an appropriate message should be displayed. (1) On launching the popup/demo the main page navigation should change to a paused state (2) On completion/closing of the popup/demo the main page navigation should either: The text in flash based courses should not disappear if we select the text and then drag the mouse.

Click all the global buttons.

(1) Navigate to the page (2) Launch the popup/demo from the main page (3) Check the navigation panel on the main page

(1) Select the text in flash based courses and then drag the mouse. Check that the text should not disappear on dragging it.

(1) Delete the cookies on your machine. (2) Run the entire course. (3) Click all the links.

(1) No error is encountered. (2) Pages/pop-ups from the link open in a new window. (3) The links change color when they are clicked. (4) In there is audio, the audio should stop when the pop-up opens. There are no links in the rollover / mouse over popup as the user will not be able to click them. (1) The links should be treated consistently for all states throughout the course. Standard treatment for the unvisited state is blue underline text. <Add client specs>

(1) Run the entire course. (2) Check for links in the rollover / mouse over popup. (1) Delete the cookies on your machine. (2) Run the entire course. (3) Note the unvisited state of the links. (4) Point the mouse on the link and note the rollover state of the link. (5) Click the link and note the visited state of the link.

(1) Run the entire course. (2) Check the hotspot placed on the links.

(1) The hotspots cover the button/link text completely including the spaces between the words.. (2) Hotspots can cover a negligible extra area. However, they should not be too large and should not overlap with other hotspots. (1) The cursor should change to the hand cursor when pointing to a link / hotspot. (2) The hand cursor should not appear on areas other than the link / hotspot.

(1) Run the entire course. (2) Place the cursor on the links / hotspots. (3) Randomly, place the cursor on the area around the link / hotspots and on other areas of the page.

(1) Run the entire course on the Liver Server. (2) Check for the hot area on each page of the course.

(1) The hotspots cover the button/link text completely including the spaces between the words in all the screen resolution. (refer to the client specs) (2) Hotspots can cover a negligible extra area. However, they should not be too large and should not overlap with other hotspots. The name on the title bar should match the course name. Pop-ups should be smaller than the course window. Pop-up windows should not be resizable. <Add client specs, if any> The name on the title bar should match the link text. Pop-up windows should be consistent in style.

(1) Launch the course. (2) Check the title bar of the course window. (1) Run the entire course. (2) Click the links to open popups. (3) Check the size of the pop-up. (1) Run the entire course. (2) Click the links to open popups. (3) Try and resize the pop-up window by dragging the bottom right corner of the window. (1) Run the entire course. (2) Click the links to open popups. (3) Check the title bar of the pop-up window. (1) Run the entire course. (2) Click the links to open popups. (3) Check the borders / styles of the pop-up window. (1) Run the entire course. (2) Click the links to open popups. (3) Check the position of the popups across pages. (1) Run the entire course. (2) Click the links to open popups. (3) Check that all pop-up windows have a Close button / link and appropriate closing instruction.

Pop-up windows should open at a fixed place, as far as possible.

(1) All pop-up windows should have a Close button/link. (2) Alternatively, there can be an instruction to use the X on the top right of the window.

(1) Run the entire course. (2) Click the links to open popups. (3) Click Next to move to the next page. (1) Run the entire course. (2) Click the links to open popups. (3) Check the position of the popup on the page.

Pop-up windows should close automatically on moving away from the page. <Add client specs, if any> Pop-up windows should not hide the link they open from or any overlap other text.

(1) Run the entire course. Any link / interaction beneath a pop-up (2) Click the links to open popups. should not be activated. (3)Try and perform any interactivity present beneath the pop-up. (1) Click close button on the popup. (2) while the popup is disappearing, click on the popup. (3) Check if the popup/screen freezes. (1) Navigate the entire course. (2) Check the progress bar and/or the page counter. Pop-ups should not freeze when a click action is performed while closing the same.

Check the status of each module.

(1) The progress bar shows the percentage completion visually. (2) The page numbers are incremented in proportion to the progress along the course. (1) The status for an unvisited module is Start. (2) The status for a partially completed module is Resume. (3) The status for a completed module is Review. (1) Only the subsequent section gets enabled after visiting a module. (1) The Assessment section gets enabled after visiting all modules. <This is design dependent, so refer to the design doc for accurate functionality>

(1) Navigate the course module-wise. (2) Check the status of the subsequent module after completing each module. (3) Check the status of the Assessment section after completing each module.

(1) Run the entire course. The focus areas should be completely (2) On pages where there is Tab functionality, press visible. If there is a scroll bar, the page the tab and check the focus areas. should scroll with the Tab action.

(1) Run the entire course. The tab order should go from left to (2) On pages where there is Tab functionality, press right and top to bottom. the tab and check the order of the focus areas. (1) Run the entire course. The tab should not highlight any blank (2) use the tab key, only hotareas/buttons should be areas on the screen, it should only highlighted. highlight hot area.

Check the Submit button without attempting the CYU.

The Submit button should be disabled before attempting the CYU.

Click the Submit button without attempting the CYU. An error message asking to attempt the CYU should be displayed. (optional) Check the Submit button after attempting the CYU. The Submit button should be enabled after attempting the CYU. (1) After attempting the CYU (e.g. clicking checkboxes in MMCQ, dragging options in Drag and Drop), undo the actions. (2) Check the Submit button after attempting the CYU. (1) Attempt the CYU incorrectly. (2) Attempt the CYU partially correctly. (3) Attempt the CYU correctly. (4) Try to attempt the CYU after the feedback is displayed. (1) The Submit button should be enabled on attempting the CYU. (2) The Submit button should be disabled on undoing the action. (1) Attempting the CYU incorrectly should display the incorrect feedback. (2) Attempting the CYU partially correctly should display the partially correct feedback. (3) Attempting the CYU correctly should display the correct feedback. (4) It should not be possible to attempt the CYU after the feedback is displayed. (1) The no. of attempts allowed should be as per design. (2) If the no. of attempts is not exhausted, the CYU should be reset.

(1) Attempt the CYU incorrectly till the time all attempts are exhausted. (2) Check the CYU state after an incorrect feedback to try the CYU again.

(1) Try to attempt the Quiz question multiple times. (1) Only 1 attempt should be allowed in (2) Attempt the Quiz question incorrectly. each Quiz question. (3) Attempt the Quiz question correctly. (2) No incorrect feedback should appear. (3) No correct feedback should appear. <Add client specs, if any>

(1) Attempt all the questions incorrectly (0 run). (2) Note the scores for individual questions (if applicable) and the overall quiz. (3) Attempt all the questions correctly (100 run). (4) Note the scores for individual questions (if applicable) and the overall quiz. (3) Attempt some questions correctly and others incorrectly. (4) Note the scores for individual questions (if applicable) and the overall quiz. (5) Check the format of the displayed score.

(1) Each individual question should be scored correctly. (2) Scoring for the 0 run should be 0%. (3) Scoring for the 100 run should be 100%. (4) Scoring for the mixed run should be correct. (5) The format of the score should be in percentage. <Add client specs, if any>

Where CYUs have more than 1 attempt: (1) Attempt the CYU incorrectly and display the incorrect feedback. (2) Move the media controller manually to the beginning.

(1) The audio should begin from the start. (2) The feedback box should disappear. (3) The correct / incorrect mark that appear against the options should disappear from the page.

Click the Print Certificate button (Check the name in The certificate should have correct the course.) format and data and should print correctly. (1) From the CYU page, exit the course. The CYU page should be reset on re(2) Relaunch the course. launch of the course. (3) Check the status of the CYU pages.

Fill in characters other than the correct answer. (e.g. for a text answer try filling in numbers or special characters.

(1) An error message asking to fill in the correct type of characters should be displayed. Or, (2) The entry of the incorrect type of characters should not be permitted. <Please include all the validation rules as part of test cases> It should not be possible to enter an unlimited number of characters.

Fill in an unlimited number of characters. (1) Some text (2) More text with minimal scroll (3) Lots of scroll Fill in answers with spaces / special characters embedded in them. For alphanumeric entries, fill in answers in uppercase, lowercase and mixed case. For numeric answers, fill in -ve, numbers, 0, and decimal values. Check the font style and size of the answers being entered.

Answers with spaces / special characters embedded in them should be marked incorrect. Answers should be marked correct irrespective of the casing. <Add client specs, if any> For numeric answers, all incorrect entries should give some response and not take the CYU in a loop. The font style and size of the answers should be same as displayed after the question is attempted.

Check the order of the options and the answers.

The order of the options should be jumbled (The correct answers should not be in front of the options). The spacing and alignment should be consistent. It should not be possible to match an option to another option.

Check the spacing and alignment of the options and the answers. Match the options to other options.

Check the lines that join the options to the answers. The lines should be straight and of consistent thickness. Check the order of the options and the drop areas. The order of the options should be jumbled (The correct drop areas should not be in front of the options). The spacing and alignment should be consistent.

Check the spacing and alignment of the options and the drop areas. Drag only one option to the correct drag area n times, where n = total number of drop areas. Drag the options out of the window.

The CYU should not be marked correct on this action. It should not be possible to drag the options out of the window. Drag the options to areas other than the drop areas (1) The option should move back to the or between the drop areas. drag area. It should not be possible to drag the options between the drop areas. (2) No feedback should be displayed. Drag multiple options on each other. (1) Attempt the CYU to display the feedback. (2) Try to move the options back to the drag area. Double-click the options. Dragging multiple options on each other should not be valid/allowed. It should not be possible to drag the options after feedback is displayed.

The options should remain in the drag areas and not be automatically placed in the drop areas. When there is more than 1 attempt defined, attempt It should be possible to drag the the CYU incorrectly by dragging an option to an options to incorrect drag areas and incorrect drag area. display the incorrect feedback. (1) Note the status of the Submit button before completing a correct drop action. (2) Attempt a correct drop action. (3) Take away this option from the drop area. (1) The Submit button should not be enabled before at least one correct drop action is complete. (2) The Submit button should get disabled when there are no options in the drop areas. <Reset button should be available for drag and drop options unless specified in the design.> Check the templates being used. Try to click the blank space after the text. The templates should be radio button templates. The blank space after the text should not be clickable.

Check all the MCQ pages.

(1) Should not present "All of the above" and/or "None of the above" options. If we cannot avoid, please get these options changed to "All of the listed" and/or "None of the listed" respectively.

Check the templates being used.

The templates should be checkbox templates. Try to click the blank space after the text. The blank space after the text should not be clickable. Click all the correct options and an incorrect option. Clicking all the correct options and an incorrect option should result in an incorrect attempt. (1) Attempt the CYU with all possible combinations (1) Clicking all the correct options and of correct and incorrect answers. an incorrect option should result in an (2) Vary the order of clicking the correct answer and incorrect attempt. attempt the CYU. (2) Varying the order of clicking the correct answer should not affect the correct answer. Check all the MMCQ pages. (1) Should not present "All of the above" and/or "None of the above" options. If we cannot avoid, please get these options changed to "All of the listed" and/or "None of the listed" respectively. Check the order of the options. In case the ordering is done by dragging numbers to placeholders, try to drag more than one number to one placeholder. The order of the options should be jumbled. It should not be possible to drag more than one number to one placeholder.

(1) Check IE 6 or greater is installed on the system. The status for requirement of IE 6 or (2) Run the course. greater should show "Passed". (1) Check Firefox is installed on the system. (2) Run the course. (1) Check Safari or Opera is installed on the system. (2) Run the course. (1) Check that Shockwave Flash Player v8 or greater is installed on the system. (2) Run the course. (1) Check that any version of Java Run-time is installed on the system. (2) Run the course. The status for requirement of Firefox with subversions should show "Passed". The status for requirement of Safari or Opera should show "Passed". The status for requirement of Flash player v8 or greater should show "Passed". The status for requirement of Java Runtime should show "Passed".

1) Run the course. (2) Check that the requirement check result (passed/failed status) is appearing only when it fails on any or all the parameters.

The requirement check result (passed/failed status) should appear only when it fails on any or all the parameter.

(3) Check that sniffer page should not appear when The sniffer page should not appear all the requirements are met. when all the requirements are met. (1) Run the course. (2) Check that sniffer is testing for Bandwidth. (1) Check that required operating system is installed on the system. (2) Run the course. (1) Run the course. (2) Check that if either one or all parameters fail then the following message should appear: This computer does not meet the minimum requirements to run this eLearning program. The requirement of specified Bandwidth should show "Passed". The status for requirement of operating system with XP, Mac, or Vista should show "Passed". When one or all parameters fail, the below stated message should appear onscreen: This computer does not meet the minimum requirements to run this eLearning program. The status for requirement of Windows media player should show "Passed".

(1) Check that Windows Media Player is installed on the system. (2) Run the course.

(1) Check that Quick Time is installed on the system. (2) Run the course.

The status for requirement of Quick Time on Mac should show "Passed".

ecification.

Testing Result (Pass/Fail)

Regression Result (Pass/Fail)

Test #

Test Case Summary

Test Case Description

Content Mapping Text Mapping (3)
TM_1 The content text maps with the storyboard. Map the course name, module names, topic names, page titles, onscreen text.

TM_2

The style of the text maps with the Check the bold, italics, underlined, style used in the storyboard. superscript, subscript parts of the text. Fonts and spacing are consistent. (1) Run the entire course. (To be done here if Read-through (2) Check the font and spacing being is not in the scope of testing) used in the content area.

TM_3

Graphic Mapping (8)
GM_1 The graphic text maps with the storyboard. Map the visuals with the visual description.

GM_2

Check for placeholders

GM_3

If there is a visual description in the graphic but graphics are not being delivered in this version, then there should be a graphic placeholder on the page. Check for consistency in graphics. If course has two states audio on/off in which audio on has animation and audio off static images, check on toggle if the graphics are following consistent style for e.g. border thickness. The style of the text in graphics maps with the style used in the storyboard. Fonts and spacing of the text in graphics are consistent. Check the bold, italics, underlined, superscript, subscript parts of the text in graphics. (1) Run the entire course. (2) Check the font and spacing being used in the graphic area. (1) View the graphic reference is full view. (2) Map with the graphic. (1) Check graphics for asterix. (2) asterix expansion should be present.

GM_4

GM_5

GM_6

The graphic must exactly map with the graphic reference.

GM_7

Asterisk point expansion should always be present.

GM_8

Color of the text is consistent.

(1) Run the entire course. (2) Check the color being used for the graphic text..

Note:

If the script is client-provided, do share your observation well-in-advance with the client so that all d Do not make changes in the course without first updating the scripts. If you are aware of any deviations and known issues, update the QC team before submitting the course

Expected Result

Actual Result

Testing Result (Pass/Fail)

Regression Result (Pass/Fail)

The text in the course should map with the Storyboard (SB).

The styles used in the course should map with the SB. The font and spacing should be consistent for similar text bodies in the content area. (e.g. Headings, examples, notes etc.)

The visual description and text in graphics should map with the SB.

Placeholders should be present in the absence of graphics.

graphic style should be consistent on toggle.

The styles used in the course should map with the SB. The font and spacing should be consistent for similar elements in the graphic area. (e.g. Headings, Labels, ) The graphic should map with the graphic reference.

all asterisk should be corresponded with expansions.

The color should be consistent for similar elements in the graphic area. (e.g. Headings, Labels, )

with the client so that all doubts are resolved prior to course construction.

efore submitting the course along with the reasons and the places of exception.

Test #

Test Case Summary

Audio Testing Audio Mapping (4)
AM_1 The audio maps with the audio script. (In case the audio is different from the Onscreen Text (OST)) The audio maps with the course. (In case the audio is same as the OST)

AM_2

AM_3

The pronunciation is as per the audio script / pronunciation word list.

AM_4

and' or 'or' is pronounced before the last bullet point in a list.

Audio Quality (7)
AQ_1 The voice of the same audio artist(s) is used.

AQ_2

The volume is consistent across the pages.

AQ_3

There are no background noises / echo.

AQ_4

The audio is clear and understandable.

AQ_5

The Rate of Speech (ROS) is consistent.

AQ_6

The audio does not end abruptly.

AQ_7

The pauses are appropriate.

Audio Synchronization (3)
AS_1 The audio is synchronized with the OST / animation. The audio is synchronized with the OST bullets starting position or when the particular phrase appears. <as per client specs> The audio does not run in a loop and ends properly.

AS_2

AS_3

Audio Controls (13)
AC_1 The global level Audio On / Off button works correctly.

AC_2

Correct tool-tips are displayed on the global level Audio On / Off , Pause, Play, Mute, Volume, Replay buttons.

AC_3

The audio stops playing on clicking any global button.

AC_4

The audio controls work correctly.

AC_5

The audio controls work correctly.

AC_6 AC_7

The audio controls work correctly. The audio controls work correctly.

AC_8 AC_9 AC_10

The audio controls work correctly. The audio controls work correctly. The audio controls work correctly.

AC_11

The audio controls work correctly.

AC_12

The audio controls are disabled where there is no audio. The audio controls are consistent.

AC_13

Note:

In some cases audio may not be verbatim as the audio script. In such cases, check if the intent of the a Pronunciations may vary for US or UK English. Check for pronunciation with the customer or on approp In some projects there are specific pronunciations used. In this case, check against the word list for sp In some projects, multiple characters / roles may be used across the course. The voice over for a char

Test Case Description

Expected Result

Actual Result

(1) Open the course in one window. (2) Open the audio script in another window. (3) Listen to the audio and map it with the audio script. (1) Complete the script mapping before proceeding with this test case. (2) Map the audio with the onscreen text. Note: The first step will be map the onscreen text/transcript with the storyboard. Once this is done, then proceed to the audio Vs. OST mapping. (1) Run the entire course. (2) Check the pronunciation of typical words against the ones provided in the audio script / pronunciation word list. (3) Check for the correct accent. E.g. if it is a US project the accent should be American and not British.

The audio in the course should map with the audio script.

The audio in the course should map with the text in the course.

(1) The pronunciation of all words should be as per the audio script / pronunciation word list. (2) The accent should map to the one asked by the client. (3) The slashes should not be read out while stating the path. (Again, please check the course standard.) and' or 'or' should be pronounced before the last bullet point in a list. The voice of the same audio artist(s) should be used across the course / series unless agreed upon by the customer to use different voices. The volume of the audio should be consistent within a page and across pages.

Check that 'and' or 'or' is pronounced before the last bullet point in a list.

(1) Run the entire course. (2) Check that the same voice(s) are used on each page and across pages. (3) If the course is one in a series, check that the other courses use the same voice(s). (1) Run the entire course. (2) Set the volume controls on your machine to a single setting. (3) Listen for the volume to be consistent on each page. and across pages. (1) Run the entire course. (2) Listen for any the background noises like echo or hissing sounds. (3) Listen for jerks / breaks in the audio.

There should be no background noise / echo / break in the audio.

(1) Run the entire course. (2) Listen for clarity of speech.

The audio should be clear and understandable.

(1) Run the entire course. (2) Check the speed of the audio on each page. (3) Check for speed of the audio across pages.

The audio should neither be too fast nor too slow.

The ideal ROS is between one hundred and eighty to two hundred words per minute. (1) Run the entire course. There should be a smooth ending (2) Check the audio does not end abruptly on each and audio should not end page. abruptly. (1) Run the entire course. The pauses in the audio should (2) Check for appropriate pauses at the following be appropriate. places: (a) When a sentence completes i.e. there is a There should not be any pause period. while reading an acronym. (b) When there is a comma. (c) Before the beginning of the a paragraph. (d) At the beginning of bullets or after lead-in lines. (e) In simulation, when there is an action to be performed. (3) Check for unnecessary pauses.

(1) Run the entire course. (2) Listen to the audio while watching the OST / animation. (1) Run the entire course. (2) Listen to the audio while watching the OST / animation.

The audio should be synchronized with the OST / animation. Map the bullet point with start position or when particular word is said as per client specs.

(1) Run the entire course. (2) Listen to the audio on each page. (3) On completion of the audio, wait for about 30 seconds.

(1) The audio should not restart by itself. (2) No junk characters or graphic should not appear on the screen.

(1) Run the entire course. (1) The audio should play on (2) On each page, click the Audio On / Off button 2- clicking the Audio On state. 3 times. (2) The audio should stop playing on clicking the Audio Off state. (1) Run the entire course. (2) On each page, click the audio controls 2-3 times. (1) The Audio On state should display the Audio On tool tip. (2) The buttons should display relevant tool tips.

(1) Run the entire course with the audio on. (2) On each page, click all the global buttons one by one. (3) Close the resultant popups.

(1) The audio should stop playing on clicking any global buttons. (2) The audio should either start from where it stopped or you may be require to click the Play button. The audio should start playing and the button should change to Pause. (1) The audio should pause and the button should change to Play. (2) On playing again, the audio plays from this point onwards. The audio should restart from the first frame. The audio should stop. On playing again, it restarts from the first frame. The volume of the audio should become zero. The volume of the audio should be adjusted. (1) The audio should run framewise. (2) There should not be any blank audio at the end. (3) The slider bar should not keep moving if the audio has stopped. (4) The slider bar should reach the end when the audio finishes. (5) The audio should not pause on moving the slider.

Click Play.

Click Pause.

Click Replay / Rewind. Click Stop.

Click Mute. Use the Volume button. Use the Slider.

(1) When the audio completes, click the Audio Off button. (2) Click Replay. (1) Run through the course. (2) Check for audio controls on all the pages. (1) Run through the course. (2) Check for audio controls on all the pages.

The button should not show the Mute state once the audio is on.

The audio controls should be disabled if there is no audio on a page. The audio controls should be consistent in look and feel across the pages.

udio script. In such cases, check if the intent of the audio maps with the audio script. eck for pronunciation with the customer or on appropriate language websites. E.g. m-w etc. s used. In this case, check against the word list for specific pronunciations. be used across the course. The voice over for a character / role should be consistent throughout the course.

Testing Result (Pass/Fail)

Regression Result (Pass/Fail)

t throughout the course.

Test #

Test Case Summary

Graphic Testing Graphic Clarity (3)
GC_1 Graphics text and elements are not blurred or patchy.

GC_2

Highlights are clear and consistent in thickness.

GC_3

Border style for the graphics is consistent.

Graphic Integrity (4)
GI_1 The graphic is sized correctly.

GI_2

No elements or text are truncated.

GI_3

Progressive graphics do not have shifts.

GI_4

Callouts do not hide any critical area of the graphic

Graphic Read-through (3)
GRT_1 Text in graphics is correct.

GRT_2

Graphics are labeled.

GRT_3

Graphic relevance with respect to tab.

Grab-based Graphics / Demos / Try-Its (9)
Grab_1 Grabs do not show unnecessary information.

Grab_2 Grab_3

There is no shift in the series of grabs used. Progressive grabs have correct highlights on folder and file names. The demo callouts are consistent across the frames.

Grab_4

Grab_5

Speed of the demo is appropriate to enable reading of all callouts.

Grab_6

The highlights and callouts point towards the correct option.

Grab_7

The demo callouts are synchronized with the audio. The audio does not run in a loop and ends properly.

Grab_8

Grab_9

Try-Its show appropriate feedback and the resultant screens are correct.

Animation Functionality (16)

Anim_1

The animation steps map with the storyboard.

Anim_2

A pre-loader is present at the beginning of the animation. Animation is not truncated.

Anim_3

Anim_4

There are no blank frames at the start or end of the animation. The animation does not run in a loop. The speed of the animation is appropriate.

Anim_5

Anim_6

Anim_7

Anim_8

The animation has proper user controls and they are working correctly. The animation has proper user controls and they are working correctly.

Anim_9

Anim_10

Anim_11

Anim_12

Anim_13

The animation has proper user controls and they are working correctly. The animation has proper user controls and they are working correctly. The animation has proper user controls and they are working correctly. The animation has proper user controls and they are working correctly. The animation has proper user controls and they are working correctly. There is no shift in the still graphics and animation (used in toggle mode).

Anim_14

Anim_15 Anim_16

Audio stops playing on stopping the animation. Right-click option on Flash elements is disabled or displays only appropriate options.

SWF Authentication (2)
SWF_AU_1 SWFs should not be self-running

SWF_AU_2

ANIMATION_Background specific: Background combinations should be defined and consistent throughout the course

Note: Graphic text may not be mapped if graphics are client-provided. However, the ideation is checked.

Test Case Description

Expected Result

Actual Result

(1) Run the entire course. (2) Check the graphics for haziness, broken lines, blurs. (3) Check the graphic for patches. (1) Run the entire course. (2) Check that the highlights used in the graphic are clear (4) Check that the highlights are consistent in thickness. (1) Run the entire course. (2) Check for the border style of all the graphics for consistency. (3) Check the font being used in the graphic area.

(1) The text and elements should not have haziness, broken lines, blurs. (2) There should be no patches on the graphic. (1) The highlights used in the graphic should be clear. (2) The highlights should be consistent in thickness. (1) Border style of the graphics should be consistent. (2) The font should be consistent for elements in the graphic area. (e.g. Headings, Labels, )

(1) Run the entire course. (2) Check the size of the graphics across the course. (if the course uses a template). (3) Check the graphic for squeezing or stretching. (1) Run the entire course. (2) Check the completeness of the elements and text. (1) Run the entire course. (2) Wherever there are progressive graphics, check the position of the base elements. (1) Display all the callouts for rollovers / links. (2) Check the position of the callouts.

(1) The graphic should be of uniform size(s). (2) There should be no stretching or squeezing.

All the elements and text should be visible and not truncated. The position of the base elements should not change from one page to next. The callouts should not hide any critical area of the graphic.

(1) Read through all the text in the graphics. (1) The graphic should map to (2) Check the text for spelling mistakes / the idea of the content in the text typos. area. (2) The text should not have any spelling mistakes / typos. Check the labels on the graphics. The graphics should have labels.

Check all the graphics within the tabs.

In case of tabbed interface, check that each tab is allocated with correct graphic. i.e. graphic content/relevance should map to the tab heading. (1) Grabs should not have developer / NIIT machine names. (2) Grabs should not have unnecessary window tiles. There should be no shift in the grabs. Progressive grabs should have correct highlights on folder and file names. (1) The instructions in the demo callouts should be written consistently. (2) The callout style should be consistent. (3) Any reference to the grab component should be highlighted and written in a consistent way in the callouts. (4) The style of the options in the callouts should map with those in the grab. The speed of the demo should be such that all the text of the callouts is read properly.

(1) Check the grabs for developer/NIIT machine names. (2) Check the taskbar in the grab for unnecessary window tiles. Check for the positioning of the grabs Check the blue highlights on the grabs.

(1) Run the demo. (2) Read-through the text of callouts for consistency and style.

(1) Run the demo. (2) Read-through the text of callouts at normal speed to ensure you are able to read the text of all callouts with ease. (1) Run the demo. (2) Check the highlights and the callout pointers.

(1) The callouts should point towards the correct options. (2) Appropriate button / option should be highlighted. (3) Correct sequence of grabs should be shown. (1) Run the demo. The demo callouts should be (2) Check for the synchronization of callouts synchronized with the audio (if with the audio. there is audio) (1) Run the demo. The demo should not run into a (2) Wait for 30 seconds after completion of loop and replay by itself. demo or till the slider bar reaches the end. (1) Run the Try-It. (2) Perform the interactions. Try-Its should show appropriate feedback as per the design and should be consistent across. (Add specific test cases as per the project guidelines)

Map the steps of the animation with the SB. The steps in the course should map with the SB.

Start the animation.

A pre-loader should be present at the beginning of the animation.

Run the animation to the end and wait for a The animation is complete and while. not truncated. There are no junk characters or screens appearing. Run the animation to the end and wait for a There should not be any blank while. frames at the start or end of the animation. (1) Run the animation to the end and wait The animation should not restart for a while. by itself. (2) Wait for about 30 seconds. (1) If there is no audio, read the captions / (1) The caption / text should be text. completely readable at a (2) If there is audio, hear the complete comfortable pace. audio. (2) The animation should be synchronized with the audio and be understandable. Click Play. The animation should start playing and the button should change to Pause. Click Pause. (1) The animation should pause and the button should change to Play. (2) On playing again, the animation plays from this point onwards. Click Replay / Rewind. The animation should restart from the first frame. Click Stop. The animation should stop. On playing again, it restarts from the first frame. The volume of the audio should become zero. The volume of the audio should be adjusted. (1) The animation should run frame-wise. (2) No blank screen should be displayed. There should be no shift in the 2 graphic elements.

Click Mute.

Use the Volume button.

Use the Slider.

Check the position of the still graphics and the animation.

On all animation pages, stop the animation. Audio should stop playing on stopping the animation. (1) Run the entire course. (1) If the right-click option is (2) On each Flash element, right-click. disabled, no pop-up is displayed. (3) If there is a right-click menu pop-up, (2) If a pop-up is displayed, only 2 note the options displayed on it. options, Settings and About are displayed.

(1) SWF should not be self-running (2) On clicking the SWF, an error message should be displayed. (3) That is DRM functionality should be enabled. Check the assets folder for animation and slides background.

(1) Click each individual SWF (2) Error message display: Unauthorized access, Permission denied (1) Background color combination should be consistent according to the SRS.

However, the ideation is checked.

Testing Result (Pass/Fail)

Regression Result (Pass/Fail)

Test #

Test Case Summary

Read-through Language (9)
LG_1 There are no spelling errors / typos in text and graphics.

LG_2

Correct punctuation is used.

LG_3

Hyphens are used appropriately.

LG_4

Em- / En- dashes are used appropriately.

LG_5

Casing of the text is correct.

LG_6

Terms are consistent.

LG_7

Article usage is correct.

LG_8

There are no cultural issues.

LG_9

The sentence does not read awkward.

Content Relevance (4)
CR_1 Content is relevant and appropriate to the topic.

CR_2

Content presented is in correct sequence and flow.

CR_3

There are no content vs. graphic mismatches.

CR_4

Graphic labels are appropriate and consistent.

Spacing (2)
SG_1 There are no extra or missing spaces. Paragraph breaks are appropriate.

SG_2

Instructional Design (7)

ID_1

Appropriate instruction text is used.

ID_2

Instruction text is consistent in look and feel. Words are not repeated. Bulleted text is parallel in sentence construction.

ID_3 ID_4

ID_5

Style of bullets should be correct and consistent.

ID_6

Use of acronyms is correct.

ID_7

Appropriate title is given to a popup.

Note:

Spellings may vary for US or UK English. Check for spellings on appropriate language websites. E.g. mIn some projects, there is a specific casing requirement. In such cases, please refer and map to the wo In some projects, a project-specific style guide is followed. Conduct a read-through keeping in mind th

Test Case Description

Expected Result

Actual Result

(1) Perform a spell check on the Storyboard (SB). (2) Read through the text / graphics in the course for spelling errors / typos. (1) Read through the entire text. (2) Check the end of all sentences for a period. (3) Check the end of all paragraph for a period. (4) Check the end of all question for a question mark. (5) Check the end of all lead-ins for a colon. (1) Read through the entire text. (2) Check that the hyphens are used as appropriate or as per the style guide. (1) Read through the entire text. (2) Check that the em- / en- dashes are used as appropriate or as per the style guide. (1) Read through the entire text. (2) Check the headings for correct casing. (3) Check that there is no running text in title case unless specified as part of the standard.

There should be no spelling errors / typos in the course.

(1) There should be appropriate punctuation marks at the end of sentences, paragraphs, questions, lead-ins. (2) There should be no duplicate punctuation marks.

The text should have correct hyphenations. The text should have correct dashes.

(1) Search for all instances of terms / terminologies / acronyms specified in the style guide / word list . (2) Check for consistency of casing and usage on each page and across pages.

(1) The headings should use correct casing. Words of 3 or less letters should be written in sentence case. (2) Normal running text should not have title cased words. (3) The casing should comply with the grammar rules. For e.g. proper nouns should always be title cased. (1) The casing of terms and terminologies should be correct and consistent across the pages. (2) The terms used in the course should be consistent for a page and across pages.

(1) Read through the entire text. The sentences should have (2) Check that the correct articles are correct article usage. present wherever appropriate. For e.g., articles should not be present before proper nouns.

(1) Read through the entire text. (2) Check for correct language usage in each frame and then across frames. For e.g., if a project requires UK English, then summarize should be written instead of summarize. the sentence formation is (1) Check that correct and does not read awkward. (2) Check that the subject verbs are in accordance with the grammar rules. (3) Check that multiple verbs are not used in the same sentence.

The language used should comply to the requirements / style guide.

The sentences should have correct sentence structure.

Check that the content is relevant to the topic that is being discussed on the page.

The content should be relevant to the topic that is being discussed.

(1) Check for the flow of content. For e.g. the introduction should come before summary. (2) Check the sequence of the content. (1) Map the graphic with the OST. (2) Check the content on the graphic completeness and clarity (not blurred). (3) Check that the text on the graphic is the same as mentioned on the screen. (1) Check the presence of labels for each graphic. (2) Map the description on the labels with the graphic. (3) Check the sequence of labels. (4) Check the labels for consistent naming convention / style.

The content should have the correct flow. The content should be in logical sequence. (1) The graphic should convey the same message and be relevant to the OST.

(1) Labels should be present for all graphics. (2) The labels should explain what the graphic is. There should be no mismatch between the label and the graphic. (3) The sequence of the labels should be correct. E.g., if the first graphic is labeled image 1.1, the next one should be 1.2. (4) Labels should be use a consistent naming convention / style. There should be no extra or missing spaces in the course. There should be an appropriate line space between paragraphs.

Check for spaces in the script/course.

(1) There should be a line space after the end of each paragraph. (2) Check that the two paragraphs are not merged into one.

(1) Check for the presence of instruction text wherever the user is required to perform an action. (2) Perform the required action using the instruction text.

(1) Instruction text should be present wherever required and be clear enough for the user to learn easily. (2) Instruction text is appropriate, clear, and complete to enable the user to perform the required action. (1) Run the entire course. Instruction text should be (2) Check all the instruction text across consistent in wording, pages. presentation and style. Check for redundant word usage on each There should be no redundant / screen. repeated words. Check for parallelism in bulleted text. Bulleted text should be parallel in E.g. What if the test criterion in the Methods sentence construction. page differs from that in the Standard? What if information is missing in the datasheet? (1) Run the entire course. (2) Check the bullets used across pages. (1) Bullet style should be consistent. (2) Any procedure or sequence of events should have numbered list. (1) Run the entire course. (1) Only the first instance of an (2) Check the first instance and subsequent acronym should be expanded. usage of an acronym <across pages / (2) The acronym should be modules>. introduced such that the (3) Check the first instance of the acronym. expansion should be followed by the acronym in parenthesis. E.g. Quality Control (QC) (3) All terms with acronyms should be title cased. (1) Run the entire course. The popups should have a title / (2) On pages with multiple links, click all the heading. This is to enable the links. users to locate which link out of the several on the page is being explained.

for spellings on appropriate language websites. E.g. m-w etc. uirement. In such cases, please refer and map to the word list. e is followed. Conduct a read-through keeping in mind the standard guidelines.

Testing Result (Pass/Fail)

Regression Result (Pass/Fail)

Test #

Test Case Summary

Layout Testing Layout (5)
LT_1 Layout is not awkward / odd.

LT_2

There is consistency in style and layout within and across pages.

LT_3

There are no shifts in the elements and text while moving from one page to the next. Text in boxes is not touching the borders. The text on buttons / labels is centeraligned.

LT_4

LT_5

Scrollbars (4)
SB_1 Scrollbars appear only where their use is necessary.

SB_2

Scrollbars do not leave large white spaces at the bottom of the page.

SB_3

Scrollbars work correctly.

SB_4

Scrollbars function correctly.

Note:

Test Case Description

Expected Result

Actual Result

(1) Run the entire course. (2) Check for text running out of the screen or getting truncated on each page. (3) Check that the graphics and text are not overlapping on each page. (4) Check that there are no large white spaces on each page.

(1) The text is not running out of the screen or truncated on any page. (2) There should be no overlap of graphics and text on any page. (3) There should be no large white spaces on any page. (4) There should be no disproportionate or odd-looking layouts (1) The margins should be consistent across the pages. (2) The position of the graphics should be consistent across the pages. (3) The bullets should be correctly and consistently indented as per their hierarchy on each page and across pages.

(1) Run the entire course. (2) Check the margins across the pages. (3) Check the position of the graphics across the pages. (4) Check the indentation of the bullets on each page and across pages. (5) Check the alignment of the text in callouts on each page

(1) Run the entire course. (2) Check the position of the course name, module name, topic name, page titles, onscreen text, and visuals. (1) Run the entire course. (2) Check all the text enclosed in boxes.

There should not be any shift between the elements and text across pages. Text in boxes should not touch the borders.

(1) Run the entire course. The text on buttons, labels should (2) Check all the text on buttons and labels. be center-aligned.

(1) Run the entire course. (2) Check all the pages for scrollbars.

(1) Scrollbars should appear on pages where text is not fully visible. (2) Scrollbars should not appear on pages where text is fully visible. (3) Vertical scrollbars are permissible. (4) Horizontal scroll bars should be avoided.

(1) Run the entire course. (2) Check all the pages with scrollbars. (3) Drag the scrollbar down on each page. (4) Check the white space after the text at the bottom of the page. (5) Check the white space at the bottom of the page across pages. (1) Run the entire course. (2) Check all the pages with scrollbars. (3) Drag the scrollbar down on each page, go to the previous page, come back to the original page. (1) Run the entire course. (2) Check all the pages with scrollbars. (3) Check the functionality of the scrollbar by dragging the slider and by using the up and down arrows. 4) Also check by clicking on the white space in the scroll bar.

(1) There should not be large white space at the bottom of the page. (2) The white space at the bottom of the page should be consistent across the pages.

(1) Scrollbars should appear only where their use is necessary (2) The position of the scrollbar should be initialized when moving between pages. 1) Scroll bars should function correctly.

Testing Result (Pass/Fail)

Regression Result (Pass/Fail)

Test #

Test Case Summary

Platform Testing File Naming Convention (1) Formatting (8) Functionality (6)

Note:

Ensure that the course is tested in the primary OS/Browser combination before releasing the course to Specific requirements for multiple OS/Browser combinations need to be captured and tested.

Multiplatform Testing Checklist

Test Case Description

Expected Result

Actual Result

Browser combination before releasing the course to QC. binations need to be captured and tested.

Testing Result (Pass/Fail)

Regression Result (Pass/Fail)

Test #

Test Case Summary

LMS Testing

SCORM Testing
Bookmarking (4) Completion Status (2)
CS_1 (scenario 1 If LMS access is Course completion is tracked available) correctly on LMS.

CS_1 (scenario 1 If LMS access is (1) Run the ADL test suite on the not available) course. (2) Visit some pages in the course and exit the course through the Exit button or (close).

CS_2

Course completion is tracked correctly on standalone version. (For CogArts courses)

AICC Testing
Step_1

Security Risk Caching Security (6) Confidentiality (1)

Test Case Description

Expected Result

Actual Result

(1) Check the status before launching the course. (2) Launch the course on LMS. (3) Go through all the main and branch pages. (4) Check the completion status. (1) The ADL test suite report should be ok for all parameters. Following ADL test suite reports need to be generated: - Sharable Content Object (SCO) Run-Time Environment Conformance Test - Meta-data Conformance Test or --------------------------------------------- Content Package Conformance Test

(1) Before starting the lesson, the completion status should show Not Started / Not complete (check the LMS terminology) (2) After visiting all the pages the status should change to Complete. In report as per the specification please check for: (1) LMS Execution State (initialize and Finish) (2) LMS (GetValue(), SetValue() and Commit()) (3) At least Check for Data Model Support, (session_time, lesson_status "Not Attempted, Incomplete, completed/passed, score.raw (in case of assessment required)) Refer to the attached document for details.

Adl_testSupport.doc

(1) Launch the course. (2) Once the course is launched, press Alt+Shift+D. --> Write "belushi" in the prompt. --> Click on the link 'Show current State' appearing at the bottom right of the course --> a window appears with all the details.

Testing Result (Pass/Fail)

Regression Result (Pass/Fail)

Test #

Test Case Summary

Performance Testing Response Time (1)
RT_1 Response Time meets client specifications.

Note:

Performance testing is performed using various tools. The choice of a tool will depend on the technolo For example, for conducting a performance test on HTML pages, we use Load runner, Silk Performer For conducting a performance test on response time for flash based applications, simulator (XAT) and Test cases will be added based on inputs from LT team.

Test Case Description

Expected Result

Actual Result

(1) Run the course in a simulator. E.g., XAT. (2) Note how long the system takes to complete a requested task or group of tasks.

Note down the observations to map to your SLAs.

ools. The choice of a tool will depend on the technology used to develop the courseware. t on HTML pages, we use Load runner, Silk Performer etc.

ime for flash based applications, simulator (XAT) and fiddler can be used

Testing Result (Pass/Fail)

Regression Result (Pass/Fail)

Test #

Test Case Summary

ADA Compliance ADA Compliance (5)
ADA_1 Every image, Java applet, Flash file, video file, audio file, plug-in, etc. that conveys content has an equivalent Alt description or text description, or is described in the adjacent text. Complex graphics (graphs, charts, etc.) are accompanied by detailed text descriptions or through a description in the body of the page. Row and column headers should be identified for data tables through Screen Reader tool. E.g. Jaws Reader. The reader tool should be able to read the text as intended.

ADA_2

ADA_3

ADA_4

ADA_5

The Alt text is closed within double/single quotes. If the enclosed text has apostrophe anywhere then care should be taken with starting and closing quotes.

Note:

Please refer to project-specific requirements for ADA compliance. This is not the complete list. The requirements vary from project to project. However, this covers the

Test Case Description

Expected Result

Actual Result

(1) Run the course Alt description or text description (2) Point your mouse over images, flash should be there for images, flash files files, video files to view the text description. etc.

(1) Run the course (2) Point your mouse over graphics for detailed descriptions.

Alt description or text description should appear for all graphics. The description should map with the text provided in the storyboard. Rows and column headers should be appropriate in alt text. In case there are alt text issues, you need to correct them. The reader will read the text as appearing in the course. Any issues encountered need to be corrected. e.g. World War II > If in simple text the reader will read as “World War i i”. For reader to read as intended this should be converted to image with alt text provided. The alt text should be closed within double/single quotes. If the enclosed text has apostrophe anywhere then care should be taken with starting and closing quotes.

Run the course through a screen reader tool (Jaws Reader).

Run the course through screen reader tool (Jaws Reader).

Check the way alt text is written for all the components.

ADA compliance. vary from project to project. However, this covers the basic ADA compliance functionality.

Testing Result (Pass/Fail)

Regression Result (Pass/Fail)

Test #

Test Case Summary

Global Elements Opening Animation / Splash Screen(3)
Open_1 The opening animation runs correctly.

Open_2

The opening animation displays the correct course name.

Open_3

The Start button functions correctly.

Help (7)
Help_1 Help_2 Help runs correctly. Grabs used in Help are correct.

Help_3

Icons / buttons used in Help are correct. Description for the icons / buttons used in Help are correct.

Help_4

Help_5

Rollovers / Hotspots are correctly placed over the components.

Help_6

Help_7

Numbered labeling of the components on the help screen is correct. Numbered labels are described correctly.

Glossary (8)
Gloss_1 Gloss_2 Glossary runs correctly. The letters should be in an alphabetical order. Only the populated letters are clickable.

Gloss_3

Gloss_4

The order of the terms is correct.

Gloss_5 Gloss_6

The casing of the terms is consistent. The Glossary terms have the correct treatment.

Gloss_7

The correct description is displayed on clicking the Glossary term from the course. All the Glossary terms are present at least once in the course.

Gloss_8

Notes (6)
Notes_1 Notes button opens a blank notepad. The cursor on notepad should be at the first line. On clicking the save button whatever is written in the notepad should be saved.

Notes_2 Notes_3

Notes_4

In notepad there should be a character limit.

Notes_5

On clicking the print button the content in notepad should be printed.

Notes_6

Clicking help in notepad should open notepad specific help.

Print (6)
Print_1 print button prints the onscreen elements

Print_2

No text/graphics should truncate/overlap. Printer setting should be mentioned if different from the default. No global elements/buttons should be part of print layout. The print out should consist of the name of the course and the Page number. The print out should be clear and easily readable. Check the Printouts in the following three scenarios: 1. Just few lines of text 2. Immediately when the scroll appears 3. Lot of text with good scrolling

Print_3

Print_4

Print_5

Print_6

Print_7

Search Criteria (7)

Ser_1_a

Launch Search window

Ser_1_b

Launch Search window

Ser_2

check basic Search functionality

Ser_2a

Ser_2b Ser_2c Ser_2d

Note:

In case of any global buttons esp. in flash-based courses, ask the PM if there is just one are multiple files please check from all locations.

Test Case Description

Expected Result

Actual Result

(1) Launch the course. (2) Check the course window.

(1) Check the course name. (2) Check any other captions.

(1) Delete the cookies. (2) Launch the course. (3) Check the Start button. (4) Click the Start button and navigate through the course. (5) Exit and relaunch the course. (6) Check the Start button.

(1) The screen should not be blank. (2) The opening animation should run without any delay. (3) If there are any delays, the first frame should display a preloader. (1) The course name should be correct. (2) The captions should be correct. (1) The button should be 'Start' when launching the course for the first time. (2) The first page of the course should be displayed on clicking 'Start'. (3) The button should change to 'Resume' on subsequent launches. Help opens in a new window. (1) For global Help, the grabs should be of the course. (2) For page-specific help, grabs used in Help should match the page from where Help was opened. The icons / buttons used in Help should match the ones used in the actual course.

From the course window, click the Help button. (1) For global help, open Help from any page. (2) For page-specific help, open Help on each page. (3) Match the grab in the Help window with the page from where Help was opened. Match the icons / buttons with the ones used in the actual course.

Match the description of the icons / buttons The description of the icons / with the actual functioning of the buttons / buttons should match the actual icons. functioning of the buttons / icons. Check the rollover / hotspot areas used in the Help window. (1) The hotspots cover the components completely. (2) Hotspots can cover a negligible extra area. However, they should not be too large and should not overlap with other hotspots.

Check the sequence of the numbered labels used to describe components. Match the numbered labels with the descriptions.

There should not be any missing numbers in the sequence of labels. (1) The descriptions should be present for all labels. (2) The descriptions should match the functioning of the labeled component.

From the course window, click the Glossary Glossary should open in a new button. window. Check the order of the letters at the top. The terms should be arranged in an alphabetical order. Click all the letters at the top. (1) Letters that have corresponding terms should be clickable and display the terms. (2) Letters that do not have corresponding terms should be either disabled or display a message conveying that the terms are not available. The terms should be arranged in an alphabetical order as used in a dictionary. All the terms under each letter should use consistent casing. The Glossary term should have the same treatment for visited as well as unvisited states. The correct description should be displayed on clicking the Glossary term from the course.

Check the order of the terms under each letter. Check the casing of the terms under each letter. (1) Run the course. (2) Check all the Glossary terms.

(1) Run the course. (2) Click all the Glossary terms.

Search for all Glossary terms in the course. All the Glossary terms should be present at least once in the course. On clicking the notes button for the first time a blank notepad should appear in a pop-up window. check for the cursor to be present at the first line. 1. write notes in the notepad. 2. click save. 3. exit notepad reopen notepad - the text that you typed should be intact. a blank notepad should open.

the cursor should be present at the first line. the text saved should be intact on opening notepad again.

Type text until you reach the character limit once the limit is crossed a prompt should appear saying that the character limit has been reached and no more characters can be added. Click the print button -> the printout should print only the text in notepad not any other information or buttons. The complete text including the hidden part should appear in the printout.

user should be prompted that no more characters can be entered when the limit is reached.

printout should print only the text in the notepad and that should be clear and readable.

On taking the printout of the page the complete text including the Check that the text should not be truncated part not visible in the page(i.e. in or overlapped. case of scroll bars) should be visible. click help icon on notepad and the help for the same should appear explaining the buttons in the notes popup window and what they intend to do. On clicking the print button the printer dialogue box should appear and on clicking OK the onscreen text and graphic should be printed. in the print out check for overlapping or truncation of text/graphics. Help icon in notepad should open notepad specific help.

All elements onscreen should be printed.

the print out should have all elements without anything getting truncated or overlapped. in case the print out needs to be taken in in case of setting different from the landscape mode the same should be default instruction text should present in the instruction text. state the settings required. Check that the global buttons do not appear The print out should not have any in the print document. global buttons appearing on it. Check that the print out should consist of the name of the course and the page number. Ensure that the print out should be clear and visible, there should be nothing appearing in the background. Put the text in the print area as per the three scenarios mentioned --> Print and check. The course name and the Page Number should appear in the Print out. The printout should not consist of any extra or unrequired information. The printout should be complete and readable. There should be no truncation/overlap.

1. Click on search link and see if editable search window is launching 2. If course is accessible then repeat this exercise with key combination (Ctrl + S) Repeated the entire exercise after closing the search window If more the then one options for exiting Search is available then repeat the entire exercise with all possible combination.

Search Window/Tab should be available to user without throwing any JavaScript error

Search Window/Tab should be available to user without throwing any JavaScript error

1. Specify the search criteria in the editable Validate the result Search box <parameter> 2. Press <find next> or <Go> Specify any search criteria in the editable box and clean the box Specify search criteria in the editable box with Special char, wildcard combo Check the char limit of editable search window User should be able to specify any type of search criteria (Char, Alpha-numeric, numeric)

<any button> which is available there to proceed should not remain active Should throw err msg if exactly doesn’t map

tons esp. in flash-based courses, ask the PM if there is just one file being used in the backend or not. If there check from all locations.

Testing Result (Pass/Fail)

Regression Result (Pass/Fail)

Test #

Test Case Summary

PPT_Print(5)
PPT_Print_1 Check for Images.

PPT_Print_2

Check for Graphic.

PPT_Print_3

Check for Print version.

PPT_Print_4

Check for Gray Scale.

PPT_Print_5

Check for Paper size.

Projection(10)
Projection_1 Monitor resolution.

Projection_2

Color

Projection_3 Projection_4

Backgrond color. Reverse Contrast.

Projection_5 Projection_6

Ambient Lighting. Consistent usage of fonts.

Projection_7

Check for images consistency.

Projection_8 Projection_9 Projection_10

Links Slide masters Title master Font

Basic Windows(13)
Basic Windows_1

Basic Windows_2

Alt Text and images

Basic Windows_3

Shifts

Basic Windows_4

Layout

Basic Windows_5

Onscreen text

Basic Windows_6 Basic Windows_7

Background Color combination

Basic Windows_8 Basic Windows_9

Tables Illustrations

Basic Windows_10

Bullet points

Basic Windows_11 Basic Windows_12

Onscreen text - Paragraphs Graphics

Basic Windows_13

Animation

Test Case Description

Expected Result

Check for Image DPI(Depth per resolution). Images DPI should be 96 x 96. (72dpi also works fine, if the target is only projection or slide printouts, and not printing for mass distribution. The delivery mechanism is important.) Check for graphic type. It should be vector graphic i.e. when we zoom in the graphic, it should not dither. Check the print out. If the print is intended to be colored, take a print out and check that the colors appear as intended and are not dull or stretched. (recommend to use a full color in color offset printer as checkpoint and testing.) Check the same for black and white print out. Always take a print out to check positioning and color.

Check for gray scale constraints.

Check paper size.

There should be no grey scale areas. i.e. there should be no shadows or <as per design specs> Paper size should be A4 or more or <as per client specs>

Check for monitor resolution.

Universal fonts like arial, times new roman or verdana should be used for onscreen text. Do not use light colors on PPTs as it dulls out the content. However the fonts/content should also be in high contrast. or <as per design specs> Background should be light in color. or <as per design specs> Avoid reverse contrast as it dulls out the PPTs content. or <as per design specs> The PPTs should be tested in ambient lighting. All header/footer/content font should be having same family and similar size.(especially when content is more)

Check for light colors.

Check for background/foreground color. Avoid reverse contrast.

Check the PPTs in ambient lighting. Check the font in header/footer/content.

Consistent usage of images with logical deviation of style.

All images used will have a logical manner of usage, style (for example same slide may have a 300x200 image and 300x300 image, but consistent in proportion) All links working as per content Clean Slide masters Clean Title master Font style should be readable and consistent throughout. Content text should not be smaller than Verdana 24 point. Small fonts are allowed only for the footer. Universal fonts like arial, times new roman or verdana should be used for onscreen text. Alt text and images should be placed within 95% of the PowerPoint slide. Refer to the embedded file.
ppt.bmp

Links are checked. Clean slide masters Clean Title master Check for font style.

Check for Alt Text and images

Check for shifts in headings, subheading, logos Check for: - Margins, fonts, font size, and colors - Lines, boxes, borders, and open spaces

Headings, subheadings, and logos should show up in the same spot on each slide - Margins, fonts, font size, and colors should be consistent with graphics located in the same general position on each frame - Lines, boxes, borders, and open spaces should be consistent All Caps should not be used except for acronyms Italics shoud only be used for: - Quotes - Highlighting thoughts or ideas - Books, Journals or Magazine titles Background used on all slides should be the same. The result displayed by the tool should be pass. Dark slides with light colored text should be used for large hall events. For print and paper, dark text on a light background should be used. Tables should be placed on a separate slide. The illustrations should be relevant to the content and should not distract.

Check for Capitalization and Italicization

Check the background colour and style Check the color combination of the background and the text using Color Contrast Analyzer tool

Check the tables Check the illustrations

Check the bullet points

- The bullet points should not exceed more than two lines. - There should not be more than five (+/-2) bullets per slide - There should not be more than five (+/-2) words per bullet - The bullets should be left justified and not center aligned Large block paragraphs should not be used on the slides. Graphics should not be center aligned. They should be off-center to provide room for text. Left placement leads the eye to the text.

Check for paragraphs Check for alignment of graphics

Check the animation

The same animation style should be used throughout the animation

Testing Result Actual Result (Pass/Fail)

Regression Result (Pass/Fail)

For Dev team only

For Dev team only

For Dev team only For Dev team only

Sponsor Documents

Or use your account on DocShare.tips

Hide

Forgot your password?

Or register your new account on DocShare.tips

Hide

Lost your password? Please enter your email address. You will receive a link to create a new password.

Back to log-in

Close