3 Matching Annotations
- Aug 2020
-
meta.stackexchange.com meta.stackexchange.com
-
Can't upvote this enough. It is highly irritating to see language destroyed (and we wonder why kids bastardize the language..).
Tags
- combating widespread incorrectness/misconception by consistently doing it correctly
- even if majority makes a mistake; it doesn't make it correct
- correctness
- example of: using incorrect terms
- hoping/trying to convince others that your view/opinion/way is right by consistently sticking to it despite many being ignorant/mistaken/unaware/holding different opinion
Annotators
URL
-
- Nov 2019
-
medium.com medium.com
-
Using expect { }.not_to raise_error(SpecificErrorClass) risks false positives, as literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError, and ArgumentError)
Actually, those would be false negatives: the absence of a test failure when it should be there.
https://en.wikipedia.org/wiki/False_positives_and_false_negatives
-
-
kentcdodds.com kentcdodds.com
-
This is called a false positive. It means that we didn't get a test failure, but we should have
No, this is a false negative. We didn't get a test failure (that is, there is a lack of the condition (test failure)), when the condition (test failure) should have been present.
Read https://en.wikipedia.org/wiki/False_positives_and_false_negatives
-