Test Cases

UC11_TC_1

* Preconditions: The trajectory plans are completed * Input conditions / steps: The trajectories are analysed in terms of joint angles. * Expected results: The joint values of the robot tracking the trajectories keeps within the robot's joint limits

UC11_TC_2

* Preconditions: The trajectory plans are completed * Input conditions / steps: The trajectories are analysed in terms of velocities/accelerations of joints. * Expected results: The velocities and accelerations of joints of the robot tracking the trajectories keeps within the robot's joint limits

UC11_TC_3

* Preconditions: The trajectory plans are completed. * Input conditions / steps: The trajectories are analysed in terms of jerks of joints. * Expected results: The jerks of joints of the robot tracking the trajectories keeps within the robot's limits.

UC11_TC_4

* Preconditions: The trajectory plans are completed. * Input conditions / steps: Make collision check of the trajectories for both robot itself and automotive body. * Expected results: The robot does not collide itself and automotive body.

UC11_TC_5

* Preconditions: Robot is moving according to the trajectory plans. * Input conditions / steps: Check the relative distances of robot body to existing obstacles in the environment. * Expected results: The system should avoid from obstacles within the limits of safety.

UC11_TC_6

* Preconditions: Robot is moving according to the trajectory plans. * Input conditions / steps: A human enters to the workspace of robot. * Expected results: The robot obeys safety-rated stop/speed and separation monitoring requirements of the standard ISO15066:2016 [10]; and ISO10218-2:2011 [9].

UC11_TC_7

* Precondition: This system follows a predefined trajectory. * Input Condition/steps: During runtime, publisher sends data to the subscriber node according to the due job by the system. The normal frequency of messages publish/subscribe by publisher/subscriber is checked and monitored with reference to previous data. During the attack, the unexpected amount of malevolent request(s) to the publisher/subscriber. * Expected Results: The malevolent request(s) to the publisher/subscriber is detected as an anomaly by comparing the communication frequency for the work done in reference time and comparing with requested job.

UC11_TC_8

*Precondition: This system follows a predefined trajectory. *Input Condition/steps: At runtime, a certain traffic flow occurs in the system depending on the workload. During the attack, this data flow is increased and due to this the expected data is lost or this data flow is decreased and due to this the unexpected data flood. *Expected Results: The traffic flow in the system is controlled according to the reference interval and control mechanism catches the abnormality.

UC11_TC_9

-Robot trajectory test * preconditions: Digital twin of the system should be modelled in Gazebo environment. * input conditions / steps: Trajectory created in digital twin which can control vehicle parts without collision and virtual pictures (2D) should be present. * expected results: Existence control of minimum %95 parts of vehicle in less than 25 minutes and in each trajectory point minimum %15 of each part must be visible.

UC11_TC_10

-Human presence test * preconditions: Two cameras enabling to capture view from both sides of each robot. * input conditions / steps: Human's presence in robots' work area. * expected results: Adjustment of robot speed depending on human distance from robot.

UC11_TC_11

-MiTM attack test * preconditions: Enable access to local network over a cable (like Cat 6, etc) * input conditions / steps: Try to sniff network communication * expected results: Cannot sniff network communication

UC11_TC_12

-DoS attack test * preconditions: Enable access to local network over a cable (like Cat 6, etc) * input conditions / steps: Try to saturate local network by sending huge amount of communication packets. * expected results: Detection and isolation of attacker.

UC11_TC_13

ARP poisoning test * preconditions: Enable access to local network over a cable (like Cat 6, etc) * input conditions / steps: Try to positioning with fake ARP requesting packets. * expected results: Local switch infrastructure protected by security systems.

UC11_TC_14

-User authentication protocol * preconditions: Enable access to local network connection over a cable (like Cat 6, etc.). * input conditions / steps: Try to connect to system on unauthorized access * expected results: Unable to access to any systems.

UC11_TC_15

-Penetration test (firewall, router etc.) * preconditions: Enable access to local network and external IP address * input conditions / steps: Try to bypass firewall and router systems. * expected results: cannot bypass firewall and router systems.

UC11_TC_16

- ML inference * Pre-conditions: The system under testing is in operational mode, environmental and intrinsical data are being logged. * Input conditions / steps: A pre-defined fault is injected into the system via IMFIT or another tool. * Expected results: ML engine detects the fault by inference and classifies it with an accuracy rate of no less than 95%

UC11_TC_17

Deep Learning Models * Pre-condition: The simulation is being run and in active mode. * Input conditions / steps: A set of malicious or fake images are fed into the visualisation block of the process. * Expected outcome: The images are labelled as unreal and the alert mechanism is triggered.

UC11_TC_18

*Precondition: Secure Gateway has been installed / connected under UC11. * Input conditions / steps: Periodic data transfer is started and web interface is renewed every 30 seconds over Ethernet. Gateway is in transparent mode. * Expected outcome: It is expected that the communication will continue uninterrupted for 24 hours and web interface will be accessible.

UC11_TC_19

*Precondition: Secure Gateway has been installed / connected under UC11. * Input conditions / steps: Encrypted data transfer is periodically initiated over the gateway. * Expected outcome: In encrypted communication, the data rate is expected to be 140KBps

UC11_TC_20

*Precondition: iPerf software is installed on the Firmware of Secure Gateway. * Input conditions / steps: The iPerf software included in the Secure Gateway software is started. * Expected outcome: Secure gateway Ethernet speed testing with iPerf result is obtained 1 MB / sec or higher.