How to qualify for Global Software Testing Awards?

You will need to become a finalist in the European Software Testing Awards, North American Software Testing Awards and/or Asia Pacific Software Testing Awards. As long as you have been a finalist over the past 24 months you are eligible to enter the Global Software Testing Awards.

If you have qualified in one or more of the above please log into your account, if you have any issues logging into you account please get in touch.

Entering the Awards is a huge deal, and many amazing projects are reviewed every year. If you want to learn more about the entry process and behind the scenes, please see below:

Entries open on the 2nd March 2026, and they close on the 25th January 2027.
During judging week, a category or categories will be allocated to the most relevant judge based on their job function, experience, and/or request.
Judges have a week in which to mark, review and send back all scores and feedback in advance of judging day. They use a scorecard like the one below.
To make it through to the finals a minimum score must be achieved – if the minimum score is not reached the journey ends for that entry/company.
Judging day is a collective meeting involving only the judges in a virtual/online location. The shortlist of the top two scoring entries across all categories is reviewed and all judges unanimously decide what entry is the winner.
Finalists are usually announced a day after judging day and the winners at the gala dinner, 24th March 2027.

Tips for a successful entry

Strong Entries

Emphasised the business importance and criticality of the project, and identified what was innovative about the approach being adopted.
Shown the biggest number of traits/characteristics one would expect from someone with good people management and communication skills: Mentorship (not only for people within his company), Coaching, being a role model, being approachable and supportive, being valued-respected-listened by people, dedicated to being team well-being, focus on skilling people up.
Evidence of overcoming challenges was clear, entries also described how they were committed to best practices and their selection of methodology to support their automation objectives along with evidence which made their application stand out from the rest.
Cleary researched and implemented the best tech to test ALL the system, NOT just the software–based backend systems.
There is very clear evidence of the project methodology and justification of tech choices. Very clearly a detailed description of understanding the Stakeholder’s needs, the importance of the project and the overall Goals.
Give context to metrics to fully justify their inclusion.

Weak Entries:

Weak entries were not able to describe challenges very well, talking about business, project, or architectural challenges – rather than challenges in their automation journey.
Did not cover all the criteria defined, which made it a slightly weaker application.
Lacked details around the approach to testing. The diagram summarised tools used but limited detail on what challenges were encountered and how those were overcome through the use of automation.
Not demonstrating evidence of delivering on time, within budget or engagement with stakeholders, nor reflecting on goals to establish ultimate project success.
Concentrating on the merits of the tool or method rather than the actual project deliverable is less likely to be scored highly.
Not justify the reasoning behind including metrics.

Need help? Give us a call on +44 (0) 203 931 5827

How to qualify for Global Software Testing Awards?

Entry Process

Tips for a successful entry

Strong Entries

Weak Entries:

Media Partners