Skip to content
QA Knowledge Hub

Test cases for a lift / elevator

Updated 2026-11-13 · 6 min read

Testing a lift is a favourite interview prompt for checking how you think. These 32 cases cover calls and travel, doors, load, emergencies, access control, accessibility and performance.

Assumes a passenger lift in a ground-plus-ten building (floors G to 10, plus one basement for parking), with car buttons, up and down landing buttons, door open and close buttons, an alarm button, an overload sensor and an access-card reader for the basement and floor 10.

How to answer in an interview

Ask before listing: how many floors and lifts, the rated load (from the plate inside the car), whether lifts work as a group, which floors are restricted, and what must happen on a power cut or fire alarm. Say that safety certification is done by authorised inspectors, and that your cases cover the controller's behaviour. Then group: calls and travel, doors, load, emergencies, access, accessibility and performance.

Scope and test data

Physical safety checks (brakes, ropes, landing door locks) are for qualified lift technicians; where a case below touches them, it is written as "observed during the technician's inspection". Use a soft foam block, not a hand, for door obstruction tests, and test weights for load tests. Waiting-time and levelling limits must come from the installer's specification before these cases can pass or fail. These are designed cases, not an execution report.

Calls and travel

IDCategoryTest caseExpected result
E01FunctionalLift idle at G; press Up on floor 3Lift travels to 3, Up arrow lights, doors open
E02FunctionalInside the car, press 7Lift travels to 7, stops level, doors open, display shows 7
E03FunctionalPress the button for the floor the lift is already onDoors open (or stay open); no travel
E04FunctionalFrom G going up, press 8, then 2, then 5Stops at 2, 5 and 8 in that order (direction order), unless the spec says otherwise
E05FunctionalOn floor 4, press Up and Down while the lift passes going upLift stops for Up on the way up; the Down call is served on the way back
E06BoundaryLook at the landing panels on floor 10 and in the basementFloor 10 has no Up button; the basement has no Down button
E07BoundaryTravel to the top floor and to the basementLift stops level at both ends and never overruns
E08NegativePress B (basement) without showing an access cardCall is not registered, or the panel asks for a card
E09FunctionalPress a car button twice to cancel it, if the lift supports cancellingCall is cancelled and the light goes off; if unsupported, nothing changes
E10FunctionalLeave the lift with no calls for the idle periodParks at its home floor if configured; doors closed; car fan and light switch off as specified

Doors

IDCategoryTest caseExpected result
E11FunctionalPress Door Open while the doors are closingDoors reopen
E12FunctionalPress Door Close after the doors openDoors close sooner, or the button is ignored, as specified
E13FunctionalPut a foam block in the door path while the doors closeDoors reverse before pressing hard on the block
E14NegativeHold the doors open past the timeoutBuzzer sounds; doors close slowly (nudging) if that feature exists
E15FunctionalTry to make the lift travel with the car door held openLift does not move while any door is open
E16FunctionalObserved during the technician's inspection: try the landing door on a floor where the car is not presentLanding door stays locked

Load

IDCategoryTest caseExpected result
E17BoundaryLoad the car to its rated load with test weightsTravels normally
E18BoundaryAdd weight just above the rated loadOverload buzzer and indicator; doors stay open; lift does not move
E19FunctionalRemove the extra weightOverload warning clears; lift accepts calls again

Emergencies and service modes

IDCategoryTest caseExpected result
E20FunctionalPress and hold the alarm buttonAlarm sounds and the intercom reaches security or the monitoring desk within the agreed time
E21NegativeCut mains power while the lift travels between floorsEmergency light works; if a rescue device is fitted, the car moves to the nearest floor and opens its doors
E22FunctionalTrigger the fire alarm signal in a controlled testLift goes to the designated floor, opens its doors and ignores normal calls, as the local code and spec require
E23NegativeSimulate a fault that stops the car between floorsDoors do not open between floors; alarm and intercom still work; the fault is logged
E24FunctionalTechnician switches the lift to maintenance modeLanding calls ignored; landing displays show it is out of service

Access, accessibility and UI

IDCategoryTest caseExpected result
E25SecurityShow a card allowed for floor 10 only and press BB refused; 10 accepted
E26SecurityShow an expired or blocked cardAll restricted floors refused; event logged
E27UIRide from G to 10 and backCar and landing displays show the correct floor and direction at every floor
E28UIArrive at a floorChime and voice announcement (if fitted) name the floor
E29UICheck button height and markingsButtons reachable from a wheelchair; raised or Braille markings as specified
E30UIPress any buttonIt lights on press and goes off when the call is served

Performance

IDCategoryTest caseExpected result
E31PerformanceMorning peak simulation: many up calls from G with all lifts in serviceGroup control sends a suitable car; waiting time stays within the installer's figure
E32PerformanceMeasure the step between car floor and landing at several floors, empty and loadedWithin the installer's levelling tolerance

What to prioritise

The cases that protect people come first: doors (E13, E15, E16), overload (E18) and emergencies (E20 to E23). A common mistake is to spend the whole answer on buttons and displays. Another is to forget the multiple-lift case: with two or more lifts, "which lift answers my call" is a requirement you should ask about.

Downloads

Quick answers

Would a software tester really test a lift?

Not its safety certification: that is done by the installer and authorised inspectors under local rules. The question checks whether you can find behaviours, boundaries and failure cases for any system. Say that early, then answer as if you were testing the lift controller's behaviour.

Should the lift stop at floors in the order the buttons were pressed?

Usually not. Most passenger lifts serve calls in the direction of travel (collective control), so pressing 8, 2 and 5 going up gives stops at 2, 5 and 8. Ask which control logic the lift uses rather than assuming.

Want a project you can show in interviews?

The portfolio project kit walks you through testing a deliberately buggy app with Selenium or Playwright and API tests, then explaining it. The app itself is free.