38103ac6c5
it doesn't make sense to have a test per STIX version. The workbench only uses the latest supported STIX version. In order to make this work, the test suite was modified to dynamically compute some settings like where to get demo data, based on the value of stix2.DEFAULT_VERSION. Switched stix2.DEFAULT_VERSION back to "2.0", since I figure it should be sync'd up with the 'from .vxx import *' import statement from the top level package. |
||
|---|---|---|
| .. | ||
| stix2_data | ||
| __init__.py | ||
| conftest.py | ||
| constants.py | ||
| test_attack_pattern.py | ||
| test_base.py | ||
| test_bundle.py | ||
| test_campaign.py | ||
| test_core.py | ||
| test_course_of_action.py | ||
| test_custom.py | ||
| test_datastore.py | ||
| test_datastore_composite.py | ||
| test_datastore_filesystem.py | ||
| test_datastore_filters.py | ||
| test_datastore_memory.py | ||
| test_datastore_taxii.py | ||
| test_environment.py | ||
| test_external_reference.py | ||
| test_fixtures.py | ||
| test_granular_markings.py | ||
| test_identity.py | ||
| test_indicator.py | ||
| test_intrusion_set.py | ||
| test_kill_chain_phases.py | ||
| test_malware.py | ||
| test_marking_definition.py | ||
| test_markings.py | ||
| test_object_markings.py | ||
| test_observed_data.py | ||
| test_pattern_expressions.py | ||
| test_pickle.py | ||
| test_properties.py | ||
| test_relationship.py | ||
| test_report.py | ||
| test_sighting.py | ||
| test_threat_actor.py | ||
| test_tool.py | ||
| test_utils.py | ||
| test_versioning.py | ||
| test_vulnerability.py | ||