Friday, April 5, 2024
1 change · saas-17.2
Enhancements to existing features
Error messages for automated web tour checks now combine the tour and step details with the specific failure reason. This makes it easier for teams to identify which tour failed and why, reducing investigation time in test environments.
Original PR description
In this commit, we make the error message more explicit to avoid to get the same error message for differents tours in runbot. e.g.
- Error: Tour ${tour.name} failed at step ${describeStep(step)}.
- Error: Element has been found. The error seems to be in run() To reach that, we just concatenate the two error messages in only one. e.g.
- Error: Tour ${tour.name} failed at step ${describeStep(step)}. Element has been found. The error seems to be in run()