Channels
administrivia
announcements
bot-dark-forest
devlog-together
in-alberta
in-boston
in-germany
in-israel
in-london
in-nyc
in-ontario
in-seattle
in-sf
in-socal
introduce-yourself
linking-together
of-ai
of-end-user-programming
of-functional-programming
of-graphics
of-logic-programming
of-music
present-company
random-encounters
reading-together
share-your-work
thinking-together
two-minute-week
wormholes
Title
a
Arvind Thyagarajan
08/24/2022, 3:40 PMThis is very cool!
https://www.fuzzmap.io/?welcome=1
We work a lot with visual state-machines (creating/defining state-machines visually to drive system state in the visual programme -- think xstate js but you're constructing the diagramme rather than having it rendered for you from code you write) and this fuzzer demo is exciting because it's an auto-state-machine, derived from real system states -- I can imagine this delightfully integrated with a testing framework.
I'm picturing a (dastardly? 😆) node-and-wire programme that runs through this fuzzer. If the run through emerges an unaccounted state, it's materialised in the state-machine embedded in the node-wire-nest, and the programmer can now create downstream logic to address this unexpected case.
could something like that work?
n
Nilesh Trivedi
08/25/2022, 12:09 PMSpeaking of automatically testing state machines, I wrote about my approach a few years ago: https://medium.com/cleartax-engineering/enumerating-test-cases-by-multiplying-state-machines-c1bedbf0e8e6