Actively Test Baselines

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
search, testing-qa

Research direction

Start with the contentctl test path for production searches and compare its handling of baseline searches with validate/build, noting the existing manual_test exception behavior. Trace where the runtime exception occurs and identify the baseline test entry point; done means non-manual production searches containing baselines are actively tested without that exception.

Written by the indexing model from the issue text.

Description

We currently lack functionality to test Baselines that are part of searches.
In fact, if a production search contains a baseline and is NOT marked as manual_test, we throw a runtime exception during contentctl test (but not an exception during contentctl validate/build, which is an intentional choice).

We should add support for active testing of baselines.

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

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.

More from splunk/contentctl

All issues in splunk/contentctl

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.