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

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

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

  • Day 6: Read and share an interesting blog post on API testing.

    Day 6: Read and share an interesting blog post on API testing. Yet Another Challenge! Ministry of Testing got us 30 days Testing Challenge.This time topic is on API Testing.Challenge Link:  https://www.ministryoftesting.com/dojo/lessons/30-days-of-api-testing  It has been long time I have worked on API Testing, after learning from API Testing Dojo (year 2015).Sixth Challenge is Read and share an interesting blog post on API testing.          Sharing will enrich everyone with more knowledge.I will actually share couple of posts which help in learning. a. Danny Dainton's GitHub Post on All Things Postman - https://github.com/DannyDainton/All-Things-Postmanb. Recent blogpost by Anne-Marie Charrett - https://mavericktester.com/2018/11/05/rest-apis-written-by-women/This blogpost includes collation of posts written female software craftspeople.Please do check out them, there are plenty of interesting blogposts.Ministry of Testing Discussion Thread:  https://club.ministryoftesting.com/t/30-days-of-api-testing-day-6-interesting-blog-post-on-api-testing/19595/18

    14.11.2018 | 11:23 קרא עוד...
  • 30 Days of API Testing – Mock, Stub, Fake

    Today’s challenge is about explaining mocks, stubs and fakes. I don’t know if I can pull it off. The problem is, different teams will use these words in different ways. I don’t think it makes a lot of sense to argue about what exactly each of them means and how they are distinct from each other, but there is some value in at least understanding the general idea that these terms are meant to communicate. In the broadest terms, when we talk about these things we are talking about something that is a substitute for a piece of production code. For example, we might have a database that stores some values. When running tests though, it might expensive to go retrieve those values many times, so instead we might make a local text file that has a few of the values we care about hard coded into it and just use that instead of the ‘real’ databases. No matter what term we are talking about – mocking, stubbing, faking, etc. – what we are doing is using something that is not the production code to simplify in some way what we are doing for our tests.  This helps us isolate things to just the specific part of the code we are interested in and can be used in some really powerful ways. I wouldn’t worry too much about understanding in an absolute sense what these various terms means. What matters in figuring out what they mean in your context. How[…]

    14.11.2018 | 9:48 קרא עוד...
  • Quality is the Responsibility of the Whole Team

    Originally this article was postet on trendig.com English & Deutsch Since 2001 we have the agile manifesto in place and since then the whole industry is learning to use agile principles and values in their daily work of software development.   agile manifesto One of the problems I see, is that many who claim to be … Continue reading Quality is the Responsibility of the Whole Team

    14.11.2018 | 5:23 קרא עוד...

טיפים

  • איך לכתוב בדיקות שישמשו אתכם גם בעתיד?
    איך לכתוב בדיקות שישמשו אתכם גם בעתיד? איך לכתוב בדיקות שישמשו אתכם גם בעתיד? אל תסתפקו בכתיבה יבשה של צעדי הבדיקה ותוצאות צפויות – סגנון כתיבה כזה יביא אתכם למצב בו בעוד מס' חודשים אתם או מישהו אחר שאמור לבצע או לשכתב את…
    קרא עוד...
  • בודק - למד להסביר
    בודק - למד להסביר בודק - למד להסביר – כבודקים אנו נאלצים להעביר הלאה מידע רב בשלבים שונים של עבודתנו, החל מהסבר על התקדמות ומצב משימת הבדיקות שלפנינו, דרך הסבר מהות הבאגים, מקורם, חומרתם והשלכותיהם. מעבר לכך פעמים רבות אנו…
    קרא עוד...
לרשימה המלאה >>