ci: add conformance test workflow#36
ci: add conformance test workflow#36cusell-google merged 4 commits intoUniversal-Commerce-Protocol:mainfrom
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
18fbdc3 to
328f2b5
Compare
Adds a CI workflow that: - Checks out conformance, samples, and SDK repos - Starts the Flower Shop reference server with test data - Runs the full conformance test suite against it - Triggers on PRs, pushes to main, and nightly schedule Results are informational (continue-on-error) so the workflow does not block merges. This surfaces test failures early without gating PRs on a suite that depends on cross-repo compatibility. Addresses Universal-Commerce-Protocol#38
328f2b5 to
940bcaa
Compare
|
@cusell-google gentle ping - this is a small, focused change ready for review when you have time. |
cusell-google
left a comment
There was a problem hiding this comment.
Thanks again @sbeashwar for the nice, small incremental PRs!
|
Verified end-to-end on my fork: https://github.com/sbeashwar/conformance/actions/runs/24915126403 All 13 test files pass (59/59). The red status on the run is from a post-job |
|
On a second thought, updated to disable post-job uv cache prune (was timing out on a lock and turning the run red even though tests passed). Latest run is fully green: https://github.com/sbeashwar/conformance/actions/runs/24915690807 |
|
@cusell-google addressed the two review comments, switched to python-sdk and gated |
|
@cusell-google addressed the review feedback in the latest commits. Test plan verified on the fork:
Ready for re-review when you have a moment. |
6f6b2c5
into
Universal-Commerce-Protocol:main
Summary
*_test.pyfiles and reports per-file results using GitHub log groupscontinue-on-error) - does not block mergesThis would have caught the breakage from #28 before merge (see #37).
Addresses #38
Test plan