Capability Interface Test Framework #1083
Merged
Conversation
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
EasterTheBunny
temporarily deployed
to
integration
GitHub Actions
Inactive
EasterTheBunny
temporarily deployed
to
integration
GitHub Actions
Inactive
EasterTheBunny
temporarily deployed
to
integration
GitHub Actions
Inactive
EasterTheBunny
temporarily deployed
to
integration
GitHub Actions
Inactive
EasterTheBunny
temporarily deployed
to
integration
GitHub Actions
Inactive
EasterTheBunny
temporarily deployed
to
integration
GitHub Actions
Inactive
Base automatically changed from
CRE-293/add-cost-field-capability-response
to
main
March 26, 2025 06:35
EasterTheBunny
force-pushed
the
CRE-366/basic-capability-interface-tests
branch
from
e5f144b to
b99b8b5
Compare
EasterTheBunny
temporarily deployed
to
integration
GitHub Actions
Inactive
EasterTheBunny
temporarily deployed
to
integration
GitHub Actions
Inactive
EasterTheBunny
temporarily deployed
to
integration
GitHub Actions
Inactive
This commit introduces a testing framework for asserting essential tests that all capabilities should conform to. As a starting point, both trigger and executable capabilities must conform to the `BaseCapability` interface and produce properly structured information. Additionally, executable capabilities should return metering information in a `CapabilityResponse`. Tests for the `BaseCapability` cannot be disabled but those for `ExecutableCapability` can be per capability implementation as each implemtation will be different.
EasterTheBunny
force-pushed
the
CRE-366/basic-capability-interface-tests
branch
from
b99b8b5 to
075499f
Compare
EasterTheBunny
temporarily deployed
to
integration
GitHub Actions
Inactive
EasterTheBunny
temporarily deployed
to
integration
GitHub Actions
Inactive
EasterTheBunny
temporarily deployed
to
integration
GitHub Actions
Inactive
patrickhuie19
approved these changes
Apr 18, 2025
EasterTheBunny
had a problem deploying
to
integration
GitHub Actions
Failure
george-dorin
approved these changes
May 13, 2025
EasterTheBunny
had a problem deploying
to
integration
GitHub Actions
Failure
EasterTheBunny
had a problem deploying
to
integration
GitHub Actions
Failure
EasterTheBunny
temporarily deployed
to
integration
GitHub Actions
Inactive
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.
This commit introduces a testing framework for asserting essential tests that all capabilities should conform to. As a starting point, both trigger and executable capabilities must conform to the
BaseCapabilityinterface and produce properly structured information. Additionally, executable capabilities should return metering information in aCapabilityResponse.Tests for the
BaseCapabilitycannot be disabled but those forExecutableCapabilitycan be per capability implementation as each implemtation will be different.CRE-366
Requires
Supports