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

Updating and expanding default_data #65

Open
zrush-mitre opened this issue Oct 15, 2019 · 1 comment
Open

Updating and expanding default_data #65

zrush-mitre opened this issue Oct 15, 2019 · 1 comment
Labels
enhancement TAXII 2.1 Issue related to TAXII 2.1 implementation

Comments

@zrush-mitre
Copy link
Contributor

The default_data file included with the TAXII repo is out of date and pretty basic for data to test against. At the very least, this data must be updated to conform with TAXII 2.1 spec. I also recommend adding some to the data to include some complexity, since this is the data that all tests use to ensure accuracy of changes. An extra step would also include a larger set of data, allowing for the speed and efficiency of the server and future changes to be tested.

I have made some changes to the default_data in my PR #62 but is most likely not entirely accurate as well.

@emmanvg emmanvg added enhancement TAXII 2.1 Issue related to TAXII 2.1 implementation labels Mar 27, 2020
@zrush-mitre
Copy link
Contributor Author

Some work has been done with this since the update to the testing for the server (see #112 and #113), specifically some objects now have multiple versions, and there is an object with two different spec_versions that has opposite version values, so there is a step in the right direction.

I would like to see more work done to expand the data though, especially when backend speed improvements are worked on to include a large amount of data to be parsed to test speeds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement TAXII 2.1 Issue related to TAXII 2.1 implementation
Projects
None yet
Development

No branches or pull requests

2 participants