Skip to content

docs: Add how-to-build a new test documentation - #313

Open
DGonzalezVillal wants to merge 1 commit into
AMDEPYC:mainfrom
DGonzalezVillal:test-docs
Open

docs: Add how-to-build a new test documentation#313
DGonzalezVillal wants to merge 1 commit into
AMDEPYC:mainfrom
DGonzalezVillal:test-docs

Conversation

@DGonzalezVillal

Copy link
Copy Markdown
Contributor

Docs on how to build tests using our new harness

Signed-off-by: DGonzalezVillal <Diego.GonzalezVillalobos@amd.com>

The tests themselves live in the certificate-level folders. Each test is its own Python module.

The `sev_verify/cert_tests/common` directory contains prerequisite tests that run before every certification level. These are declared in `prereqs.toml`. For example, `snp_ok` verifies that SEV-SNP is enabled and functional on the host and that the required components are present. If any required prerequisite fails, certification is skipped, since subsequent tests would also fail.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we should also use this directory for 'library' modules that all tests use, like the future tcb one.

]
```

### VM profile

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### VM profile
## VM profile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants