More constants added to error log for the Jetpack test suite

[wigglemuff]

Fixes #9773

Changes proposed in this Pull Request:

• Constants mentioned in the following issue have been added in this PR - Docker: Add some more debug constants #9773

Testing instructions:

• You need to output to log from test files e.g. with error_log('boom')
• Instructions for running tests in Docker setup
• Tail logs from Docker setup with yarn docker:tail while running those tests — you should see "boom" with this change. Without the change you don't see it.

Proposed changelog entry for your changes:

• N/A

[jetpackbot]

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

Generated by 🚫 dangerJS

[mdawaffe]

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 :)

[kraftbj]

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.

[wigglemuff]

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? :)

[jeherve]

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.

[kraftbj]

Let's roll with this as I think it would help in reporting more actionable errors. If we run into any situations where this causes us more harm, we can revert. Since it is just in the testing environment, we can be a little more liberal to let it merge vs code that runs in production anywhere.