For many of us, these are “testing times” indeed. In the run-up to 2020, there was a sense of optimism about the future. Businesses were working harder to achieve a good balance between in-store and online, with a lot of focus being put on harmonising the two. There were big projects on the horizon. Investment in technology was ever-increasing. And Coronavirus or COVID-19 was creeping into the headlines…

Digital IT is an ever-changing world. Often described to me as “the place to be” in terms of my career, the last 8 months have shown that IT, Digital and Ecommerce really have paved the way for a step-change in how we shop and interact with businesses. Many companies have had to rapidly accelerate their shift towards digital and digital strategies, as physical stores were impacted by closures, social distancing, and restrictions since the first lockdown in March. As we at Eclipse recognise, shopping trends are changing, and technology is essential. Ensuring we are delivering rapidly, but maintaining high levels of quality is as important as ever to maintain customer satisfaction, and to lure perhaps hesitant customers into this new digital era.

In these testing times, we talk now more than ever about needing to deliver quality solutions, but as we know quality is often sacrificed when time and cost are a greater factor. So how can we adapt our software testing practices and align with the changing world of digital? Here are some top tips for making Testing work harder within your organisation in the right ways.

 

Test Early!

There is a lot written about testing early and a lot to be said for the benefits of it. “Static analysis” or “testing a work product without the work product code being executed” is a useful testing phase that is often neglected. The word static itself implies that nothing is moving or changing and when there is an urgency to deliver, the focus is often to get cracking with the development and ask questions later. But taking the time to fully understand a requirement, by thinking and talking scenarios through, can result in less rework at later stages in the development lifecycle (after testers have found the coded defects). As testers in Eclipse applying Agile methodologies, we utilise our static testing skills during product backlog refinement sessions, collaborative discussions with developers and analysts, asking the right questions (my personal favourite is “what if?”) and detecting defects early before they have been coded!

 

Try “Trifecta”

The Trifecta also referred to as the Three Amigos, is a name given to the 3 roles of an agile team who will discuss, refine, groom, enrich and identify the best solution approach for every Product Backlog Item (PBI) taken into a sprint – Analysts, Developers and Testers. By involving the right individuals from multiple disciples in discussions about solutions and keeping the communication channels open throughout makes a HUGE difference. Having Trifecta sessions including analysts or owners of the requirements prompts discussions on differences in understanding, fuelling our test early principle and saving time and cost throughout.

 

Prioritise!

Everyone wants to have the most beautiful fully functioning website. As software testers, it is in our nature to strive for the best, but we know that this takes time. At Eclipse, we know that prioritising our effort based on factors agreed with our product owners and teams can make all the difference – the age-old debate of breadth vs depth of coverage. We ask about the MVP, we calculate risk and we focus our efforts where it matters. This allows us to be confident in quality levels whilst supporting building the backlog of improvements to be tackled over time.

 

Test!

This might sound strange in a blog about testing, but don’t neglect or underestimate the benefit of any form of testing. Done in the right way, testing can save time and effort in the future, and ultimately could be what protects your reputation. I have seen first-hand how neglecting testing effort can then go onto have the butterfly effect – it can take one customer or end-user to find something that affects their experience, and damage limitation has to come into play. At Eclipse, testing and quality assurance is a default part of our services. We give it the attention it requires and deserves (whilst prioritising our efforts of course!)

 

Automate!

Look for ways to complement your manual test cases, reap the benefits of reducing the repeatability and allow your testers to focus on testing more complex cases; those which often require more thought and are perhaps exploratory in nature. At Eclipse, by automating those repeatable but critical tests based on factors such as those with high business value or functionality where the level of regression and defect rates are high, we have helped our customers to move from irregular large releases to regular iterative releases. A little investment goes a long way; the investment in the short term pays dividends in the long term by increasing manual testers efficiency and effectiveness.

 

If testing is something that you feel needs a little more attention, speak to us about how Eclipse can help you with your Testing approach to ensure you are getting the most out of your processes, tools and teams.