Implement tests where needed

[acicovic]

Is your feature request related to a problem?

We strive to write tests for all new code that is added to the plugin. Due to workload, sometimes tests come after the integration of the code.

This thread is:

• A catch-all to track where tests need to be implemented for recent code.
• A call to action to examine what tests should be written for older code that is of high impact or prone to breakages.

Describe the solution you'd like

1. Write tests (unit, integration, E2E or combination) where applicable for recent code.
2. If resources allow it, expand this effort to older code that is of high impact or prone to breakages.

Recent code that has no or needs more tests

• Content Helper: Add structure tests #986.
• Metadata Author Archive Builder: Add support for the Co-Authors Plus plugin #1159.
• PARTIALLY DONE - After a bug which came from a missing require (which also resulted in our implementation of autoloading), we noticed that our metadata Tag_Builder and Date_Builder classes have no tests.
• The Dashboard Widget needs to have tests implemented (We've added integration tests here as part of Add filters for disabling Content Helper features #1539.
• Prevent always saving settings on Parsely->run() #1784 (comment)
• Disable plugin setup message in managed credentials mode #1772 (comment)
• Analytics_Posts_API: Increase request timeout #1789 (comment)

Other related issues

• DONE - Consistently use self::factory() in tests #1121