What does browser-tests stage in the CI do?

I was making changes to BEAT packages regarding their test-only phases. When running in test-only mode, we should not try to build the manual or check the package components anymore, as that will not fly with the current test strategy.

I made modifications to beat.cmdline and beat.core to take this into account (check latest MRs on those packages), simply making sure that sphinx and conda based test lines are only executed during the build and not in test-only phases.

I wanted to do the same for this package, but I wonder what the stage browser-tests really do. It seems to be not doing more than what is done during build.

Could @flavio.tarsetti clarify, please?