1

Create device tree with one licensed device node.

2

Check License bus controller.

1

When one licensed device node is present, one license is consumed for this driver.

When driver is started, system calculates number of instances marked with Licensed attribute and requests that amount from the currently installed license.

1

Check driver copyright information

1

Driver copyright information is in this format: Copyright © 'COMPANY' 'YEAR'

1

Create and upload configuration in SC-1000 Configurator software. Configuration should contain additional nodes (e.g. CAN modules, doors, etc.).

2

In C4 create a SC-1000 Bus Controller in configuration device tree with all necessary properties filled correctly. No other nodes are needed at the moment.

3

Click Load Configuration command on SC-1000 Bus Controller.

4

Follow import instructions.

5

Check results in updated device tree.

1

Nodes that were configured in SC-1000 Configurator are present in C4 device tree.

2

Device works as configured.

1

Modify configuration through the SC-1000 Configurator application by adding a new node and changing the name of an existing node and upload it to the SC-1000 Bus Controller.

2

In C4 click Load Configuration command on SC-1000 Bus Controller.

3

Follow import instructions.

4

Check results in updated device tree.

1

C4 device tree is updated.

2

Device works as configured.

1

Set the device time 60 min back.

2

Start the endpoint

3

Wait until driver is fully started

4

Check the time on device

1

Device time is synchronized with C4 server current time.

Time set to 'DEVICE'. Offset with real time was 'OFFSET' minutes

Event is stored only when the time difference is greater than C4 preset value

1

Start the endpoint

2

Wait for connection establishment.

3

Drop the connection on the switch or router, in such a way that the Windows system still detects the Ethernet connection.

4

Wait until the disconnection is signaled.

5

After circa 30 seconds, the driver attempts to reconnect. Wait until the attempt is finished.

6

Recover the connection.

7

Wait for connection reestablishment.

1

During a disconnection, all device nodes under the endpoint are set to "Disconnected" state.

2

After the connection is recovered, all device nodes under the endpoint are set to their real state.

'DEVICE' network connection interrupted.

'DEVICE' network connection restored. Number of retries: RETRYCOUNT.

1

Create an incomplete configuration tree with missing device.

2

Establish connection.

1

Endpoint continues to work.

Configuration failure 'PARENTDEVICE': Missing device 'DEVICENAME' with address: 'ADDRESS'. Detail: 'EVENT_DESCRIPTION'

Test must be repeatable on each node type that can be created in a tree and that can be removed from device tree configuration without harming the core functionality (e.g. it doesn’t make sense to remove the driver node itself or panel node when only one panel is allowed in configuration, but it’s perfectly valid for detectors, contacts, etc.).

1

Start the endpoint.

2

Interrupt the connection between some devices

3

Wait until the disconnection is signaled

4

Recover the communication and wait until the driver states recover.

1

During disconnection, the disconnected device nodes under the endpoint are set to "Disconnected" state.

2

After the connection is recovered, device nodes under the endpoint are set to their real state.

Internal communication error 'DEVICE'. Description: 'DESC'

Restored 'DEVICE' after an internal communication error. Description: 'DESC'

1

Create two devices of the same type (see notes for same types) that are identified by the address, in the device configuration tree.

2

Set the same address value for both devices.

3

Start the endpoint.

1

One or both items with the same address value have their status set to “ConfigurationFailure”. If driver can maintain communication with one of the conflicted devices, then only the not communicating device’s status is set to “ConfigurationFailure”.

2

Other devices work normally.

Duplicated address 'NUMBER' detected between 'DEVICE1' and 'DEVICE2'.

All devices are considered as same type as follows: door, turnstile, partition, lift unit, lift door, relay controller, ramp.

All modules (main module and CAN module expanders) are considered as same type.

•

Ideally, no exception should occur. If an exception happens, plugin should log it only in unexpected scenarios.

•

If plugin logs exceptions in expected scenarios, it's bad design.

•

For example, if plugin cannot connect to device because wrong password is entered in C4, exception should not be logged, warning is recommended, since such exception should be handled in the code.

1

Download plugin(*.c4plugin)

2

Extract all files from it. You can use 7-Zip, or some other packer you prefer.

