The Ups and Downs of Making Elevators Go
I thought this was interesting, and would make for some fun testing as well.
What parts would be challenging to test?
What automation might help in testing?
(The article reminds me of a project I did in grad school, where I attempted to optimize the number of servers and the number of cashiers in a fast-food restaurant (owned by my family), based on projected arrival rates of customers. It was a lot of fun to design and code simulations, and made for some interesting and unexpected results.)
"Sometimes what is good for the individual person isn't good for the rest."
This is the quote that stands out for me and the scenario where there is a person on the 6th floor, with an elevator on the 7th floor (going down) after having already made 2 stops. This really applies in software and test design. It's easy to test whether something returns the right value, but when you have to start testing the user experience, there are so many variables that there is never really one correct answer.
As far as testing goes, sure you could mathematically determine, based on approach times, wait times, travel times, etc. what would be the most efficient behavior, but if that's all you are measuring, are you doing your job?
Thanks for the interesting read.
P.S. And happy belated birthday?
"I feel like I get paid to play videogames. I watch the simulation, and I see what happens, and I try to improve the score I am getting," she says.
I want her job
Hello all, let me introduce myself. I have a BA in Computer Science in 1994 but I've been working in a variety of different positions since, some in that field and some not. Recently my company, where I was technically Admin Asst but I also worked help-desk & tech support overflow, designed our web site, did some SQL reporting, etc., was bought out and now I've been reassigned to develop our QA dept. We have a web-based product rolled out to specific clients, and there are regular updates to the code. There had been, it seems, just one person testing & writing release notes along with his other tasks; I've now taken over the testing & notes and my boss wants to develop it into a more formal setup. (The man I "replaced" is actually no longer with the company; not due to me!) I have a friend in QA who directed me to this site, and I've been browsing around for the past week or so.
The elevator article is great because people don't often think about the behind-the-scenes on things like that. This is an example where all the formal, automated testing in the world wouldn't necessarily give the best result, because you need real users to respond as well - how else did she find out the 20-sec rule. I liked the idea in the in-set picture of telling it ahead of time where you want to go, so the system can more efficiently route you.
You keep on using that word. I do not think it means what you think it means.
Thanks for sharing interesting post also teaching me that there's always a think-outside-the-box solution if dug enough and the principle as "Sometimes what is good for the individual person isn't good for the rest."
a member of QASymphony. www.qasymphony.com
qTrace - Screen Capture Software with Intelligence
qTest - Cloud-based Test Management