Two MoTacon attendees are on the left. The MoTaacon logo is in the center, and to the right a prompt to Get Your Ticket.
Favourite Three Tools with Neil Studd thumbnail

Favourite Three Tools with Neil Studd

Often when we're testing, or writing automation, our goal is to define the current working state of an application, and detect when a change occurs. However, you don't necessarily need a full-blown automation framework or expensive off-the-shelf products in order to achieve this.

There are low-code and no-code solutions which can be configured to run seamlessly in the cloud, and even some tools that can run on internal networks or applications which are hosted purely on your machine. With the power of these tools at your fingertips, you can go on the offensive by detecting problems at the first moment that they occur.

Or if you're currently experiencing problems with an application defect, site downtime or a repeatedly failing build, you can prevent wasted time by creating a monitor which alerts you as soon as the problem is resolved.


Comments

Sign in to comment
Explore MoT
Influence, from the other side of the table image
What I learned about influence by becoming a stakeholder
MoT Advanced Certificate in Test Automation image
Ascend to leadership roles by mastering strategic skills in automation strategy creation, planning and execution
Into The Motaverse image
Into the MoTaverse is a podcast by Ministry of Testing, hosted by Rosie Sherry, exploring the people, insights, and systems shaping quality in modern software teams.
Subscribe to our newsletter