Elgato_dark/python-tuf
1
0
Fork 0
mirror of https://github.com/theupdateframework/python-tuf synced 2026-05-24 10:08:28 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
python-tuf/tests/repository_data
History
Velichka Atanasova 06c8fb8cd3 Add a test for the 'ecdsa' key type 
Changes tests/repository_data/keystore/root_key3* to be an ecdsa key,
created and encrypted with the generate_ecdsa_key and
encrypt_key methods of securesystemslib.keys.
The test_updater_root_rotation_integration.py test
tests both repotool and updater.

Signed-off-by: Velichka Atanasova <avelichka@vmware.com>
2021-06-21 16:32:49 +03:00
..
client Re-generate repository and client test metadata 2020-03-11 11:35:37 +00:00
keystore Add a test for the 'ecdsa' key type 2021-06-21 16:32:49 +03:00
project Re-generate projects test metadata 2019-09-16 15:43:39 +02:00
repository Re-generate repository and client test metadata 2020-03-11 11:35:37 +00:00
generate.py Adopt sslib keygen interface encryption changes 2020-11-11 10:27:56 +01:00
generate_project_data.py Remove redundant test logic 2020-05-12 22:16:38 +01:00
map.json Tests: Queue replace tmp files, OS port creation 2020-11-13 14:01:57 +02:00
README.md fix-up the the -> the 2019-09-01 22:53:02 +08:00

README.md

Unit and integration testing

Running the tests

The unit and integration tests can be executed by invoking tox from any path under the project directory.

$ tox

Or by invoking aggregate_tests.py from the tests directory.

$ python aggregate_tests.py

Note: integration tests end in _integration.py.

If you wish to run a particular unit test, navigate to the tests directory and run that specific unit test. For example:

$ python test_updater.py

It it also possible to run the test cases of a unit test. For instance:

$ python -m unittest test_updater.TestMultiRepoUpdater.test_get_one_valid_targetinfo

Setup

The unit and integration tests operate on static metadata available in the repository_data directory. Before running the tests, static metadata is first copied to temporary directories and modified, as needed, by the tests.

The test modules typically spawn HTTP(S) servers that serve metadata and target files for the unit tests. The map file specifies the location of the test repositories and other properties. For specific targets and metadata provided by the tests repositories, please inspect their respective metadata.