_Any_ kind of verification, including tests! After writing tests, the very first thing you should do is blatantly break something and check whether your tests catch it. And if not, write better tests (or debug your build). :)
-
-
-
true!
Kraj razgovora
Novi razgovor -
-
-
when do you stop inserting these small errors to see if the tool is really capable every single one of them? I thought test coverage was tough ...
-
it's just a thing to do periodically while developing specifications, as a sanity check and a hedge against vacuity
Kraj razgovora
Novi razgovor -
-
-
nice (and wholly agree!) source?
-
email sent by me!
- Još 1 odgovor
Novi razgovor -
-
-
That's testing. You've invented testing.
-
it's busses, actually
- Još 1 odgovor
Novi razgovor -
-
-
I do not think this has to do with formal methods. Humans are prone to confirmation bias. One must constantly be skeptical of evidence that supports ones beliefs. That said, anytime I get a result using a FM tool, I immediately try to prove false with it.
-
Ya, I just find formal methods really, really prone to this. I've been burned hard multiple times
- Još 4 druga odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.