March 2016 Summaries

The idea behind Fragile Automation's User Interface (UI) testing is to automate some UI tests to ensure an application behaves as expected. However, issues such as unstable infrastructure, environment settings, and tool or library versions can cause problems. To address these issues, it's essential to consider the architecture of the testing framework, use isolated tests where necessary, and prioritize back-end stability. Additionally, timing issues and knowing what tests to run are crucial in maintaining a stable test suite. By focusing on UI components and business logic, teams can strike a balance between testing every possible scenario and avoiding unnecessary complexity. With proper planning and implementation, automated testing can provide significant benefits over time.

There are several strategies for getting started with automation in test environments. A strategy should aim to focus on the spirit of a goal rather than an arbitrary value, as setting a random goal can lead to ineffective tests and a lack of tracking. The "80-20" rule suggests focusing on areas that cause most bugs, allowing teams to optimize their resources. Focusing on customer-reported bugs can also help prevent recurrence of issues and improve quality standards. A simple yet effective strategy is the CRUD (Create, Read, Update, Delete) approach, which covers basic functionalities and allows for easy automation. Finally, it's essential to review and adjust the effectiveness of an automation strategy regularly to ensure it remains relevant and resource-efficient.