• jjjalljs@ttrpg.network
    link
    fedilink
    arrow-up
    2
    ·
    4 months ago

    It’s strangely satisfying when the “this will probably never happen” test case finds a problem during development.

    I had tests for deleting that were like

    • create item a
    • create item b
    • delete item a via the code under test
    • assert item a is gone
    • assert item b is still there

    I thought maybe the whole bit with item b was excessive, but sure enough one day I accidentally fucked something up and deleted all the items, and the test pointed it out before the bad code left my local machine.

    • nxdefiant@startrek.website
      link
      fedilink
      arrow-up
      1
      ·
      4 months ago

      Ok, well, if you ever come across a test framework named AuTest, you can blame me, because I’m stealing the shit out of that.

  • THCDenton@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    4 months ago
    Z – Zero
    
    O – One
    
    M – Many (or More complex)
    
    B – Boundary Behaviors
    
    I – Interface definition
    
    E – Exercise Exceptional behavior
    
    S – Simple Scenarios, Simple Solutions