1.3.20 · D5Probability & Statistics
Question bank — Hypothesis testing and p-values
True or false — justify
A p-value of 0.02 means there is a 2% chance the null hypothesis is true.
False. The p-value is , computed assuming is true; it can never be the probability of . That flipped quantity needs a prior and Bayesian inference.
A p-value of 0.60 proves the null hypothesis is correct.
False. A large p-value only means the data are unsurprising under ; it never confirms . You "fail to reject", which is agnosticism, not proof — a small or noisy sample can hide a real effect.
If we reject at , there is a 5% chance we made a mistake on this particular test.
False. The 5% is the long-run rate of false rejections when is true across many tests; for one specific rejection the "chance of error" isn't 5% and isn't even defined without a prior.
Two studies with and carry essentially opposite scientific conclusions.
False. The evidence is nearly identical; only the arbitrary line falls between them. Treating this cliff as meaningful is a well-known abuse of thresholds.
A statistically significant result () is automatically important in practice.
False. With a huge sample size , even a microscopic effect crosses the threshold. Significance answers "is it distinguishable from noise?", not "is it big enough to care about?" — check the effect size.
Lowering from 0.05 to 0.01 makes the test better in every way.
False. It cuts false positives (Type I) but raises false negatives (Type II), lowering power. It's a trade-off, not a free improvement.
The p-value tells you how large the effect is.
False. The p-value blends effect size and sample size, so it can't isolate magnitude. A tiny effect with big and a huge effect with small can give the same p-value.
A two-tailed p-value is always exactly twice the one-tailed p-value for the same data.
True for symmetric distributions like the normal, where each tail has equal area, so doubling the one-sided tail gives the two-sided value — but only when the observed statistic lies on the tested side.
If your result is not significant, collecting more data until it becomes significant is a valid fix.
False. Repeatedly peeking and stopping when inflates the true Type I rate far above 5% (optional stopping / p-hacking). The stopping rule must be fixed in advance.
The confidence interval and the hypothesis test can disagree about the same parameter.
False, when built consistently: a 95% confidence interval excludes the null mean exactly when the two-tailed test rejects at . They are two views of the same computation.
Spot the error
"We got , so the probability our alternative hypothesis is true is 97%."
Error: p-values say nothing about . The 0.03 is computed under ; the "97% true" claim is the transposed-conditional fallacy.
"We ran 20 independent A/B tests, and one came back with , so that feature clearly works."
Error: with 20 tests under true nulls you expect about one false positive at . This needs multiple-testing correction before celebrating.
" is that the new model is better than the old one, and we test whether it's worse."
Error: must be the "no effect / status quo" claim (accuracy equal), and carries the effect you want evidence for. Here the hypotheses are swapped.
"Since the standardised statistic and we only cared about improvement, we doubled the tail to get the p-value."
Error: for a one-tailed test you use a single tail (the one red region in the figure); doubling is only for two-tailed alternatives. Doubling here wrongly halves your evidence.
"We chose after seeing the data landed at ."
Error: must be fixed before looking at the outcome. Choosing the threshold to just clear your p-value is a form of p-hacking.
"The die test gave , so we accept that the die is perfectly fair."
Error: you fail to reject, which means "no evidence of unfairness", not "provably fair". A subtle bias could simply be undetectable with only 60 rolls.
"We used a z-test on samples with unknown population standard deviation and a heavily skewed distribution."
Error: the z-test relies on the Central Limit Theorem (needs larger ) and a known . Small skewed samples with an estimated call for a t-test and caution.
Why questions
Why do we assume is true before computing anything, instead of assuming ?
Because ("no effect") pins down an exact distribution to compute probabilities from, while ("some effect") is a vague family with no single number. You can only measure "how weird is this?" against a fixed reference.
Why is the p-value a tail probability ("at least as extreme") rather than the probability of exactly our observation?
For continuous data the probability of any exact value is zero, and even for discrete data a single point is a poor measure of surprise. "At least as extreme" captures how far into the unlikely region we landed, which is what surprise really means.
Why is 0.05 the usual , and is it special?
It isn't special — it's a 1920s convention (Fisher) chosen for convenience. The field standardised on it, but any threshold trades false positives against false negatives; the "right" depends on the cost of each error.
Why does a larger sample size shrink the p-value for a fixed true effect?
More data shrinks the standard error (with the population standard deviation), so the same real gap becomes many standard errors away from the null mean , pushing the test statistic further into the tail. This is why huge makes trivial effects "significant".
Why must we report effect size alongside the p-value?
The p-value alone can't tell a meaningful effect from a trivial one detected by brute sample size. Effect size (or a confidence interval) answers "how much?", the question that actually drives decisions in real experiments.
Why does the chi-squared die test lose one degree of freedom (df = 5, not 6)?
Because the six observed counts must sum to the fixed total (60), so once five are known the sixth is forced. One linear constraint removes one free dimension.
Why can rejecting never prove is exactly true?
Rejection only says the data are implausibly extreme under ; many alternatives besides your specific could also produce such data. Evidence against one claim is not proof of a particular competing claim.
Edge cases
What does the p-value equal if your standardised statistic sits exactly at the null mean ()?
For a two-tailed test : data can't be less extreme than the mean itself, so essentially every outcome is at least as extreme. This is maximal agreement with .
If a coin gives exactly 50 heads in 100 flips, is that evidence the coin is fair?
No — it's the most likely single outcome under fairness, giving a p-value near 1, but "consistent with " is not "confirms ". A cleverly biased or two-headed-then-switched coin could also produce it.
What happens to power as the true effect size approaches zero?
Power : when the effect vanishes, "correctly detecting it" collapses to the false-positive rate. No test can reliably detect an effect that isn't there.
Can a p-value ever be exactly 0?
Not in continuous theory — the normal tail is always positive, so for any finite statistic. Reported "" really means "smaller than the software's rounding floor".
What is the p-value's distribution when is exactly true?
It is Uniform on : under a true null every threshold is crossed exactly a fraction of the time, which is why the Type I rate equals .
If two effects are each non-significant separately, can their combination be significant?
Yes — pooling data or combining evidence can raise the effective sample size and push a real-but-small joint effect past the threshold. Non-significance doesn't add up linearly.
With one-tailed testing, what happens if the data land far in the unexpected direction?
The one-tailed p-value approaches 1 (huge on the wrong tail), so you fail to reject even for an extreme result — the cost of committing to a direction in advance. A two-tailed test would have caught it.
Recall One-line self-check
Cover every answer above; if you can reconstruct the reasoning (not just true/false), you own the concept. The two deadliest traps to over-learn: p-value , and "fail to reject" "accept ".