Description

Architectural

• removed BaseTest class and TEST() redefinition, tests don't need to derive from it from now on
• replaced PlatformInitBase that inherited from BaseTest with lightweight PlatformTestSuite, platform initialization/deinitialization is done in static methods SetUpTestSuite()/TearDownTestSuite() and doesn't interfere with fixture initialization
• switched to our own main() entry point from gtest_main

Logging

• logging is now initialized in gtest environment
• all tests are now expected to use BOOST_LOG
• resulting test_sunshine.log can be uploaded as github actions artifact in CI
• this log is shared with normal sunshine outputs
• each test start/result is now printed to the log, automatically through gtest event listener
• each failed test will also print the relevant portion of the log into stdout, implemented as additional stringstream boost log sink in gtest event listener
• added new log level tests hidden behind SUNSHINE_TESTS compile definition
• now sunshine doesn't add stdout boost log sink if it's compiled with SUNSHINE_TESTS
• migrated all tests' cout messages to BOOST_LOG(tests)

Cosmetics

• replaced ::testing namespace with testing, safeguarding against conflicts is pointless when we should not introduce them in the first place
• replaced all instances of class with struct and dropped all access specifiers, here such access specifiers only add noise
• switched parameterized test names from 0,1,2... to custom names where it was applicable

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components