Zenmervolt
Elite member
I will never, never, never, never, never again allow myself to get dumped into a project during the testing phase. New rule for my work life: I will never test anything that I have not had a hand in creating.
Originally posted by: Zenmervolt
Just that it's a royal pain to test something that you had not part in designing. Especially first pass testing. UAT is different because the severe bugs are ironed out. It absolutely SUCKS to spend 14 hours in the test lab and not pass even ONE test scenario for the new system and then to find out, in the last 30 minutes, that the reason is because your computer is one of the company's Win 2K boxes instead of XP which is why IE isn't rendering the web portal applications properly.
Also, whoever was in charge of culling the employee numbers for testing was a dumbass and didn't bother to save _ANY_ org info other than title with the employee numbers. Which means that we need to look every goram user up in the database to find out who they report to in order to test the system properly. Also, half the goram employees culled for testing don't have their supervisor added to testing which makes them useless. Also, I have no friggin clue on the logic flows because I wasn't there for system design. Finally, whoever wrote the test scripts has clearly never documented any processes in his or her life.
ZV
It's good that I don't know. Because I would kill them.Originally posted by: Zanix
Test routines are supposed to be build into the design. wtf, where are the people who built it?Originally posted by: Zenmervolt
Just that it's a royal pain to test something that you had not part in designing. Especially first pass testing. UAT is different because the severe bugs are ironed out. It absolutely SUCKS to spend 14 hours in the test lab and not pass even ONE test scenario for the new system and then to find out, in the last 30 minutes, that the reason is because your computer is one of the company's Win 2K boxes instead of XP which is why IE isn't rendering the web portal applications properly.
Also, whoever was in charge of culling the employee numbers for testing was a dumbass and didn't bother to save _ANY_ org info other than title with the employee numbers. Which means that we need to look every goram user up in the database to find out who they report to in order to test the system properly. Also, half the goram employees culled for testing don't have their supervisor added to testing which makes them useless. Also, I have no friggin clue on the logic flows because I wasn't there for system design. Finally, whoever wrote the test scripts has clearly never documented any processes in his or her life.
ZV
Originally posted by: Zenmervolt
It's good that I don't know. Because I would kill them.Originally posted by: Zanix
Test routines are supposed to be build into the design. wtf, where are the people who built it?Originally posted by: Zenmervolt
Just that it's a royal pain to test something that you had not part in designing. Especially first pass testing. UAT is different because the severe bugs are ironed out. It absolutely SUCKS to spend 14 hours in the test lab and not pass even ONE test scenario for the new system and then to find out, in the last 30 minutes, that the reason is because your computer is one of the company's Win 2K boxes instead of XP which is why IE isn't rendering the web portal applications properly.
Also, whoever was in charge of culling the employee numbers for testing was a dumbass and didn't bother to save _ANY_ org info other than title with the employee numbers. Which means that we need to look every goram user up in the database to find out who they report to in order to test the system properly. Also, half the goram employees culled for testing don't have their supervisor added to testing which makes them useless. Also, I have no friggin clue on the logic flows because I wasn't there for system design. Finally, whoever wrote the test scripts has clearly never documented any processes in his or her life.
ZV
ZV