©2012-2015 Confidential and Proprietary
Clear Ballot GroupClearAccess 1.0
Test Plan
Part Number: 100069-10001
Copyright © 2012-2015, Clear Ballot Group
All rights reserved.
This document contains proprietary and confidential information, consisting of trade secrets of a technical and/or commercial nature. The recipient may not share, copy, or reproduce its contents without express written permission from Clear Ballot Group.
Ballot Resolver, ClearAudit, Clear Ballot, ClearCount, ClearData, Clear Design, ClearVote, Image-to-Ballot Traceability, MatchPoint, ScanServer, ScanStation, Speed Accuracy Transparency, Visual Verification, Visualization of Voter Intent, and Vote Visualization are trademarks of the Clear Ballot Group.
ScandAll PRO is a trademark of FUJITSU LIMITED. All rights reserved.
Other product and company names mentioned herein are the property of their respective owners.
The Clear Ballot Group
7 Water Street, Suite Seven
Boston, MA 02109
(857) 250-4957
Document History
Date / Author / Description / Version8/10/2015 / Deborah Block-Schwenk / ClearAccess Test Plan / 1.0
Contents
Title 1.0Test Plan1
©2012-2015 Confidential and Proprietary
Contents......
1.1About this document......
Intended audience......
Related Documents......
Resource Requirements......
1.1Hardware......
1.2Software......
Test Tools......
1.3Responsibilities......
Features to be Tested (Scope)......
Requirements......
Dependencies and Integration......
Test Strategy and Approach......
ADF Features......
Election Navigation......
Printing and tabulation......
Security......
Features Not to Be Tested......
Title 1.0Test Plan1
©2012-2015 Confidential and Proprietary
1Introduction
This document outlines the test approach for the ClearAccess component of the ClearVote system.
1.1About this document
This test plan describes the test approach for ClearAccess, the Accessible Ballot Marking Device component of the ClearVote system.
Intended audience
This document is intended for Clear Ballot Group Quality Assurance and Product staff as part of the documentation of the Quality Program. Other interested parties include other Clear Ballot Group staff as well as certification and independent testing lab staff.
Related Documents
The ClearVote Quality Assurance Program as well as the ClearVote Test and Verification Specification provide the framework for this document. User documentation also contextualizes the tests performed.
Resource Requirements
This section briefly describes the resources required for testing ClearAccess. See the Quality Program and Test Specification for more details about the testing environment at Clear Ballot Group.
1.1Hardware
Two touch-screen equipped computers, the Dell 3030 and the Dell 7348, were recommended for use with ClearAccess
1.2Software
These tests require the ClearAccess version 1.0.0 software to be fully installed. ClearAccess uses the Chrome browser.
Test Tools
ClearAccess is tested manually. A number of the features of a given Accessible Definition File (ADF) that encodes an election are set up in ClearDesign.
1.3Responsibilities
The test plan creation and test case execution are the primary responsibility of the Quality Assurance staff. Other staff contribute expertise and support.
The QA staff research and consult with others to determine the correct software functionality. They then determine the test approach (this document), and outline the steps for each test case.
The test cases are executed (usually by the QA staff, but as noted on complete test case reports), and defects are entered. Defects are evaluated by the development staff, the CTO and/or the Product Manager.
Fixed defects are verified by the QA staff after release to the QA environment.
Features to be Tested (Scope)
The ClearAccess test plan covers the following features
- ADF features (overlaps with ClearDesign)
- Election navigation
- Printing and tabulation
- Security
Requirements
ClearAccess must meet all certification requirements for an accessible Ballot Marking Device.
The marked ballots produced must be able to be scanned and tabulated correctly by the ClearCount component of the ClearVote system.
Dependencies and Integration
ClearAccess is very heavily dependent on ClearDesign. The ADF file required for voting in an election is created in ClearDesign.
End-to-end testing that includes tabulation of the marked ballots created by ClearAccess is an essential portion of the testing effort
Test Strategy and Approach
ADF Features
Several features of the ADF and ClearAccess voting experience are defined within ClearDesign. These include several of the codes to access the election, and whether undervotes or blank votes receive a warning message. These test cases therefore overlap both components of the system with the criteria set in ClearDesign and the verification of the criteria performed in ClearAccess.
Election Navigation
Election navigation includes confirmation that a user can navigate a ballot through the various means provided: touchscreen, E-Z Access keypad (with audio only or with both visual and audio present) and Origins sip-and-puff. The help provided must match the device used.
The ClearAccess documentation provides detailed accounts of how to use each device supported by ClearAccess.
Printing and tabulation
A variety of common printer scenarios were tested to demonstrate the ability of the system to recover. In addition, as stated above, the ability of the ballots produced by ClearAccess to be tabulated by ClearCount was tested consistently.
Security
In order to prevent unauthorized access to other areas of computer running ClearAccess, security and hardening were reviewed and tested. This includes physical security to prevent access to power buttons, unused USB ports, etc.
Title 1.0Test Plan1