splunk / splunk/contentctl

Enforce distinct test names

Open
#224 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
139
Forks
52
Avg merge
1h 16m
Merged PRs (30d)
3

Description

  • For the purpose of reporting test results, it would be useful to have tests with unique names
  • Currently, almost all tests are named True Positive Test
  • We should add some validation which ensures either:
    • Every individual test has a unique name
    • OR every test for a given detection has a unique name

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test entry point is named. Start by locating the test definitions and the code that reports test results, then determine whether uniqueness should apply globally or per detection. Done means validation rejects duplicate names and the relevant test coverage confirms the selected rule.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
testing-qa
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.