You are here: Development Standards > Quality Assurance > Design Phase > Beta Stage

# Beta Stage

The purpose of beta testing is to completely test all functional and technical aspects of the software and to locate software bugs and verify the corrections to those bugs. A good mix of beta sites is necessary to ensure a variety of testing scenarios. Each participant in the beta testing program attends a tele-training session, and external sites complete an evaluation guide about each application by a deadline. Sites receive updated software and user’s guides as needed.

Tests are easy to execute and manage if performed in logical segments. QA testing includes some or all of these tests:

___ Review Paperwork

___ review older version bug reports

___ review application-specific checklists

___ review previous test plan documents

___ Create New Test Plan

___ Perform Fresh Install (first round)

___ test standalone functionality

___ interface other applications

___ enter each level of program using each menu without receiving errors

___ exit from each level without receiving errors

___ verify all functions work at a basic level

___ print reports to the screen, a file, print preview, and a printer

___ ensure HLE areas function according to standards

___ ensure screen commands work according to standards

___ complete posts in summary and detail

___ ensure master file data validity

___ test file conversion upgrades from previous to current version

___ Perform Consecutive-Round Test

___ perform Windows/DOS file compare from previous round

___ analyze a list of the program changes

___ install media

___ test for regression (spot-check to ensure fixes don’t create other issues)

___ test user interface (such as commands, windows, and consistency)

___ test keys (command and in-field edit)

___ test all functions

___ ensure screen and report naming conventions were followed

___ test windows (help, inquiry and maintenance) and command bars

___ test messages (both errors and warnings)

___ test reports for accuracy, design, and naming conventions

___ test GENERAL Report Writer and ODBC for new or changed files

___ analyze sample data for accuracy, appropriateness, and completeness

___ test forms (ensure program prints correctly on forms)

___ Perform Systems Test

___ test menu selections, functions, and aspects of the application

___ test options and interfaces

___ multiuser tests (file locks and record locks function appropriately)

___ Review the User Guide

___ Perform Minisystems Test

___ include one or more accounting periods

___ focus on different functions or features of the application

___ use steps for consecutive round testing

___ Perform Acceptance Test (Beta through Controlled Release) Program

QA has standard checklists; test-case instructions; test standards for testing such things as reports, screen functionality, menus, GENERAL Report Writer data files, sample data, data dictionaries, installation, upgrades and data conversion; and paperwork review. Here are the test plan setup steps:

1. Copy your master test plan into an area where you can modify it.
2. Begin test plan development as if you were a user setting up the application.
3. Read the application specifications to select from the master test plan the test options and steps that are applicable.
4. Create the test plan based on option settings in this order: File Maintenance, Daily Work, Reports, Posts, and then Interfacing application(s).