InnerWeb
Skip to main content

Workshop gate acceptance: five test scenarios

Acceptance of a workshop gate can be closed in five scenarios that take about fifteen minutes in total: refused training, refused permit, double scan, revoked card and exit. Each has a clear expected result, so the person accepting the implementation knows what to record in the protocol.

5
acceptance test scenarios
Source: scope of the page
5 s
double-scan rejection window on the server
13 s
refresh interval of the evacuation list

Preparing for acceptance

Before the test you need four test accounts: a person with a full set of permissions, a person without training, a person without a permit and a person with a revoked RFID card. You also need a working scanner with the keyboard country set and reading of QR codes with a URL switched on, and access to the gate log.

The gate verdict has four elements: valid training, qualification for hazardous work, an active permit (or a scheduled visit) and an active account. Each scenario below tests one of them or one of the protective mechanisms of the gate.

Scenarios 1 and 2: refused training and refused permit

Scenario 1: scan the badge of a person without valid training. Expected result: a refusal, a missing training with its name recorded in the log, a voice alarm that tells a missing training apart, and a notification with the person, date, place and the missing item.

Scenario 2: scan the badge of a person without an active permit. Expected result: a refusal, a missing permit recorded in the log, and a voice alarm that tells a missing permit apart. If the alarm plays the same signal in both scenarios, although it should tell them apart, check the sound configuration.

Acceptance test scenarios of the gate

Acceptance test scenarios of the gateChart: five test scenarios in order, from refused training to exit.012345orderRefused trainingRefused training: 1 order1Refused permitRefused permit: 2 order2Double scanDouble scan: 3 order3Revoked cardRevoked card: 4 order4ExitExit: 5 order5
Source: Scenario layout based on to

Scenario 3: double scan

Scan the same badge twice within a short interval. Expected result: one record, and the second scan rejected. The protective window is 5 seconds on the server and 2584 ms in the browser.

Also check a scan after five seconds: now the system should accept it as another punch, that is an exit if the person is inside. The test shows the edge of the window and confirms that it is not too wide.

Scenario 4: revoked card

Scan a revoked RFID card. Expected result: the card does not identify its owner at the gate, the scan goes to the log as rejected, and the person is not let in.

In addition, check the behaviour of the training kiosk: the kiosk deliberately treats a revoked card differently from the gate. This is not a fault, so do not record it as one. Note in the protocol that the difference was checked and matches the expectation.

Scenario 5: exit

Scan the badge of a person who is inside the plant, with a green verdict. Expected result: the system records an exit, because it sets the direction of the record itself: a green verdict and a person inside gives an exit. The person disappears from the list of people on site, and the evacuation list refreshes every 13 seconds.

Confirm that there is no entry button at the gate: the scan itself is the act of control. The absence of such a button is part of the acceptance, because it proves that nobody can be let in outside the register.

Acceptance protocol

Record in the protocol: the date, the persons testing, the result of each of the five scenarios (compliant or not compliant), the scanner settings and remarks. A non-compliance in any scenario closes the acceptance conditionally, pending correction and repetition of that scenario.

The protocol later serves as evidence for an audit that the gate worked according to the specification on the day of go-live. It is good to attach a printout of the log with the five test scans.

Checklist

Video

Frequently asked questions

How long does acceptance in five scenarios take?

About fifteen minutes if the test accounts and the scanner are ready. Most of the time goes on entering the results into the protocol.

Is the difference in the kiosk's behaviour a fault?

No. The training kiosk deliberately treats a revoked card differently from the gate.

What to do if the alarm plays the same signal for a missing training and a missing permit?

Check the sound configuration. The system should tell the two cases apart, and in other cases only the refusal signal sounds.

Let's talk about the gate in your workshop

We will show the security panel on the example of a rolling stock maintenance depot and discuss how to connect it to your existing access control system.

Let's talk