Update test case 2 (Capabilities) to support SPDM 1.3#146
Conversation
|
Other than the supported algorithms block, I'm not seeing anything immediately obvious that is new. Mostly just things that will trigger new checks in later tests. |
|
Hmm also need to update the docs. |
|
Since this results in 2.5 and 2.7 being basically identical, would it make more sense to change 2.5 to 1.2+ and have a specific test for anything only in 1.3? |
This updates test case 2 to check for and confirm report of SPDM 1.3 in GET_CAPABILITIES. All tests are the same at this time, and the test body for 1.2 has been made common with checks to toggle support for 1.3. This does not validate any new capabilities, such as the supported algorithms block, added in SPDM 1.3. Signed-off-by: Will Marone <Will.Marone@amd.com>
wmaroneAMD
force-pushed
the
validator-work
branch
from
078d53b to
a5af14d
Compare
|
If they are identical, we can just use 1.2+. |
|
Ok. I will unify the general case and create a specific test for the 1.3 feature. |
|
@jyao1 I think it's good as-is. The core of the test is unified for Capabilities 1.2 and up, which gets most of the reuse I think is possible. Unless there's a greater issue, I think a merge now is fine. |
wmaroneAMD
force-pushed
the
validator-work
branch
from
cc3c74e to
a5af14d
Compare
|
No changes, just removing a push to the wrong branch. |
|
Note that DMTF/libspdm#2968 adds support for |
3 participants
This updates test case 2 to check for and confirm report of SPDM 1.3 in GET_CAPABILITIES. All tests are the same at this time, and the test body for 1.2 has been made common with checks to toggle support for 1.3.
This does not validate any new capabilities, such as the supported algorithms block, added in SPDM 1.3.