Currently the StudioUI tests are divided into two groups:

• common
• edge

It would be useful to review the existing tests and decide why were they marked as edge - there are three reasons I'm aware of: the tests would take too long (in that case they should be marked with another tag, e.g. @fullRegression), the tests modify the database (it that case a new tag @restoreDatabase (which restores database as an AfterScenario Step) could be introduced, so that they can be run more often) or they require specific configuration (in that case @edge should stay).