Dev's HATE UI testing because they don't always know what data to use.

This is good in some aspects because they interact with the system like a common user and understand the importance of a good UX, but it is also bad because it removes their attention to the code and can cause them to avoid UI dev.

Setup data scripts to make sure the data they need is ALWAYS ready in an env.

 

Make sure your developers have a few accounts to use to test various aspects of the site and the security matrix.  

If DB refreshes from a higher environment are occurring, find an automated or scripted way to persist core test data.  If the developer's entire environment is swept away then they will spend much more time trying to put those pieces back together to get back to where they were. They will not be spending the time developing new features.

 

The true goal here is to remove those data dependencies and make sure the system is reliable through various automated tests and a less coupled architecture.  Data scripts are a nice bridge until you get to a more advanced and abstracted solution.