Verify and run a Swittest EMV test suite
A 8-step recipe with Switstack. We can help you get access.
Recipe · 8 steps
Verify and run a Swittest EMV test suite
with Switstack · Software Quality Engineering
Pre-flight a suite, then run a test selection with streaming results.
- authenticate
- list-suites
- Suites and tests are addressable by name or index interchangeably.
- get-test
- Read the test's configuration before running — this is what tells you whether its pre-conditions match the device.
- The virtual card the test presents.
- Validate content and format before committing bench time. A malformed suite that fails mid-run wastes a session; verification is cheap.
- The 200 response is text/event-stream (SSE with data/event/id/retry). Read pass/fail from TestStatusEnum in the streamed TestResultSchema and failure detail from ErrorIndicationSchema — the HTTP 200 is not a pass.
What you'll need to have ready
- username
- password
- suite: Test suite name or index.
- test: Test name or index, for the inspection steps.
- test_selection: A single name, an index (1036), a comma list (0, 99, 1036), a range (0-5), a list of ranges (0-5, 15-40), a mix (0-5, 8, 9, 15-40), or `all`.
- verbose: 0 status/errors, 1 + payment and log data sets, 2 + parsed authorization TLV, 3 + parsed DF8129/DF8115/DF8116.
For your developer
Arazzo workflow switstack:verify-and-run-a-test-suite, 8 operations: token → list_test_suites → get_test_suite → get_test → get_test_config → get_test_vcard → verify_test_suite → run_tests. Specs on APIs.io.