I am impressed by #SQLite testing approach, breadth, methodology and investment:
https://www.sqlite.org/testing.html
It's very important that there are OSS projects that set such examples.
There is always something to improve, but I think nobody will object that that's good level of testing
-
Prikaži ovu nit
-
Just some excerpts: 2. Test Harnesses 3. Anomaly Testing 3.1. Out-Of-Memory 3.3. Crash Testing 4. Fuzz Testing 4.1. SQL Fuzz 4.1.1. AFL 4.1.2. OSS Fuzz 4.1.4. third-party fuzzers ...
1 reply 0 proslijeđenih tweetova 7 korisnika označava da im se sviđaPrikaži ovu nit -
4.1.4.third-party fuzzers 4.2.Malformed DB Files 4.3.Boundary Value Tests 5.Regression Testing 6.Automatic Resource Leak Detection 7.Test Coverage 7.6.Mutation testing 8.Dynamic Analysis 8.2.Valgrind 8.4.Mutex Asserts 8.6.Undefined Behavior Checks 10.Checklists 11.Static Analysis
1 reply 0 proslijeđenih tweetova 5 korisnika označava da im se sviđaPrikaži ovu nit -
Their fault injection approach is similar to systematic fault injection we use in syzkaller for
#linux kernel: https://lore.kernel.org/patchwork/patch/774420/ … That's the way for testing error paths. Lots of different fuzzers +1 Just one is never enough. Also continuous fuzzing on OSS-Fuzz.1 reply 1 proslijeđeni tweet 4 korisnika označavaju da im se sviđaPrikaži ovu nit -
Measuring and knowing your test coverage +1 Lots of dynamic analysis +1 (though I am surprised to see Valgrind but not ASAN) Release checklists and tracking +1 (no "our release is all broken, but we did not even know")
1 reply 0 proslijeđenih tweetova 2 korisnika označavaju da im se sviđaPrikaži ovu nit -
Interesting note re static analysis (SA): "SA hasn't been helpful in finding bugs in SQLite. SA has found a few bugs in SQLite, but those are the exceptions. More bugs have been introduced into SQLite while trying to get it to compile without warnings than have been found by SA"
1 reply 6 proslijeđenih tweetova 15 korisnika označava da im se sviđaPrikaži ovu nit
Though, the code base is clean of compiler warnings and _some_ static analysis warnings. Which makes sense.
-
-
Odgovor korisniku/ci @dvyukov
I remember the quote, it was about compiler warnings, which the author understand as false positives. This is not the same as modern SA, which can give you an example of faulty input.
0 replies 0 proslijeđenih tweetova 0 korisnika označava da im se sviđaHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Č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.