Skip to content
This repository has been archived by the owner on Dec 12, 2023. It is now read-only.

More Fixes for 1.0.0-rc2 Release #44

Closed
wants to merge 19 commits into from
Closed

Conversation

ohsh6o
Copy link

@ohsh6o ohsh6o commented Jan 1, 2021

This time, these changes will collect the last remaining bits and pieces for the move to 1.0.0-rc1.

Closes #39.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@ohsh6o ohsh6o mentioned this pull request Jan 14, 2021
Since 1.0.0-rc1 introduced some breaking changes, we need to check for
this now. The new upgraded example SSP does not have that field edited
since I believe it was manually created and/or manually edited after it
was run through the usnistgov/OSCAL M3->RC1 upconverter, this seems to
have been missed.
Put them in the right locations in the report instead of repeating
them ad nauseam.
This is annoying and distoring module updates.
We will need to make way for reading values from upstream OSCAL
Metaschema files.
It can only fire once, which is why tests were breaking.
@github-actions
Copy link

Unit Test Results

  1 files  ±0    2 suites  ±0   0s ⏱️ ±0s
  0 tests ±0    0 ✔️ ±0  0 💤 ±0  0 ✖️ ±0 
46 runs  +3  46 ✔️ +3  0 💤 ±0  0 ✖️ ±0 

results for commit 42c5cec ± comparison against base commit 6524f06

During the rebase and what looked like the last commit, this
somehow got lost not once, but twice!
@github-actions
Copy link

Unit Test Results

  1 files  ±0    2 suites  ±0   0s ⏱️ ±0s
  0 tests ±0    0 ✔️ ±0  0 💤 ±0  0 ✖️ ±0 
46 runs  +3  46 ✔️ +3  0 💤 ±0  0 ✖️ ±0 

results for commit 68b7324 ± comparison against base commit 6524f06

Will add tests then use it for context filter.
@github-actions
Copy link

Unit Test Results

  1 files  ±0    2 suites  ±0   0s ⏱️ ±0s
  0 tests ±0    0 ✔️ ±0  0 💤 ±0  0 ✖️ ±0 
46 runs  +3  46 ✔️ +3  0 💤 ±0  0 ✖️ ±0 

results for commit 57fdca1 ± comparison against base commit 6524f06

Passing in the @ns attribute as just a string won't work.
@github-actions
Copy link

Unit Test Results

  1 files  ±0    2 suites  ±0   0s ⏱️ ±0s
  0 tests ±0    0 ✔️ ±0  0 💤 ±0  0 ✖️ ±0 
46 runs  +3  46 ✔️ +3  0 💤 ±0  0 ✖️ ±0 

results for commit 0643030 ± comparison against base commit 6524f06

@github-actions
Copy link

Unit Test Results

  1 files  ±0    2 suites  ±0   0s ⏱️ ±0s
  0 tests ±0    0 ✔️ ±0  0 💤 ±0  0 ✖️ ±0 
48 runs  +5  48 ✔️ +5  0 💤 ±0  0 ✖️ ±0 

results for commit 2a5346f ± comparison against base commit 6524f06

@github-actions
Copy link

Unit Test Results

  1 files  ±0    2 suites  ±0   0s ⏱️ ±0s
  0 tests ±0    0 ✔️ ±0  0 💤 ±0  0 ✖️ ±0 
52 runs  +9  52 ✔️ +9  0 💤 ±0  0 ✖️ ±0 

results for commit 7196ee3 ± comparison against base commit 6524f06

@github-actions
Copy link

Unit Test Results

  1 files  ±0    2 suites  ±0   0s ⏱️ ±0s
  0 tests ±0    0 ✔️ ±0  0 💤 ±0  0 ✖️ ±0 
52 runs  +9  52 ✔️ +9  0 💤 ±0  0 ✖️ ±0 

results for commit 52a2a4b ± comparison against base commit 6524f06

@github-actions
Copy link

Unit Test Results

  1 files  ±0    2 suites  ±0   0s ⏱️ ±0s
  0 tests ±0    0 ✔️ ±0  0 💤 ±0  0 ✖️ ±0 
52 runs  +9  52 ✔️ +9  0 💤 ±0  0 ✖️ ±0 

results for commit 465bcdb ± comparison against base commit 6524f06

@ohsh6o ohsh6o changed the title More Fixes for 1.0.0-rc1 Release More Fixes for 1.0.0-rc2 Release Apr 8, 2021
@github-actions
Copy link

github-actions bot commented May 5, 2021

XSpec Test Results

  1 files  ±0    2 suites  ±0   0s ⏱️ ±0s
52 tests +9  52 ✔️ +9  0 💤 ±0  0 ❌ ±0 

Results for commit 0c3de86. ± Comparison against base commit 28978ae.

This pull request removes 2 and adds 11 tests. Note that renamed tests count towards both.
with lv:registry when a valid filesystem path is provided the function will return a non-empty collection of information types, threats, and values
with lv:registry when an invalid filesystem path is provided the function will return an empty collection of information types, threats, and values
when the document metadata should have an OSCAL version number and it is defined with an unsupported OSCAL version it is invalid. assert unsupported-oscal-version fatal
when the document metadata should have an OSCAL version number and it is defined with the supported OSCAL version it is valid. not assert unsupported-oscal-version
when the document metadata should have an OSCAL version number and it is not defined it is invalid. assert unsupported-oscal-version fatal
with lv:extension-registry when a valid filesystem path is provided the function will return a non-empty collection of information types, threats, and values
with lv:extension-registry when an invalid filesystem path is provided the function will return an empty collection of information types, threats, and values
with lv:has-core-ns when a node with an explicit @ns attribute is provided that does not match the OSCAL default the function returns false
with lv:has-core-ns when a node with an explicit @ns attribute is provided that matches the OSCAL default the function returns true
with lv:has-core-ns when a node with no explicit @ns attribute is provided the function returns true
with lv:has-extension-ns when a node with an explicit @ns attribute does match the extension registry in the SSP the function returns true
with lv:has-extension-ns when a node with an explicit @ns attribute does not match the extension registry in the SSP the function returns false
…

@ohsh6o ohsh6o closed this May 11, 2021
@ohsh6o ohsh6o deleted the issue-39-oscal-rc1-fixups branch May 11, 2021 04:20
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants