ABHcardsBlogQA/Test Automation

ABH Card #7: A (Mon)day in the life of a Test Engineer

By May 7, 2018 May 17th, 2018 No Comments
Morning Glory

Monday being Monday, it’s usually packed. First up, I catch up with emails and messages that have accumulated over the weekend, along with the major codebase changes that have been merged, and after that, head over to the daily Scrum meeting. Ideally, you start application deployment jobs before the Scrum, so that features are ready for verification after the meeting.

Mid-day Details

After the Scrum, I work on reviewing any minor changes to the current feature in development. For me, it’s all about details and offering a different perspective when looking for problems not obvious to others. If there are no major things for me on the Scrum board, I handle pull requests. Review of PR-s opened by others is a process of understanding someone else’s line of thought, and you have to look at it in great detail. Nobody likes junk on the master branch. When approaching such things, it makes no difference whether you are reviewing someone else’s product or making your own. I focus on the details and try to understand the core of the problem. This helps me make less mistakes. I always go over my work at least twice; whether it’s a new test case, automation script, new PR review, email or something else. Besides checking that everything is as it should be, I try to think from as many angles as possible on the produced material, to see if it makes sense to everybody that will use it. That gives me an additional perspective. Once I feel like everything checks out, I present it to others.

Time for Self-Development  

After lunch, I escape from my colleagues so that I can fix major things on my PR-s and produce new tests, if there is time. Sometimes, you need solitude to concentrate and that is part of the daily grind, so you can improve your own skills and contribute more to the project and the team. Recently, my team started a new project that included joining existing remote teams (devs, QA, DevOps guys and managers). We had to comply to existing technologies so we could start working on the huge existing codebase. I never worked with JavaScript, Jasmine and Protractor in test automation, so I had learning to do. The stack has its quirks and a different way of thinking than others I used in the past, along with other pros and cons. Obviously, I made sure I had time to learn this and improve my skills to be ready to tackle new challenges at full speed. Today, I can proudly say that I am richer for another technology stack, another way of thinking and another experience.

By the end of the day, I can say … Monday’s aren’t so bad.