<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>PBT on Machine-Cycle</title>
    <link>https://machine-cycle.pages.dev/en/tags/pbt/</link>
    <description>Recent content in PBT on Machine-Cycle</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 29 Jul 2021 10:00:00 +0200</lastBuildDate><atom:link href="https://machine-cycle.pages.dev/en/tags/pbt/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A different way of thinking about testing: the Property Based Test</title>
      <link>https://machine-cycle.pages.dev/en/posts/property_based_testing/</link>
      <pubDate>Thu, 29 Jul 2021 10:00:00 +0200</pubDate>
      
      <guid>https://machine-cycle.pages.dev/en/posts/property_based_testing/</guid>
      <description>Let’s see why a coverage of 100% is not enough to make us sleep safe and sound In my previous article, we have seen how testing and refactorizing legacy code with Golden Master Pattern. Now, we will continue to talk about testing, introducing a new paradigm with a simple example.
We are familiar with writing tests based on examples. In literature we talk about “Example test”: given an input we have an expected output.</description>
    </item>
    
  </channel>
</rss>
