splunk / splunk/addonfactory-solutions-library-python
allow test_hec_event_writer to be executed more than once per splunk instance
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
If solnlib integration tests are called second time locally with use of the same splunk instance, error like below will be raised.
`
assert len(search_results) == 1
E assert 2 == 1
E + where 2 = len([{'_bkt': 'main15806ABEBD-E78E-4B8A-B1B0-5DC0ADD73AB5', '_cd': '15:210', '_indextime': '1691056507', '_raw': '[{"tes...me": "test_hec_event_writes_with_non_utf_8", "field_a": "Üü_Öö_Ää_some_text", "field_b": "some_text_Üü_Öö_Ää"}]', ...}])
If [the SPL](https://github.com/splunk/addonfactory-solutions-library-python/blob/d7b36323d0070d6f04195d78e282cd7fa0494b28/tests/integration/test_hec_event_writer.py#L63) is extended by condition like | where _time>{test_start_timestamp} AND _time<{test_end_timestamp}`
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
Start with tests/integration/test_hec_event_writer.py, especially the SPL at line 63, and reproduce the test twice against the same Splunk instance. Check how test_start_timestamp and test_end_timestamp can distinguish events from the current run; done means a repeated execution returns only the current test event and keeps the assertion at one result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100