You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: