The Reading web team had to disable a browser test on the beta cluster because the default Selenium_user is not fit to test the use case we have (we have a test that expects the user to be new).
Our test checks if a user is new and has no edits the interface behaves a certain way.
When we run @integration tests on a per commit basis this is not a problem as new users are created for every scenario.
Could we make it possible to run some tests as a user that meets certain criteria, e.g. a user that doesn't have any edits, has a certain amount of edits.