WSLC SDK Initial Tests

[JohnMcPMS]

Summary of the Pull Request

Tests for initial WLSC SDK implementation and placeholders for not-yet-implemented APIs.

PR Checklist

• Closes: Link to issue #xxx
• Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
• Tests: Added/updated if needed and all pass
• Localization: All end user facing strings can be localized
• Dev docs: Added/updated if needed
• Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Adds tests for the implemented portions of the WSLC SDK and placeholders that expect E_NOTIMPL results from the unimplemented functions. Based on the WSLA tests as the SDK is a wrapper layer for it.

Validation Steps Performed

Ran these tests.

[Copilot]

Pull request overview

This pull request adds initial test coverage for the WSLC SDK (Windows Subsystem for Linux Container SDK), providing both functional tests for implemented APIs and placeholder tests for not-yet-implemented functionality. The tests follow patterns established in the existing WSLATests.cpp and provide comprehensive coverage of session management, image operations, container lifecycle, and process I/O handling.

Changes:

• Added WslcSdkTests.cpp with test coverage for WSLC SDK session, image, container, and process APIs
• Added placeholder tests expecting E_NOTIMPL for APIs not yet implemented
• Updated CMakeLists.txt to include the new test file and link against the wslcsdk library

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.

File	Description
test/windows/WslcSdkTests.cpp	New test file with 30+ test methods covering WSLC SDK functionality including session creation/termination, image pulling, container lifecycle, process I/O handling, and placeholder tests for unimplemented APIs
test/windows/CMakeLists.txt	Added WslcSdkTests.cpp to SOURCES, included WslcSDK headers, linked wslcsdk library, and added wslcsdk to dependencies

[OneBlue]

LGTM, minor comments

[OneBlue]

I recommend validating the return value of these (even in the RAII helpers) since we're validating the SDK behavior here

[JohnMcPMS]

I'm not seeing a VERIFY_SUCCEEDED_LOG type macro in TAEF. I doubt that we want to terminate the process if these are happening during an exception in the test. We could try/catch it, but would that actually cause the test to fail due to error logging?

In addition, these are attempting to do maximum cleanup for idempotency reasons. Tests can and should call these cleanup functions and verify the output as part of running the main test body.

Do you want it to be a requirement that the runtime always returns a success on repeat calls to these cleanup functions?