AnsweredAssumed Answered

Best practise for testing scripts / developments

Question asked by globe11123 on Mar 1, 2017
Latest reply on Mar 2, 2017 by globe11123

I've made myself a little development module within our system so that our employee's can make development requests or ask for changes to be made within the system.


Currently I am making an instant backup from Filemaker server and copying that solution which is the quickest method of testing the live database without messing with live data.


I've found that many of the changes I've made aren't being fully tested enough (more of a gung-ho method of getting stuck into the problem rather than checking what the consequences of making the changes are) which then is creating more work for me to re-look at the request/change and redo it.


Whats the best practise for testing any developments made?

Is there any better methods than just taking backups all the time?