Sunday, September 28, 2008

Laverdi looking for testers in vilnius



LAVERDI is looking for a TEST ANALYST/TESTER and TEST TEAM LEADER in Lithuania.
This is very urgent requirement, please send the cv and 2 references to Mr.Ibish Ozen,
Managing Director, i.ozen@laverdi.com

Friday, September 26, 2008

sample exam questions ISTQB



Yesterday recieved a gift from internet friend, the tester. He had passed the test, ISTQB, foundation level. Send me the book he used for practising - "sample exam questions ISTQB". "120 Practise questions and solutions" . Will take ISEB testing foundation exam. As foundation ISEB now relates to ISTQB foundation level, the book should help. Going to passs it until Christmas. Stil some time left for studying.

Wednesday, September 17, 2008

apie ISEB sertifikavimą LT

Sorry, english readers, this post only in lithuanian.

Lietuviams testuotojams: nebloga kolegos nuoroda apie testuotojų sertifikavimąsi, išskirtinai ISEB, ne ISTQB.

Sunday, September 14, 2008

Reaching the end of a job interview, the human resources person asked a QA engineer fresh out of the community college ,
"And what starting salary were you looking for?"
The engineer said, "In the neighborhood of $125,000 a year, depending on the benefits package."
The interviewer said, "Well, what would you say to a package of 5-weeks vacation, 14 paid holidays, full medical and dental, company matching retirement fund to 50% of salary, and a company car leased every 2 years - say, a red Corvette?"
The Engineer sat up straight and said, "Wow! Are you kidding?"
And the interviewer replied, "Yeah, but you started it."

Tuesday, September 09, 2008

tester's day!

Happy testers day!



Top 24 replies by programmers when their programs don't work:

24. "It works fine on MY computer"
23. "Who did you login as ?"
22. "It's a feature"
21. "It's WAD (Working As Designed)"
20. "That's weird..."
19. "It's never done that before."
18. "It worked yesterday."
17. "How is that possible?"
16. "It must be a hardware problem."
15. "What did you type in wrong to get it to crash?"
14. "There is something funky in your data."
13. "I haven't touched that module in weeks!"
12. "You must have the wrong version."
11. "It's just some unlucky coincidence."
10. "I can't test everything!"
9. "THIS can't be the source of THAT."
8. "It works, but it's not been tested."
7. "Somebody must have changed my code."
6. "Did you check for a virus on your system?"
5. "Even though it doesn't work, how does it feel?"
4. "You can't use that version on your system."
3. "Why do you want to do it that way?"
2. "Where were you when the program blew up?"
1. "I thought I fixed that."