Going Up Test Scenarios

In each of the following sections, a scenario is described (in which a prototypical elevator engineer whom will be called “Doug” is the main character). Each description is preceded with a list of components/features that are needed for that scenario.

Test Scenario 1

Doug is working in the machine room in Sieg when he receives a phone call that Suzallo's elevator is broken. The caller hangs up too fast that Doug is not able to ask for which elevator is having problems. Doug runs to machine room and Suzallo.

He hooks up his Tablet PC with the GoingUp application to the main control board. GoingUp starts and a view of the Suzallo elevators is shown. It is indicated that car 1 has an error and is standing on the 3rd floor, while the rest of the elevators are running normally. Doug goes to the component view for car 1 to get more detail and finds that the door component is the one with the problem. He opts for more detail again and finds that the door open signals (KET-O and KET-S) are in conflicting states.

Doug controls car 1 to go to the 4th floor closer to the machine room. Doug goes to car 1 and fixes the problem. Car 1starts running again automatically.

Test Scenario 2

Doug is in the machine room of Sieg. He was watching all the elevators run normally. Then suddenly GoingUp notifies him that car 2 has an error (conflicting states). Doug goes immediately to the I/O signals view of car 2. He sees that the error is happening in one of the signals of car 1 and not from one of its states. He selects for more detail on the signals and finds that there is conflict between the door open signals (KET-O and KET-S). He knows this problem very well and fixes the elevator immediately. Car 2 starts running again automatically.

Test Scenario 3