Specific Field Tests

Tester's Screen Validation Checklist

2.8. Specific Field Tests
2.8.1. Date Field Checks
2.8.2. Numeric Fields
2.8.3. Alpha Field Checks

Specific Field Tests

Date Field Checks

Assure that leap years are validated correctly & do not

cause errors/miscalculations

Assure that month code 00 and 13 are validated correctly & do not

cause errors/miscalculations

Assure that 00 and 13 are reported as errors

Assure that day values 00 and 32 are validated correctly & do not cause errors/miscalculations

Assure that Feb. 28, 29, 30 are validated correctly & do not cause errors/ miscalculations

Assure that Feb. 30 is reported as an error

Assure that century change is validated correctly & does not cause errors/ miscalculations

Assure that out of cycle dates are validated correctly & do not cause errors/miscalculations

Numeric Fields

Assure that lowest and highest values are handled correctly

Assure that invalid values are logged and reported

Assure that valid values are handles by the correct procedure

Assure that numeric fields with a blank in position 1 are processed or reported as an error

Assure that fields with a blank in the last position are processed or reported as an error an error

Assure that both + and - values are correctly processed

Assure that division by zero does not occur

Include value zero in all calculations

Include at least one in-range value

Include maximum and minimum range values

Include out of range values above the maximum and below the minimum

Assure that upper and lower values in ranges are handled correctly

Alpha Field Checks

Use blank and non-blank data

Include lowest and highest values

Include invalid characters & symbols

Include valid characters

Include data items with first position blank

Include data items with last position blank

Web usability evaluation/Testing

U should check basic things such as:

Layout- Does your site look credible to your end users?

Site Navigation and Architecture -How the information is organized on your site including site categories, sub categories, titles, subtitles and labeling in relation to your end users

Information retrieval- Are your end users able to find information that they want with ease?

Site Loading speeds - Evaluation of page download time to find out it your users are waiting too long for pages to appear

Learning Management System LMS

Learning Management System (or LMS) is a term used to describe software tools designed to manage user learning interventions.

The characteristics shared by both types of LMSs include:

* Manage users, roles, courses, instructors, and facilities and generate reports
* Course calendar
* Learner messaging and notifications
* Assessment/testing capable of handling student pre/post testing
* Display scores and transcripts
* Grading of coursework and roster processing, including waitlisting
* Web-based or blended course delivery

Basic stuff about DLL for testers

Dynamic-Link Libraries

A dynamic-link library (DLL) is a module that contain functions and data that can be used by another module (application or DLL).


A DLL can define two kinds of functions: exported and internal. The exported functions are intended to be called by other modules, as well as from within the DLL where they are defined. Internal functions are typically intended to be called only from within the DLL where they are defined. Although a DLL can export data, its data is generally used only by its functions. However, there is nothing to prevent another module from reading or writing that address.

DLLs provide a way to modularize applications so that their functionality can be updated and reused more easily. DLLs also help reduce memory overhead when several applications use the same functionality at the same time, because although each application receives its own copy of the DLL data, the applications share the DLL code.

The Windows application programming interface (API) is implemented as a set of dynamic-link libraries, so any process that uses the Windows API uses dynamic linking.

About SCORM for E-learning Testers

SCORM 1.0

The original version. Proof of concept only. Introduced the notion of Shareable Content Object (SCO) and the API model in which the burden of managing communication latency across the Internet is handled by the runtime environment, not by the content objects.

SCORM 1.1

The first production version. Used a Course Structure Format XML file based on the AICC specifications to describe content structure, but lacked a robust packaging manifest and support for metadata. Quickly abandoned in favor of SCORM 1.2.

SCORM 1.2

The first version with a real conformance test in the form of a test suite. Uses IMS Content Packaging specification with full content manifest and support for metadata describing the course. Also allows optional detailed metadata tagging of the content objects and assets described in the manifest. Usually works well; both the delivery system and content pass the test suite without cheating, but lacks sequencing and some other desirable features. No longer maintained or supported by ADL.

SCORM 2004

The current version. Based on new IEEE standards for API and content object-to-runtime environment communication, with many ambiguities of previous versions resolved. Includes ability to specify adaptive sequencing of activities that use the content objects. Includes ability to share and use information about success status for multiple learning objectives or competencies across content objects and across courses for the same learner within the same learning management system. A more robust test suite helps ensure good interoperability.

SCORM 2004 Editions

* 1st Edition (January 2004) — versioning changed so each book could be independently maintained
* 2nd Edition (July 2004) — improvements regarding Content Aggregation Model and Run-Time Environment
* 3rd Edition (October 2006) — clarification of various conformance requirements and of the interaction between content objects and the runtime environment for sequencing; some new conformance requirements to improve interoperability.

Introduction

Here I am! starting a blog.. to just keep track of my thoughts and progress in life.

I wish to share my knowledge and simultaneously gain some popularity. :)

Hopefully I get some good hits and Google pays me a million.. : p