[HN Gopher] How rqlite is tested
       ___________________________________________________________________
        
       How rqlite is tested
        
       Author : otoolep
       Score  : 67 points
       Date   : 2025-01-14 20:21 UTC (2 hours ago)
        
 (HTM) web link (philipotoole.com)
 (TXT) w3m dump (philipotoole.com)
        
       | Ericson2314 wrote:
       | Now that there is testing like
       | https://turso.tech/blog/introducing-limbo-a-complete-rewrite...
       | going on, tbh the testing described in the linked piece doesn't
       | seem so good.
        
         | dangoodmanUT wrote:
         | Probably a lot better than 99.999% of software? This is made by
         | one person, with code that cannot be deterministically tested
         | (external SQLite) But you seem to be cargo culting, as this
         | testing has existed in DBs for nearly a decade
        
           | otoolep wrote:
           | rqlite has been in development for about a decade too!
           | 
           | https://github.com/rqlite/rqlite/blob/master/CHANGELOG.md#10.
           | ..
        
             | dangoodmanUT wrote:
             | kudos do you even just for sticking with it for that long,
             | but I know it's well loved
        
           | IshKebab wrote:
           | It's not cargo culting. Deterministic Simulation Testing has
           | been the standard for silicon verification practically
           | forever (though it isn't called that because nobody does
           | anything else).
           | 
           | Applying it to software is a logical step if you want similar
           | levels of quality assurance.
           | 
           | Do you _need_ that level of assurance for a database?
           | Probably not in most cases. But I think it 's a reasonable
           | thing to mention on a post that is touting database
           | reliability, especially because there are real databases that
           | do use it.
        
       | someguy101010 wrote:
       | I also enjoyed this in video format
       | https://youtu.be/JLlIAWjvHxM?feature=shared&t=2049
       | 
       | Always have been envious of that performance testing setup that
       | is shown here
        
       | fegu wrote:
       | There seems to be some copy pasta in the FAQ on if any node can
       | be contacted for writes or reads, the paragraph on reads mentions
       | writes.
        
         | otoolep wrote:
         | Thanks for flagging -- fixed.
        
       | didip wrote:
       | I love how dedicated you are with this project, Philip. Been
       | watching it for many many years.
        
       | denysvitali wrote:
       | In case you missed it, OP is also the author of rqlite
       | 
       | (I for one didn't notice at first)
        
         | otoolep wrote:
         | Yes, that is right. So here's my disclaimer: I'm the author of
         | rqlite.
         | 
         | I really admire the testing that the SQLite team does[1], and
         | the way it allows them to stand behind the statements they make
         | about quality. It's inspiring.
         | 
         | IMO there have only been two really big improvements to
         | software development relative to when I started programming
         | professionally 25 years ago: 1) code reviews becoming
         | mainstream, and 2) unit testing. (Perhaps Gen AI will be the
         | third). I believe extensive testing is the only reason that
         | rqlite continues to be developed to this day. It's not just
         | that it helps keep the quality high, it's a key design guide.
         | If a new module cannot be unit tested during development, in a
         | straightforward manner, it's a strong sign one's decomposition
         | of the problem is wrong.
         | 
         | [1] https://www.sqlite.org/testing.html
        
       ___________________________________________________________________
       (page generated 2025-01-14 23:00 UTC)