LOGIN
התחברות או הרשמה
Avatar
להמשך הרשמה ידנית – לחץ על כפתור ההרשמה, להרשמה/כניסה מהירה בעזרת חשבון רשת חברתית – לחץ על הלוגו בכותרת

אפס סיסמה - שכחתי את שם המשתמש

שם משתמש
סיסמה
זכור אותי

he icon   en icon

בכדי להוסיף פוסט בבלוג יש להרשם או להתחבר - ההרשמה/כניסה מתבצעת מכותרת האתר.

Tester - tired of your job?

נכתב על ידי 
ראשון, 19 פברואר 2017 07:19
דרגו כתבה זו
(7 הצבעות)

Tester - tired of your job?

bigstock Portrait Of Tired Young Busine 41087092

If you are a regular visitor in high tech forums, chats and facebook groups, you must have read the amount of opinions saying QA Engineering is boring.

Sadly not all QA engineers are in this profession out of love for testing. Some see it as a transition point for becoming a programmer and feel like they have compromised, while others admit that they have become bored and frustrated of their daily work and routine.

But, is testing really boring?

Every time I'm asked that question I always say that it depends on how lazy you are. In my opinion - testing is a highly interesting profession that demands from us the ability to open our minds, use our imagination and always learn new things.

If you are a lazy person who does not like to challenge yourself, exploring, thinking creatively and acquiring new skills, if you don't have the passion for always learning new technologies, do not get your personal and professional satisfaction from searching and finding bugs and defects, then testing is not for you.

With that said, every job has its down sides and it is not always an exciting and thrilling job. When the learning curve is saturated, testing does have its monotonous aspects like executing the same test cases and writing repetitive reports.

So, how do we keep the motivation flame burning? Here are some things I do to stay motivated:

·         Learn- people get bored when they are not challenged in their everyday routine. I am always passionate of learning new things. Most testers get about 2-3 hours a week as their free learning time. Use it to hit the internet in search of information. New automation tools, testing tips and methods, instructional videos and courses to improve your coding knowledge and technical skills.

·         Attend regular meet-ups conferences and workshops – try to attend in as many meet-ups as you can. In addition to the valuable knowledge you will acquire, you will meet interesting people and hear about how they manage their time and tasks. Connecting with other testers, sharing information and knowledge and just chatting with someone from your field of work is always a positive experience.

·    Guide and instruct your team members - there is an old saying: "If you cant explain it in a simple way that means you don't understand it yourself". Teaching others is a great way to develop your own skills and deepen your understanding.

·         Automate your recurring tasks – incorporate automation into your work process. Automating recurring tests is a very positive way to take the load off the manual tester and it is a great way to grow professionally and acquire highly important skills. It is also a good way to break the routine.  Suggest it to your management- it could be your initiative and work in your favor in the long term.

·         Stay away from negative people - People observe behavior and atmosphere from their surroundings, so my advice is to surround yourself with positive people that are not frustrated and still passionate about their work.

·         Set long term goals- What are your carrier goals? Where do you see yourself in 5 years? Set clear long term goals and make everyday count as you work your way to them.

·         Write about your work – Testing is a very wide field of work and every company has its own specialization. Write about your experiences, the challenges you face at work, tools you work with, write "how-to" guides and instructional articles so other testers could learn from your experience. Sharing information can help others and the feedback you will receive could help you deal with you own challenges.

·         Talk to colleges from different companies and organizations – Hear how they work, learn about different work methods that could inspire your team, tools that can make your work easier and more versatile. Updates from the industry can work magic to your own testing performance.

·         Don't get stuck in a bad place – If you feel like you are fed up, unappreciated or if you feel that you are "marching on the spot" carrier wise, try finding another work place. I always say that no amount of money is worth going home frustrated.

 

 

שונה לאחרונה ב ראשון, 19 פברואר 2017 09:20

חובה להיות משתמש רשום במערכת בכדי להגיב - ההרשמה/כניסה בכותרת האתר

חדשות מעולם הבדיקות

  • 75: Modern Testing Principles - Alan Page

    Software testing, if done right, is done all the time, throughout the whole life of a software project. This is different than the verification and validation of a classical model of QA teams. It's more of a collaborative model that actually tries to help get great software out the door faster and iterate quicker. One of the people at the forefront of this push is Alan Page. Alan and his podcast cohost Brent Jensen tried to boil down what modern testing looks like in the Modern Testing Principles. I've got Alan here today, to talk about the principles, and also to talk about this transition from classical QA to testing specialists being embedded in software teams and then to software teams doing their own testing. But that only barely scratches the surface of what we cover. I think you'll learn a lot from this discussion. The seven principles of Modern Testing: Our priority is improving the business. We accelerate the team, and use models like Lean Thinking and the Theory of Constraints to help identify, prioritize and mitigate bottlenecks from the system. We are a force for continuous improvement, helping the team adapt and optimize in order to succeed, rather than providing a safety net to catch failures. We care deeply about the quality culture of our team, and we coach, lead, and nurture the team towards a more mature quality culture. We believe that the customer is the only one capable to judge and evaluate the quality of our[…]

    23.05.2019 | 2:00 קרא עוד...
  • Five Blogs – 23 May 2019

    The (best) five blogs I read today. Check them out. Change management in the agile world – Getting ready for WAR Written by: Dianne Inniss Product Roles, Part 6: Shorten Feedback Loops Written by: Johanna Rothman Why I Am a Tester Written by: James Bach Seven Issues Testers Experience Being Agile Written by: Thomas Cagley Defining Observability For Robotics Written by: Ian Sherman Quote of the day: “We are products of our past but we don’t have to be prisoners of it” -Rick Warren You can follow this page on Twitter

    23.05.2019 | 1:20 קרא עוד...
  • Testing Culture – Excuses, Blame and Fear

    I came across an interesting article which discussed common excuses that testers make:http://thethinkingtester.blogspot.com/2019/05/seven-excuses-software-testers-need-to.html There were 3 which I found particularly worrying: The other tester on my team missed the bug If I log the bug I found in production, I’ll be asked why I didn’t find it sooner. There wasn’t enough time to test If a tester needs to use these excuses, then the issue might not be with testing but with the company culture. A company culture where colleagues are encouraged to make excuses, attempt to shift the blame on someone else, or instil enough fear so someone is afraid to report something critical is not a good one. “There wasn’t enough time to test” This particular excuse will always exist and it is a valid one. There will be strict release deadlines which can’t always be pushed back. When the software has to be released, it has to be released. The tester has very little control over this. However, it doesn’t mean that the tester is entirely blameless if a critical bug makes its way to live. It is the testers responsibility to ensure that the tests are optimised and prioritised. Tests covering the most essential features should be run first. Tests should also be optimised so that they are run as quickly and efficiently as possible. Occasionally, the tester may be in the unfortunate situation where there isn’t enough time to test even the most essential features. It is also the testers responsibility to communicate what the[…]

    22.05.2019 | 11:30 קרא עוד...

טיפים

לרשימה המלאה >>