On Thu, Mar 2, 2017 at 2:36 PM, Atira Odhner <aodh...@pivotal.io> wrote: > Just to clarify the change we made in this regard --- we use the 'reset > layout' link in the header between tests, but it essentially still does a > page load and doesn't save us time. If we were to do an actual page load we > would run into issues because of the navigation confirmation popup. If we > were to manually reset the layout I think it would be very difficult to > account for all the various scenarios and ensure a reasonable separation > between tests.
Understood. I think that's fine - the further optimisation would be to think about test groups, where tests can be safely undertaken in sequence without a reset in-between. I think it would be reasonable in such cases to abort the group if a single test fails, thus potentially leaving the UI in an unknown state. That would potentially save a lot of time when testing the debugger or query tool, where you would have to navigate to a suitable node and then load the tool to even begin testing. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-hackers
