[ViPPET] Add functional tests for performance job metadata flow#2078
Merged
ktaube26 merged 2 commits intoopen-edge-platform:mainfrom Apr 3, 2026
Merged
[ViPPET] Add functional tests for performance job metadata flow#2078ktaube26 merged 2 commits intoopen-edge-platform:mainfrom
ktaube26 merged 2 commits intoopen-edge-platform:mainfrom
Conversation
p-zak
approved these changes
Apr 2, 2026
KaliszWiktoria
approved these changes
Apr 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a new functional test module for the ViPPET performance job metadata flow (
metadata_mode=file). The new test file covers the full end-to-end lifecycle of metadata collection during performance jobs, as well as the relevant error paths.File added:
tools/visual-pipeline-and-platform-evaluation-tool/vippet/tests/functional/test_performance_metadata_flow.pyThe tests validate the following behaviours:
Happy path (
@pytest.mark.full):metadata_mode=fileon a pipeline that includes agvametapublishelement reachesCOMPLETEDstate and includes a non-emptymetadata_stream_urlsdict in its status response.Content-Type: text/event-stream.Pipeline/variant combinations are discovered dynamically at collection time by querying the VIPPET API and filtering for variants whose pipeline graph contains a
gvametapublishnode. If none are found (e.g. no compatible device is available), the parametrized tests are automatically skipped with a descriptive reason.Error paths (
@pytest.mark.smoke/@pytest.mark.full):metadata_mode=disabledreturns 404 with a message that referencesmetadata.metadata_mode=fileon a pipeline without agvametapublishelement reachesFAILEDstate with an error referencinggvametapublChecklist: