Skip to main content


Showing posts from September, 2017

Continuous Testing On Our Pipelines

I’m going to assume that I’m not the only one who has had hours of discussions around how much automation to plug in to our pipelines.
Firstly, I want to briefly talk about different environments and what I believe they should be used for. I’m going to keep this high level as I don’t want to make an assumption on what environments your pipeline will consist of.

Each of these could be made up of multiple environments. For example, ‘Test’ could suggest you have Local Dev, Integration and System Test. ‘Live’ could suggest you have Client Test, Live and Disaster Recover, but they would fall in to the categories I have illustrated. 

Test Environment(s)
I see test as being the environment where all new functionality is tested whether that be isolated components or end to end. Testing can be automated where appropriate and added to the products over all regression pack. Accept that in test you may need to apply an element of mocking as it’s not always possible to test external third parties…

The Software Testers Job Title... Meaningless!

Question: What does a “job title” actually mean?
Answer: A job title is the name used to describe a specific group of tasks performed by an individual for a business or another enterprise. A job title is an efficient way to tell what a person does.
Phil’s Answer: Nothing
As a software tester, does a job title really identify what you do day to day? Probably not!
Now – you are looking for a new role because your company just made you redundant, you go and search on a recruitment website with the search criteria of “Test” and get thousands of results?!?!
How many different job titles could you possibly uncover?

Test Engineer (and Test Engineer II, Test Engineer III, etc.)Quality AnalystTesting AnalystAutomation EngineerTest ArchitectTest Automation DeveloperTest ManagerDirector of TestSenior Test Engineermany, many more…
If you had to define your job title based on what you actually do what would it be? I think mine would be something along the lines of:
“Software Exploring Testing Mento…

Recruiting Software Testers… It should be easy, Right?

Recruitment, A process that I know is painful for the recruiter and candidate(s). So how do we get this right? How do we know we are asking the right thing to ensure any candidate is right for the job but also the role is right for the candidate? 1 hour/1.5 hours isnt a long time to make a decision.
After many exhaustive hours dealing with recruitment over the past 18 months or so I don’t believe I am perfect at it but I do feel I have learnt a lot about what I am looking for.
Stage 1, The Phone interview: 

This stage of an interview should be kept to a minimum, a brief discussion of experiences.

I generally use the phone interview to pick up on 5 key points:
 - Have they done any research on the company/role  - Why they want to make this move  - What methodologies have they worked with  - Manual and automation experience  - How they keep up to date with modern testing techniques
I want to ensure that they are committed to the application process, they have worked in a similar environment and u…