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

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

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

he icon   en icon

שגיאה
  • JLIB_FILESYSTEM_ERROR_PATH_IS_NOT_A_FOLDER_FOLDER
  • JLIB_FILESYSTEM_ERROR_PATH_IS_NOT_A_FOLDER_FILES

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

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

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

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

  • Check the Effectiveness of Your Automated Tests

    Check the Effectiveness of Your Automated Tests Have you ever found yourself working on an automated test suite and wondered if it's worth the effort? It's probably a typical thought that goes through the minds of every developer and tester working on test automation. Even in all of my years of building and maintaining automated tests, I admittedly find myself thinking this way occasionally, wondering if there's a better use of time elsewhere on the project.Whenever I notice teams of developers and testers not putting any emphasis on test automation, it's usually because there's a level of uncertainty in the effectiveness of automated tests. The team might think it would help their work but can't or won't dedicate some time to know for sure. Worse yet, some teams believe that test automation is an added burden to the software development and testing process with little to no reward. These developers and testers proceed with the belief that they can deliver quality work faster by skipping these types of tests.Even teams with a solid test automation strategy in their workflow have some reservations about the effectiveness of their test suite. They can't figure out how to gauge the success of their testing work and try to find ways to measure it, like counting the number of automated test cases or keeping track of code coverage. While these seem like good metrics, they're not as valuable as you might think.If you're in a team trying to determine if your test automation work is worth the effort, how can you[…]

    30.11.2021 | 5:00 קרא עוד...
  • “Spring Testing Tips” Webinar Recording

    SPRING IS HERE! Well, not really. Well, according to my window it looks like it, but the calendar says otherwise. But the recording of the Tips for Spring Testing webinar is here. In fact, it’s just below. Check it out! Oh, and if you’re interested in some training on these topics, let me know! The post “Spring Testing Tips” Webinar Recording first appeared on Everyday Unit Testing.

    30.11.2021 | 2:27 קרא עוד...
  • What testing does your team do that is Lean?

    What testing does your team do that is Lean? We want to find bugs as early as possible so that the cost of fixing them is as little as possible. The earlier a bug is found the cheaper it is to fix. If a bug is found and fixed in a specification before any code is written then it costs very little to fix. If a bug is found during development then it costs some development time to fix it. If a bug is found in production and fixed then the cost to fix it includes some development time, some customer service time and its effect on customers. A lean perspective expresses this in another way as lean is about reducing waste and improving the flow of work. Bugs are waste so finding bugs early is lean because it reduces waste, and so improves the flow of work. The value of testing as early as possible was highlighted by Tom Gilb when I heard him speak about ‘Lean QA’ a few years ago. He spoke about how it is best to find issues as early as possible in development. The advantages are clear in theory and it is helpful to be able to give examples. Tom Gilb spoke about inspecting specifications for software before code is written as an example of early testing and showed how many issues can be identified by inspecting the specifications. One way for testers to help with inspecting specifications is to review requirements with a developer before they start work as this may identify[…]

    30.11.2021 | 2:10 קרא עוד...

טיפים

  • הכירו את לקוחותיכם
    הכירו את לקוחותיכם הכירו את לקוחותיכם "הכירו את לקוחותיכם" למרות שמשפט זה נשמע דיי טריוויאלי והרי אנו כבודקים אמורים לדעת כי "אנו מייצגים את הלקוח בפני הארגון" הרי שבמרבית המקרים יש עוד הרבה מה לעשות ולשפר בנושא. האמת היא…
    קרא עוד...
  • אל תגיד "אוטומציה זה למומחים באוטומציה"
    אל תגיד "אוטומציה זה למומחים באוטומציה" אל תגיד "אוטומציה זה למומחים באוטומציה", הכל מתחיל בך! - שאל את עצמך על אילו פעולות אתה חוזר יותר מ-5 פעמים ביום? וכיצד תביא לכך שלא תצטרך לעשות זאת שוב?   טיפים מחברי ITCB-AB
    קרא עוד...
לרשימה המלאה >>