That's a great PR description, thank you so much for your effort!

Generated by 🚫 dangerJS

Do we want to be running tests with CONCATENATE_SCRIPTS off and SCRIPT_DEBUG on? That's a different environment than most people use in production? I don't know if it matters :)

I suppose it depends on if we're testing the concatenation or not. If there are problems, the errors would be more direct to what on our end is broken. I see your point though. Not sure either.

I read up about this here: https://stackoverflow.com/questions/32588692/how-does-concatenate-scripts-work-on-wp-config/32589922

And I found this info:

by defining the constant as false you are practically forcing WordPress to load each script on the administration page individually rater than collectively. So in that case - If one script fails to load and work correctly, the others can still continue to operate correctly.

This is a recommended setting for debugging and local development

I guess that's why @jeherve's asked to add it (for debugging).

That's a different environment than most people use in production?

Would that be an issue? I don't think so. @jeherve can add more to this I guess? :)

That's a different environment than most people use in production? I don't know if it matters :)

I don't know; I personally like to switch back and forth when testing; CONCATENATE_SCRIPTS and SCRIPT_DEBUG can be helpful to get to the source of an issue.