3

In normal conditions, driver package should contain only common files, which might be part of driver (dll, pdb, package, etc.). We try to avoid distribution of unnecessary files, which might appear in the driver's package accidentally. However, there might be valid reasons to distribute such files.

4

If driver package contains non-common files developer should prove that he really needs these files.

•

Plugin contains only necessary files.

1

Add each device node category to device tree.

2

Make sure that description of every device property is in the manual.

3

Test functionality of each device property.

1

Each property is described in manual

2

Functionality of each property corresponds to the manual.

1

Disconnect the mains power

2

Wait until the disconnection is signaled

3

Reconnect mains power

4

Wait until the recovery is signaled.

1

When mains power is disconnected device status is set to Fault state

2

After mains power is reconnected device status is set to real status of device.

'DEVICE' mains failed.

Restore 'DEVICE' after a mains failure.

This test must be replicable on all types of devices that have independent powering and are backed up by battery or another power source

1

Disconnect the backup power

2

Wait until the disconnection is signaled

3

Reconnect the backup power

4

Wait until the recovery is signaled

1

When backup power is disconnected device status is set to Fault state

2

After backup power is reconnected device status is set to real status of device.

'DEVICE' – low battery.

'DEVICE' – low battery restored.

This test must be replicable on all types of devices that have independent power and are backed up by battery or another power source.

1

Configure an access point to combined credentials mode using SC-1000 Configurator. (Only Card + PIN is supported.)

2

Upload configuration, and wait until it is applied to the device

3

Create new person.

4

Grant the person access to the access point.

5

Assign the person a valid credential which support merging

6

Merge these credentials together

7

Send credentials to the device.

8

Use the credential to access the access point

1

The person got access to specific access point

Access granted to 'PERSON' at 'DEVICE' using ‘Card’ at ’READER’.

SC-1000 stores card only in event message, so card is stored in audit log, even if combined credentials are used. Combined access mode is configured in SC-1000 Configurator.

The SC-1000 supports neither “PIN code only” nor “Card or PIN” access mode.

If the door did not open, Access granted message will NOT be sent.

1

Create a new person

2

Grant the person access to the access point

3

Assign valid Card to this person

4

Send credentials to the device

5

Use the credential to access the access point

6

Door is opened.

•

Person has correctly defined permissions in a device

'UPLOAD_TYPE' upload to 'DEVICE' successfully completed (duration'TIME').

Access granted to 'PERSON1' at 'DEVICE1'.

If the door did not open, Access granted message will not be sent.

Follow Test Scenarios section

Example case 1: Create 2 persons. Add valid credentials to both persons.

Add access to both persons on both doors.

Perform credential upload.

Change access so Person A has access only to Door 1 and Person B only to door 2.

Perform incremental credential upload.

Verify that persons only have access to expected access point.

Verify that access events contain correct person name.

Example case 6: Create 2 persons.

Add Card 1 to person A. Add card 2 to person B.

Add access to access points.

Perform credential upload.

Change credentials, so Person A has Card 2 and Person B has Card 1.

Perform incremental credential upload.

Verify that persons only have access to expected access points, with correct card.

Verify that access events contain correct person name.

All upload scenarios finish successfully. Upload does not fail in any case.

Persons have access to all expected access points with expected credentials.

Access events contain correct person which accessed the access point.

1

Execute command “Door manual override” on door

2

Try to open the door using valid credential

3

Execute command “Door manual override off” on door

1

During door lockout door ignores any attempt to open it with valid credentials

2

Status of the door is DoorManualOverrideOn when overridden.

'PERSON' sent command 'Door Manual Override Off' to 'DEVICE'.

Command 'Door Manual Override Off' from 'PERSON' was delivered to 'DEVICE'.

'DEVICE' manual override finished.

'PERSON' sent command 'Door Manual Override' to 'DEVICE'.

Command 'Door Manual Override' from 'Support' was delivered to 'Door 1'.

‘DEVICE' manual override started.

1

Execute command “Door unlock permanently” on door

2

When door contact is present, simulate real door opening

3

Execute command “Door lock” on door

4

When door contact is present, simulate real door closing

