Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test interoperability with the python implementation via subprocess calls #63

Open
shibumi opened this issue Jul 30, 2020 · 4 comments
Open
Labels
enhancement New feature or request

Comments

@shibumi
Copy link
Collaborator

shibumi commented Jul 30, 2020

Please fill in the fields below to submit an issue or feature request. The
more information that is provided, the better.

Description of issue or feature request:
Right now, we have a static test/data directory with some test data in it. I am not sure, if this test data got created with in-toto-python. I would like to suppose, that we add a few tests calling in-toto-python dynamically. That way, we do not mix up in-toto-python generated test/data and our static test data. Furthermore we have some dynamic tests. Thanks to @trishankatdatadog for pointing this out.

Current behavior:
We just test against a static test directory

Expected behavior:
We should be able to test in-toto-python interoperability via calling in-toto-python. The Go TUF implementation is a nice example for such tests.

@lukpueh
Copy link
Member

lukpueh commented Aug 3, 2020

Also see "Cross-implementation interoperability" section in in-toto org roadmap 2021 (WIP, in-toto/specification#37)

@lukpueh
Copy link
Member

lukpueh commented Aug 3, 2020

cc @adityasaky

@adityasaky
Copy link
Member

Adding interoperability tests would definitely be great!

@shibumi shibumi added the enhancement New feature or request label Jan 15, 2021
@adityasaky
Copy link
Member

in-toto/in-toto#563

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants