14. 管理你的时间
我们的时间很容易被大块的工作和不断的会议所占据，导致我们没有时间去学习，去深挖更多的Bug，甚至没有时间保持健康的生活状态。为了避免透支，你需要学习如何管理你的时间。
15. 明智地选择测试自动化
自动化测试可能缺乏熟练测试人员的那种“余光视力”。不正确的自动化有时会变成一推庞大而难以维护的代码，并且对衡量软件质量没有什么实际意思。但是精心设计的自动化测试有助于及早发现软件缺陷。
16. 提高你的编程能力
我遇到过一些很有天赋的测试人员，他们倾向于不去写代码。这有一定道理。就像电影评论家在变得挑剔而富有陈见后不会去考虑电影观众的喜恶一样，在我充当编程员的角色时，我想的就不再和用户一样了。但是编程还是一项有价值的技能，他能帮助你更好地阅读代码，理解产品的内在，同时帮助你写一些小工具使得平淡反复的工作变得简单。
17. 参加Bug的审阅 （Triage）
在产品发布前的最后一些日子里，Bug审阅组开会决定哪一些Bug应该修复，哪一些应该留到以后的版本去修复。如果你通常不在这个会议的邀请名单中，那么去主动要求参加。你会看到在测试员信誉，用户影响和已知风险等因素间做出折衷决定的过程。这将会是一种非常有趣的经历。
18. 不断学习
不管是“软技能”，比如公开演讲， 或者编程语言，亦或新的测试技术，成功的测试工程师总是会从繁忙中抽出时间来坚持学习。
19. 爱你所做的事，并把它做好
如果你不能承担放弃当前工作的代价，那么就学着去热爱它。测试人员有时会变得嫉世愤俗，尤其是在困难的发布周期中。享受工作并且不满足于仅仅完成计划内目标的人才会成为优秀的测试工程师。
译者：如果你能坚持做好以上这19条，你一定能成为一名非常出色的测试工程师。
附英文原文：
I started to make a list of 10 tips I'd give to junior software testers. But then I saw a talk by Ben Huh , of lolcats/icanhascheezburger fame. Ben made the point that, with the internet, content is free, but the organization, editing, and presentation all require skill. Inspired by Ben and the cheezburger franchise, I asked 60 successful testers to each provide 3 tips they'd give to a junior tester. I received tips back from more than 40 of the testers, and ended up with a list of more than 100 tips. To respect their privacy, I won't provide the verbatim tips here, but I did find it interesting that there was a lot of commonality and the tips were collectively much better than what I came up with. I grouped the collected testing tips into these 19 themes.
1. Focus on the customer Keep the customer in mind when testing. Develop empathy for their needs. Talk to customers and observe them using your software.
2. Read bugs If you work with a group of testers, read all the bugs they log each day, especially any logged in the area you're testing. You can learn a lot from how other testers approach bug finding.
3. Read code Find the code that implements your feature. Even if writing code isn't your thing, reading code critically helps find potential boundaries and flaws.
4. Take pride in your bugs Bug advocacy starts with a well written bug title and description. I re-read the bugs that I log to assess whether they are fair and properly detailed. For important bugs, if they aren't getting fixed, be the driver to make sure the right decisions and tradeoffs are being made.
5. Get involved in your feature's design Before code is written, find out about the planning and get involved while big changes are still possible. This also helps to understand the tradeoffs and compromises that are being considered.
