Mark Bland
Senior Test Manager
Premier Farnell

Professionally: I’m a Senior Test Manager with 12 years of experience working in Manual, Automation and Non-Functional test teams of which 8 years has been in leadership roles at all management levels. (Currently managing Manual/Automation & Non Functional Disciplines).

I moved into testing from a 1st line Product Support role at Premier Farnell which I held for 5 years, this was preceded by 8 years of working as an Electronic/Electromechanical engineer in many different areas of the industry. As a service engineer I learnt many of the skills and principles which lead to me being successful as a tester (Diagnostic skills and quality principles), in fact a lot of the regulations and standards I worked to as a service engineer are the same standards that govern software testing today.

Personally: I’m both a Dad and a Grandad, I love travelling and experiencing life and other cultures and have a number of hobbies, (Including but not limited to) Teaching and training in Defensive Tactics/Unarmed Combat, Music (Playing and listening to), Photography, Reading and many other things there simply isn’t enough time for. Basically I’m a pretty busy guy.


Starting from scratch (Outside looking in.)

Where do you begin when starting your own in house testing team What are the pitfalls, what are the fundamental principles that create  solid foundation? Do these principles apply when you are overhauling an existing team. Should all new test teams be Dev-Ops Testers (SDETs) or will this model simply not suit some companies.?

Key Takeaways:

  • Simplifying the process of setting up test teams.
  • Building a team that works for my company
  • Is Dev Ops the Only Future..?
  • Is it possible that some companies simply wouldn’t benefit from Dev Ops (Or are they just not approaching the implementation properly?)
  • Is Dev Ops a tool box from which you can select relevant elements discard the rest?