EMV Testing

See swittest online documentation for more details.

Testing an EMV Level 2 kernel is an herculean task. There are thousands of test cases that must be executed during certification sessions. And most of the test plans must be run manually. But the main problem is on the number of times you have to run them: - A test plan update; - A specification update; - A specification bulletin release; - A piece of code modifed to improve the product;

... should lead to QA sessions in the limit of your team's bandwidth to avoid costly surprises at the lab.

When you manage an EMV Level 2 stack that supports 15+ kernels, these update situations occur very often. Out of your control, you will receive a certification tool update every week. That's why switstack moka ecosystem has been designed so EMV functional tests must performed at each commit. Switstack development infrastructure uses CI/CD pipes to realize systematic test plan executions. It is the only way to scale that type of compliance software.

EMV testing is a feature that is delivered as a service. For each EMV Level 2 kernel, switstack releases and maintains an automated test service emulating the corresponding official test plan to help developers to maintain their code. It is not meant to replace accredited tools but it is the only instant guaranty that your EMV development cycles are on track and ready to go to certification.