The Council of Europe’s E-Voting Handbook¹⁴ identifies six types of testing EMBs should conduct:

• Acceptance Testing – this method of testing software that tests the functionality of an application performed on a system (for example software, batches of manufactured mechanical parts, or batches of chemical products) prior to its delivery.
• Performance Testing –  this testing determines the speed or effectiveness of a computer, network, software program or device. This process can involve quantitative tests done in a laboratory, such as measuring the response time or the number of millions of instructions per second (MIPS) at which system functions. Qualitative attributes such as reliability, scalability and interoperability may also be evaluated. Performance testing is often done in conjunction with stress testing.
• Stress Testing – this testing determines the stability of a given system or entity. It involves testing beyond normal operational capacity, often to breaking point, in order to observe the results. Stress testing may have a more specific meaning in certain industries, such as fatigue testing for materials.
• Security Testing – this process determines if an information system protects data and maintains functionality as intended. The six basic security concepts that need to be covered by security testing are: confidentiality, integrity, authentication, authorization, availability and non-repudiation.
• Usability Testing – this technique evaluates a product by testing it on users. It can be seen as an irreplaceable usability practice, since it gives direct input on how real users use the system.
• Review of Source Code – this systematic examination of computer source code aims to find and rectify mistakes overlooked in the initial development phase, improving both the overall quality of the software and the developers’ skills.¹⁵

^{14 Caarls, S. (2010) E-voting Handbook: Key steps in the implementation of e-enabled elections, Strasbourg: Council of Europe}

^{15 CoE (2010).}