Skip to content

filling in the testing gaps #243

@loosebazooka

Description

@loosebazooka

Now that aaron converted java conformance as a server, we can run easy code coverage on conformance over java looking for gaps in our testing, things we could add

bundle

  • fail if a bundle with no dsse or hashedrekord
  • fail on empty inner timestamp data (timestamp.rfc3161timestamp)
  • unexpected types? mashedrekor:1.0.0 dsse:3.0.0
  • certificate id/issuer matching? or other fields

hashedrekord

  • mismatched signature (actual vs logged)
  • mismatched hash (actual vs logged)
  • mismatched cert (actual vs logged)

dsse

  • unsupported payload type
  • provided artifact hash is not in subjects
  • fail if multiple signatures provided (sigstore limitation)
  • mismatched cert (not sure if this is actually reachable)

checkpoints

  • fail if more than 20 sigs
  • fail if no matching signature found

There's more tests related to unsupported algorithms that would still be useful to check that we don't fail open when we hit unparseable information.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions