Our QA team has just started to work on an automated test strategy for our agile process and have been considering a low code approach. Is anyone using a low code product like Mabl or Leapwork for their testing? What has your experience been like and would you recommend a low code approach?
Test automation can reach a point at which it is no longer supporting organizational goals. Martin Ivison examines four key causes for this unhealthy state and finds out that carefully chosen metrics and a holistic, adaptive, and risk-driven approach go a long way to prevent and remedy this problem.
When author Zane Roett began a new Senior Manager test role in a new organization in 2019, he found that it became an important task to create and lead the development of a software test engineering professional community of practice (TCoP).
The Testing Eight is not the name of the latest Hollywood blockbuster but instead refers to eight testing fundamentals whose principles can be applied to any development methodology to ensure the quality of its deliverables.
It is time to test the customer experience. If you test customer experience, you are likely to find out how customers behave at every step of their journey and what steps they never get to. Therefore, you will optimize stages that need improvement in the right order.
Oleksandra Melnikova discusses the benefits and drawbacks of using shared vs individual test environments and provides the results of her survey intended to gather the preferences and reasoning from QA professionals.