Favourite Three Tools with Neil Studd
-
Locked
Neil Studd
Software Engineering Coach @ Makers
Talk Description
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.
By the end of this session, you'll be able to:
- Get examples of multiple tools which can be used for change detection, and how they can send email/Slack notifications, or write information to file.
- How to evaluate tools with similar feature sets, to establish which is most appropriate for your current context.
- How you can utilise such tools for personal projects, for instance allowing you to detect when products arrive in-stock, or when event tickets go on sale.
Suggested Content
