>robustness
Robustness
>stable == running the same battery of unit tests a million times
Imagine not understanding unit tests
What about that post infers they don't understand unit tests?
Imagine thinking unit tests prove robustness
>battery
>a million times
Because exhaustive test cases are for brainlets who don't understand how to to check edge cases efficiently.
also
>infers
(you)
>time complexity
>space complexity
Imagine your transliterating function crashing your program because you gave it an angle bracket
imagine not sanitizing your inputs
> but what if I already thought of evey edge cae
stay webshit, my guy
unit tests dont prove robustness, but extensive testing is as close as you can get to it (though you can prove algorithms / protocols with some cool tools i ever use)
shut up retards
lmao that reminds me of a boomer at work that says FreeBSD is more robust than Linux but he can't explain why
wrong img
if(input_type != operational_type) {
return dilate;
}
>boomer wallpaper
>boomer complaints
boomerpilled
>but extensive testing is as close as you can get to it
if you aren't doing property based testing, you aren't testing shit
>robust
>not even antifragile
it's easy if you try
>not following the via negativa principle in code
while (poster == INCEL) {
puts(HAVE_SEX);
}
...
WHAT IS DILLATE SOMEONE TELL ME
void explain_term_to_newfag(char *term) {
return;
}
> not posting the graphviz code
don't google it
What if you have a lot of edge cases? So if I have a lot of tests, I don't understand unit tests? A project with 5 tests would therefore be top shit?
>user-first
>code-first
>Jow Forums