Today we welcome back our popular guest author, Renée Mineart.

There are many, many challenges in developing and delivering a successful application. That’s what makes it interesting, if you ask me. One of the greatest of these challenges, in my experience, is time management (apart from a planet wide pandemic of course!).

Today, I’d like to blog about mobile testing. Like many of you out there, I am a frequent mobile user and I would feel considerably inconvenienced were I to be without it for even just a few hours!

The market is flooded with mobile hand-held devices and we rely so heavily on them for so many reasons: communication, diary bookings, notes, reminders, security and protection, emergencies, socialising, learning, entertainment, sleep, relaxation and so on.

Today’s blog is about pet 'computer experience' hates, ’Better out than in!’ so they say. Let's refer to it as my ‘Testing Room 101’ target list. 

The reality is, these are experienced by people across the board and not just software testers, of course! Perhaps the line of work of a software tester makes them more noticeable or perhaps they subconsciously look for them. There’s nothing like a good rant to get things off your chest when things are annoying, so here goes! How many of these are on your pet hate list?

Today we welcome back our popular guest author, Renée Elizabeth Mineart.

If I were asked to encapsulate what makes humans unique in a single sentence, I’d probably say: “...our ability to achieve the impossible.” This trait is often best demonstrated when we are faced with adversity - a planet-wide pandemic, for example.

What is SAFe?

SAFe is a framework which combines various pieces of different agile methodologies and principles such as Scrum, Kanban, Extreme Programming (XP), Lean and DevOps.

Why use SAFe?

Today we welcome back Jane Kelly who dives into the fascinating world of Track & Trace.

Track & Trace has been heavily reported on in the news and it has made me think about some of the synergies with Software Testing. Tracking can be thought of in terms of the emerging path of what is being analysed, where its current state is, and where it is likely to end up. Like testing, tracking requires many different measures to provide value.

Today we welcome back our popular guest author, Renée Elizabeth Mineart.

Welcome back to my series on how to successfully deliver a failed project. If you’ve not read the introductory blog post yet, it can be found here. We left off talking about communication and I’d like to dive a bit deeper into this topic if I may.

Today we welcome back our popular guest author, Renée Elizabeth Mineart.

It has taken me a considerable amount of time to get my head around this topic. I’m not sure, even now as I place fingertips to keyboard, it is the right direction for this blog. But I think it’s an important topic to cover and is perhaps not talked about often enough. So, I ask you to please, bear with me as we broach the murky waters of … (queue dramatic music) … Project Failure. 

In my last post I discussed how a Testing Centre of Excellence can reduce cost and create efficiency in an organisation. In this post, I will discuss some of the other benefits of a TCOE.

A Testing Centre of Excellence can:

• Increase test maturity and promote innovation across the organisation
• Define, encourage and enforce best practices
• Define test policy and test strategies aligned with the business needs

What is a Testing Centre of Excellence?

A Testing Centre of Excellence (TCOE) can be many different things with different objectives and its scale and reach will vary from company to company. Generally speaking, it’s an internal organisation that provides various testing and testing related services to its internal customers. Although internal, it can be set up and delivered by a third-party external organisation. The TCOE can be onshore or offshore and geographically dispersed but, by definition, will always be managed centrally.