How do you approach testing for software that is constantly evolving, such as web applications or mobile apps?

🗄️ Archive
1

When testing software that is constantly evolving, it’s vital to make use of an agile approach to testing that can keep up with the pace of development. Below I have mentioned some strategies and best practices to consider:

  1. Collaborate closely with developers: As changes are made to the software, work closely with the development team to ensure that testing efforts are aligned with the latest updates and priorities. Establish a clear feedback loop to ensure that issues are identified and addressed as soon as possible.
  2. Use automation where possible: Automated testing can help streamline testing efforts and allow for more frequent testing, particularly for repetitive or time-consuming tasks. Invest in robust test automation frameworks and tools that can support the evolving needs of the software.
  3. Monitor and measure: Use monitoring and analytics tools to track how the software is being used, identify areas of the software that are experiencing issues or receiving negative feedback, and measure the impact of any changes or updates.

These were three practices that I think should be considered but there’s more to it. So, I would like to know more about it.

1 Like
2

Depending on the software architecture, mock up can be used for mock-frontend and/or mock-backend so testings can be done independently.

3

Hi Jennifer.

Welcome to the most awesome Software Testing community in the world. Oh wait, no, best community in the whole universe! Welcome.

I’m going to start with my stock answer, get a scout who knows where the moving stuff is. Namely: Wardley Maps

But I think your question is more aimed at how do testers survive when the “product” evolves at super high speed. Which might require unique heuristics, because so far nobody is throwing in anything unique here. For now I’m going to throw in one suggestion only. A Zero bug policy.