Investigate potential for integration testing in GitHub CI

[jpstewart]

This is an extreme(ly unlikely) stretch goal for unit testing, but something worth investigating. Integration tests in CommonLibSSE NG require a Skyrim executable, but not for Skyrim to initialize. Is it possible, within licensing restrictions, to do this in CI? Investigation goals include automated installs of Steam in the Windows VM used for testing, downloading and installing either Skyrim or at least the Skyrim executable and DLLs, using secrets to store the Steam credentials.

Notes and Questions

• Steam supports silent install: https://silentinstallhq.com/steam-silent-install-how-to-guide/
• Can steam automate configuring credentials?
• Can steam automate installing a game, or downloading certain files from a depot?
• Is this ultimately still compliant with the Skyrim/Steam licensing?

[jpstewart]

Additional resources for automating Steam install:

Steam command line options, including script execution
SteamCMD, the Steam command line version

[jpstewart]

Possible workflow:

• Create SteamCMD directory at C:\SteamCMD.
• Download and extract SteamCMD there.
• Run steamcmd +login <username>, using username made for testing.
• Feed password, using GitHub secrets. Don't use SteamGuard as this complicates the process.
  • Alternatively, SteamCMD only needs SteamGuard once, according to docs. Perhaps do this manually once, then store resulting credentials in GitHub secrets, and push to the file that saves it.
• Run steamcmd +app_update 489830 to install Skyrim SE.
• Run steamcmd +app_update 611670 to install Skyrim VR.
• Install the FuDGE test runner.
• Run integration tests.
• Run end-to-end tests fo SE/VR via FuDGE test runner.