Voting System Standard Test Procedures
While voting systems vary greatly, each one is tested using the same test methods. For each test method, a test case or review is customized to the unique voting system.
Voting system testing tasks can be broken down into the following categories: Functional and Physical Configuration, Audits, and the iBeta Deliverables.
Manufacturers deliver their Technical Data Package (TDP), source code, voting system hardware, reports, and other relevant test materials.
| |
Functional Configuration Audit
|
Physical ConfigurationAudit
|
iBeta Deliverables
|
|
Preparation
|
- Review of the voting system manufacturer's testing and functional documentation to assess the scope of testing and test methods.
|
- Review of the TDP for compliance
- Review and documentation of the submitted voting system configuration
- Review and documentation of the conformance to the manufacturer's configuration and quality management
|
- TDP and Code repositories to manage voting system manufacturer's deliveries
- A determination of scope and test methods
- A Discrepancy Report of TDP, quality or configuration management issues
- Preparation of the Certification Test Plan
Submission of the Certification Test Plan to the manufacturer and to the EAC
- Customization of the standard test cases for the specific voting system
|
|
Testing
|
- Coordinate execution of the environmental hardware testing with the subcontractor laboratory
- Execute software testing
Regression testing of fixes
|
- Review the source code for compliance
- Regression review of code fixes
- Witness the build of the executable from the reviewed source code
Review the tested voting system configuration at each test location
- Regression review of TDP fixes
|
- A Discrepancy Report of code and testing issues
- Documentation of the build and installation of the executable
- Documentation of the voting system configuration at each test location
- Documentation of test activity and results in the test cases and Discrepancy Report
- Submission of updates to the manufacturer and EAC of the Certification Test Plan, as needed
|
|
Reporting
|
- Verification of successful completion and documentation of all tests and issues within the test record
|
- Verification of the successful completion and documentation of all reviews, witnessed builds, and voting system configurations within the test record
|
- The Certification Test Report, including the recommendation, test results, and supporting test detail
- Submission of the Certification Test Report to the manufacturer and to the EAC
|
|
Archive
|
- Archive test results to single write media
|
- Archive all review records to single write media
- Archive final source code, disk image of pre-build, post build environments, executable code of the Trusted Build, and installation devices, including their respective file signatures to single write media
|
- Issuance of the final version of the Certification Test Report incorporating the EAC Certification Number
- Delivery of the Trusted Build to the manufacturer and the Approved Repository
- Archive of the complete test record to single write media
|
* Depending upon the determined scope, software testing will include some or all of the following tests: functional, security, integrated system level, usability, accessibility, accuracy, availability, volume, and maintainability.
|
