Feature request: Sequential testing
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
Feature request
Template not yet filled out, just to start tracking demand. Context: https://posthog.slack.com/archives/C07PXH2GTGV/p1776754497414459
Is your feature request related to a problem?
Customers, especially those with a data-science-heavy experimentation practice or AI-driven rapid-iteration workflows, want to safely "peek" at experiment results and make decisions earlier when the signal is clear, without inflating false-positive rates.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
Feature gap
Debug info
- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
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 with the linked Slack discussion to understand the customer demand and existing experimentation behavior. The issue names no files, tests, or entry points and leaves the solution unspecified, so first establish the intended sequential-testing scope and acceptance criteria before locating implementation work.
Written by the indexing model from the issue text.
Assessment
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100