1

After issuing the command "Door unlock permanently ", the door status is set to Unlocked Permanently.

2

During real door opening, the door contact is activated, and the door status is set to Opened.

3

After issuing the command " Door lock ", but door contact is still open, the door status remains Opened.

4

After real door closing, the door contact is deactivated or the door relay timer expires, the door status returns to Locked (normal) state.

'PERSON' sent command 'Door Unlock Permanently' to 'DEVICE'.

Command 'Door Unlock Permanently' from 'PERSON' was delivered to 'DEVICE'.

'DEVICE' unlocked permanently.

'PERSON' sent command 'Door Lock' to 'DEVICE'.

Command 'Door Lock' from 'PERSON' was delivered to 'DEVICE'.

'DEVICE' locked.

1

Activate door contact when door is locked

1

Door status is set to Forcibly open

Door 'DEVICE' forced open.

1

Use the credential to access the access point

2

Activate door contact

3

Keep the contact activated longer than the predefined time

1

Door status is set to Open when the door contact is activated.

2

After predefined open time expiration, the door status is set to Open Too Long.

3

Two Room Closed events are received.

'DEVICE' opened.

Door 'DEVICE' open too long.

1

Execute command “Door unlock” on door

2

When door contact is present, simulate real door opening

3

When door contact is present, simulate real door closing

1

After issuing the command "Door unlock", the door status is set to Unlocked.

2

During real door opening, the door contact is activated, and the door status is set to Opened.

3

After real door closing the door contact is deactivated, and the door status is set to Unlocked.

4

If the door relay timer also expires, the door status returns to Locked (normal) state.

'PERSON' sent command 'Unlock' to 'DEVICE'.

Command 'Unlock' from 'PERSON' was delivered to 'DEVICE'

'DEVICE' unlocked.

'DEVICE' opened.

Access granted for 'UNKNOWN CREDENTIAL ' at 'DEVICE'.

'DEVICE' unlocked.

'DEVICE' locked.

1

Activate Exit Button.

2

When door contact is present, simulate real door opening

1

During real door opening, the door contact is active, and the door status is set to Open.

Exit button pushed 'DEVICE'.

1

Create a new person

2

Assign the person a valid credential

3

Grant the person access to the access point

4

Send credentials to the device

5

Use the credential to access the access point

6

Open the door

1

Person got access to specific access point

Access granted to 'PERSON' at 'DEVICE' using ' CREDENTIAL_TYPE' 'CREDENTIAL_NAME' at reader 'READER'.

If the door did not open, Access granted message will not be sent.

1

Create new person

2

Assign the person a valid credential

3

Grant the person access to the access point

4

Deny the person access to another access point

5

Send credentials to the device

6

Use the credential to access another access point

1

Person did not get access to specific access point

Access denied to 'PERSON' at 'DEVICE' using credential 'CREDENTIAL_NAME' on reader 'READER'.

Reason: Door not allowed

7

Revoke all access rights for Person

8

Issue Full Upload command

9

Slide a card on correct reader

2

Card will be recognized as unknown

Access denied to 'PERSON' at 'DEVICE' using credential 'CREDENTIAL_NAME' on reader 'READER'.

Reason: Credential unknown at this door

1

Create a new person

2

Assign the person a valid credential

3

Grant the person access to the access point

4

Restrict access permission with time restriction

5

Send credentials to the device

6

Check whether the restriction is applied correctly

1

The assigned time restriction is correctly applied

2

When a person has no limitation in access it gets access granted event (with the condition that the door was actually opened). When person has limited access by time restriction it gets access denied event.

Access granted to 'PERSON' at 'DEVICE' using 'CREDENTIAL_TYPE' 'CREDENTIAL_NAME' at reader 'READER'.

Access denied to 'PERSON' at ‘DEVICE' using credential 'CREDENTIAL_TYPE' on reader 'READER'. Reason: Active time restriction

SC-1000 can handle maximum 15 different time restriction sets.

Access granted message will be sent only if the door was opened.

1

Create a new person

2

Assign the person a valid credential

3

Create holiday set, having today’s date

4

Send credentials to the device

5

Check whether the restriction is applied correctly

