mitre-attack / mitre-attack/mitreattack-python
[Request] Optimize the time taken to complete E2E tests
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 743
- Forks
- 176
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem?
The tests take anywhere from 3-8 hours to complete.
Describe the solution you'd like
Reduce the amount of HTTP queries that the test modules send to the TAXII server. Theoretically, the TAXII server only needs to be queried by one of the tests (once) to validate that this argparser option works as intended.
Describe alternatives you've considered
If duplicate objects need to be retrieved multiple times, consider caching responses locally and/or retrieving the target STIX objects from the mitre/cti JSON source files.
Additional context
pyinstrument was used to validate that approx. 15% (3880s) of the total pytest runtime duration (24800s) of the tests were consumed by TAXII queries.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by profiling the pytest suite and tracing the TAXII server queries, especially the test covering the argparser option. Review whether repeated target STIX objects can come from cached responses or the mitre/cti JSON source files. Done means preserving the option's validation while substantially reducing duplicate HTTP requests and the 3–8 hour test duration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100