99 Things You Can Do to Become a Better Tester - 1

keleiwei

网上看到一篇文章总结了99件（虽然我不明白为什么其实列出了100件，可能是因为99这个数字比较吉利）可以使你成为更优秀的测试工程师的事，
由于PDF文件太大，只能以复制的方式分享给大家。


1. Get to know your customers - Chris George
2. Work first line support for a while - Chris George

3. Never stop learning - Chris George

4. ...and recognize that you will never know everything - Amy Phillips

5. Learn when to automate and when not to - Chris George

6. Question the way you work every day - Kinofrost

7. ... and have the courage to share your findings with whoever is in charge
as well as fight for key changes - Erick Brickarp

8. Pair with developers. - Gareth Waterhouse

9. Test as early as possible - Gareth Waterhouse

10. Remember it is about people. - Tony Bruce

11. Learn to question. - Tony Bruce

12. Learn to explain. - Tony Bruce

13. Understand the business model and business challenges/context before
determining the testing challenges. Its not all clicks and buttons. -Mohan Panguluri

14. Keep your eye on the ball (the end goal) - Kate Paulk

15. Get an understanding of Systems Thinking - Martin Huckle

16. Also get an understanding of mental modelling, the scientific method
and design of experiments - Kinofrost

17. Be critical but do not criticise - Kim Knup

18. Create a MindMap - Rosie Sherry

19. Learn from other Tester mistakes - Mantas

20. True, but learn from your mistakes first :-) - Mauri Edo

21. Attend or even better speak at Software Testing and Programming
conferences (there are free/low cost one that provide great value) -
Stephan Kämper

22. Take the Association for Software Testing "Black Box Software Testing"
course(s) - Stephan Kämper

23. Follow other testers on Twitter - Stephan Kämper

24. Addition to Stephan's suggestion: Follow testers on Twitter is a good
start but make sure you don't stop there. Twitter is a great way to share
ideas and experiences, get feedback and practice your debating skills
not to mention getting in contact with other passionate testers. - Erik
Brickarp

25. For non-native English speakers: Improve your English. For native
English speakers: Learn another language. - Stephan Kämper

26. Teach testing. - Stephan Kämper

27. Learn to program, some lines can help so much - Stephan Kämper

28. Start a test blog - Erick Brickarp

29. And comment on others - Amy Phillips

30. Read Articles, Blogs, Forum posts. - Haplerinko

31. Join an open source project you like as tester. - Erick Brickarp

32. Is "Join Software Testing Club!" taken? I couldn't see it... or maybe it is
too obvious :-) - Geir Gulbrandsen

33.Listen to what your client has to say. This is, by far, the most important
(and underrated) Testing skill, in my humble opinion. - Marcelo Cordeiro Leite

34. +1 for listening. Being really, really good at listening helps you not only
to understand your client, but to pick up on areas where the team is
confused or unsure about what we're building - a slight hesitation in
speech because the dev keeps getting two different entities muddled up,
perhaps.

35. Read the ISTQB syllabus from start to end - then use it as a map of the
box you need to be thinking outside of! - Geekonomicon

36. Do not avoid technical discussions/information - Boipelo Mawasha

37. Every year or 2 - Refresh on basics - Read ISTQB Syllabus, TheTestEye
SW Quality Characteristics, BBST material, etc. again. (Every time you
have different perspective thus gain different insights from same
material) - Halperinko

38. Always use the best methodology invented - Common Sense. Then
choose your testing methodology... - Gil Bloom

39. Build a good relationship with the developers. - David Wardlaw

40. Resist the temptation to go after bogus certifications. Take the risk of
thinking for yourself. I've got 99 ideas on how to become a better tester,
but certification ain't one. - Johan Jonasson

41. Learn how to use testing techniques such as boundary value analysis,
equivalence partitioning etc - Amy Phillips

42. Explore your ideas through blog posts, discussions, or by speaking at
events. Listen to others opinions and use to broaden your own - Amy
Phillips

43. Read the release notes for products you use (or even ones you don't
use), many list the bugs they've fixed. Test whether the same bugs exist
in your product. - Amy Phillips

44. Learn from bugs that end up in production. Try to work out how your
testing missed them. - Amy Phillips

45. Listen. And then form your own opinion. - Amy Phillips

46. Keep your mind open to new techniques and tools - Graham Perry

47. Come up with three ways that your boss, your co-worker, and your
trainee can become better at their jobs ... then apply it to yourself. - Jeff
Lucas

48. Read as much as you can about testing. Then read as much as you can
about things outside of testing; product design, software development,
psychology, anthropology etc - Amy Phillips

49. When you analyse a system, don't forget the parts of it that are not
made of code, but living, breathing, fickle, forgetful, quarrelsome,
cooperative, adaptable, lovely human beings. - Anna Baik

50. Explore the system!! - Vishu Udayan

dengcainiao

谢谢分享！！！

萧小先生