6

Modify holiday set in a way that it doesn't contain today’s date

7

Send credentials to the device

8

Check whether the restriction is applied correctly

1

The assigned time restriction is correctly applied

1

Issue a tamper on a device

2

Restore the tamper

3

Confirm the alarm from C4 UI (Reset alarm command).

1

Until the alarm confirmation, the detector has active tamper status.

Tamper on 'DEVICE'.

Tamper completed on 'DEVICE'.

Test must be reproducible on all devices that are capable of generating the tamper alarm

In case the device ends the tamper state automatically, there is no need to confirm the tamper from C4 UI and the test is also considered as passed.

1

Create a complete configuration device tree with additional nodes of each type that are not presented on device.

2

Set address of additional nodes to a fictive value.

3

Start the endpoint.

4

Check the status of all nodes in device tree.

1

Driver starts.

2

Nodes that are presented on device have equal status to real status of device.

3

Nodes that are not presented on device have unknown status (black).

1

A RelayController node must be configured to the device.

2

Execute command “On” on RelayController.

3

After the output is opened, execute command “Off” on it.

1

When output is activated, its status is Open.

2

When output is deactivated, its status is Normal.

'PERSON' sent command 'On' to 'DEVICE'.

Command 'On' from 'PERSON' was delivered to 'DEVICE'.

'DEVICE' opened.

'PERSON' sent command 'Off' to 'DEVICE'.

Command 'Off' from 'PERSON' was delivered to 'DEVICE'.

'DEVICE' closed.

1

Disconnect the endpoint

2

Wait for 1 minute

3

Execute operation on device that leads to the entry in the device audit log

4

Wait for 1 minute

5

Connect the endpoint.

1

All events from the device that happened during disconnection are stored in audit log with original time of the events on device, not with the time when they were read out from the device.

1

In SC-1000 Configurator software create a Partition

2

Create a zone under the partition with the Zone Type property set to Intruder alarm

3

Create a zone under the partition with the Zone Type property set to Fire alarm

4

Create a zone under the partition with the Zone Type property set to 24 hours

5

Upload configuration

6

After successful reconnect in C4, import configuration

7

Make sure the partition is not armed

8

Activate input contacts on device

9

Deactivate input contacts on device

10

Arm (or forced arm) the partition

11

Activate input contacts on device

12

Deactivate input contacts on device

13

Confirm the alarm on partition (Reset alarm command)

1

Partition status is Normal if not armed, and Armed after successfully armed

2

When partition is not armed and contact is activated, the 24 hours type zone status is Alarm.

3

After partition is armed, when contact is activated, its status is Alarm.

4

After Reset alarm command, all deactivated zones status is Normal

'DEVICE' armed.

Alarm on 'DEVICE1'.

Alarm restored on 'DEVICE1'.

Fire Alarm on 'DEVICE2'.

Fire Alarm restored on 'DEVICE2'.

If partition arm was unsuccessful: 'DEVICE' arming failed.

An SC-1000 zone generates alarm only if the partition is armed. A zone will remain in alarm state until acknowledgement even if the detector is not in alarm anymore. Disarming a partition will clear any active alarm from the zone detectors.

1

Issue a duress alarm (the PIN code must be one number higher than the correct one, e.g. instead of 1234 type 1235).

2

Confirm the duress alarm (Reset alarm command)

1

A device where the duress alarm is reported has Alarm status.

2

After confirming the duress alarm, duress alarm is finished and the device where the duress alarm was reported has normal status.

Duress alarm from 'DEVICE'

1

A partition and a zone under it must be in the device hierarchy.

2

Arm the partition

3

Bypass the zone

4

Activate input contacts on device

5

Deactivate input contacts on device

6

Bypass Off command on the zone

7

Activate input contacts on device

8

Deactivate input contacts on device

1

When bypassed, zone status is Bypass.

2

After Bypass Off command, zone status is Normal or Alarm

3

During bypass, no Alarm state is displayed, no Alarm audit log is stored on the Zone.

'DEVICE' bypass on

'DEVICE' bypass off

After Bypass Off: Alarm on 'DEVICE'.

Alarm restored on 'DEVICE'.