Investigate better defaults for earliest/latest for integration testing
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 139
- Forks
- 52
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
- Currently we have a window of -5y to -1m that we search for events when integration testing
- We should consider expanding that window, or perhaps just setting these values to None
- If we don't, at some point in the future old attack data will start to fall out of this window and appear to fail
Contributor guide
No contributing guide indexed for this repository
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
No file or test is named. Locate the integration-testing configuration that defines the -5y to -1m event window, then inspect how earliest and latest are passed to event searches. Compare the proposed defaults against historical attack-data coverage and update or add integration-test coverage for the chosen behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100