Formal methods may not be common in everyday software development, but they are time-tested tools for detecting ambiguities and contradictions in specifications. What if we could identify properties from formal specifications and automatically generate property based tests? This would be valuable from a quality assurance perspective.

I'm exploring this idea by building a Ruby tool that parses formal specifications, detects property patterns, and generates executable property based test code.

In this talk, I'll demonstrate the concept, discuss the challenges, and share insights from bridging formal methods and Ruby testing.