-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add endpoint spec to get events from a test run #2255
Merged
Merged
Changes from 3 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,63 @@ | ||
version: 3.0.0 | ||
components: | ||
schemas: | ||
TestRunEvent: | ||
type: object | ||
properties: | ||
type: | ||
type: string | ||
stage: | ||
type: string | ||
enum: | ||
- trigger | ||
- trace | ||
- test | ||
description: | ||
type: string | ||
createdAt: | ||
type: string | ||
format: date-time | ||
testId: | ||
type: string | ||
runId: | ||
type: string | ||
dataStoreConnection: | ||
$ref: "./config.yaml#/components/schemas/ConnectionResult" | ||
polling: | ||
$ref: "#/components/schemas/PollingInfo" | ||
outputs: | ||
type: array | ||
items: | ||
$ref: "#/components/schemas/OutputInfo" | ||
|
||
PollingInfo: | ||
type: object | ||
properties: | ||
type: | ||
type: string | ||
enum: | ||
- periodic | ||
reasonNextIteration: | ||
type: string | ||
isComplete: | ||
type: boolean | ||
periodic: | ||
type: object | ||
properties: | ||
numberSpans: | ||
type: integer | ||
numberIterations: | ||
type: integer | ||
|
||
OutputInfo: | ||
type: object | ||
properties: | ||
logLevel: | ||
type: string | ||
enum: | ||
- warning | ||
- error | ||
message: | ||
type: string | ||
outputName: | ||
type: string |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we include a
info
type?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it's worth unless we want to show in the event log what are the values for each output after they were resolved. @xoscar what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the info type is not something we'll be using in the near future so I think its fine to not have it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, makes sense @mathnogueira