I thought it might be interesting to some people to start doing some posts about my day to day job as a QA Lead! I often get asked what it is that I do, how do I do it, what skills are important and just what is difficult about the job, so what better way than to just start a diary documenting all of this!?
In writing this, I've figured it would be a good idea to get others to do the same across the different levels and teams, as we very often get asked in interviews "What will my day to day role be?" So hopefully this will serve as a useful piece of information.
So lets begin (on a Friday as this idea came to me on a Friday!)
Friday June 17:
8AM : It's Friday, and it's Summer, so you know what that means (or maybe you don't, but you will now)... It's Summer hours here! So a 3PM finish today! I got in early today to make up for the England game yesterday where no work was completed for obvious reasons (what a result!), I have to catch up on emails as well as trying to get a solution to build and run some automation before an Automation Deep Dive that I've booked in with one of the Senior QAs here to see what they're working on and to see if there can be any improvements.
He's already taken the team through what he's done at a high level, but I want to go deeper and see what improvements can be made. Already after the last session I feel it would be beneficial to go over BDD & SpecFlow as well as taking the entire team through a Test Planning workshop to get everyone talking and communicating. Right now it seems like the Automation that he's worked on is just worked on by him, I want to change that and get the whole team on board. Hopefully the workshops I've arranged will help with that.
11AM: left my desk to go to another meeting, but got grabbed en route and ended up participating in some swarming on some failing automation by one of the 10 teams that I help which was pretty cool to see and be a part of! (So the meeting had to happen without me, but it was worth it!)
Midday: We also had a review of some End to End tests for a major project that's going on, it's being done by a single team, so it's important that we as Leads have overview as the project touches a number of areas that we all look after. It's good to see progress being made and whilst I disagree with the reasons why we're doing it, it's important that it's done right and is easy to maintain going forward by everyone involved.
We also discussed about having checks for the API & UI as part of one test suite, which I'm not a big fan of, it will increase the feedback loop of the API checks, as well as making the overall suite flaky. I'd rather have them as 2 seperate packs, and if the API fails we don't run the UI... So watch this space in that regard as we are going to discuss it next week.
1PM: Time for lunch so I went out for a quick walk in glorious sunshine, sometimes I'll take a packed lunch, but either way it's lovely to get out of the office! Had a catch up with someone about Test Data and how we can manage that for teams Integration Testing for one of the big releases that is coming up soon.
2PM: Final meeting of the day, but it's a celebratory one and one that is in good spirit for a team that's been working hard and met some really tight deadlines, so the update is good, and it's more of an update for the other teams on what's going on and what's happening. It's nice to see such a big group of people come together and pull all in the same direction in achieving something for the greater good.
3PM: Home Time! Whilst on the way home I send out meetings for the workshops that I want to do, so hopefully people can make them!
So today has been largely been spent in meetings, working with people to help them improve and just facilitating conversations between people and ensuring that we're following a good path when it comes to Testing & Engineering, which can be difficult when I have so many teams, but it's important to have strong Seniors within the teams and platforms who can help with the load.