@gabriela.pinto reported that once he/she had a problem with Chrome 137.0.7151.55; switched to Chrome for Testing v137.0.7151.55; then his/her problem was fixed.
This report makes me puzzled. This report indicates that Chrome browser 137.0.7151.55 and Chrome for Testing 137.0.7151.55 behaves differently.
This is a surprise for me. The Chrome team wrote Chrome for Testing: reliable downloads for browser automation | Blog | Chrome for Developers where they promised that Chrome browser and Chrom for Testing work no differently except auto-updates.
… Chrome is a software too much sophisticated for me. I cannot really understand it.