<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Acceptance Tests on The Agile Techies Daily List</title>
    <link>https://agiletechies.com/tags/acceptance-tests/</link>
    <description>Recent content in Acceptance Tests on The Agile Techies Daily List</description>
    <image>
      <title>The Agile Techies Daily List</title>
      <url>https://agiletechies.com/images/papermod-cover.png</url>
      <link>https://agiletechies.com/images/papermod-cover.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-US</language>
    <managingEditor>rajesh@duggalmail.com (Raj Duggal)</managingEditor>
    <webMaster>rajesh@duggalmail.com (Raj Duggal)</webMaster>
    <lastBuildDate>Tue, 20 May 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://agiletechies.com/tags/acceptance-tests/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Acceptance Tests as Business Contracts</title>
      <link>https://agiletechies.com/posts/acceptance-tests-as-business-contracts/</link>
      <pubDate>Tue, 20 May 2025 00:00:00 +0000</pubDate><author>rajesh@duggalmail.com (Raj Duggal)</author>
      <guid>https://agiletechies.com/posts/acceptance-tests-as-business-contracts/</guid>
      <description>&lt;p&gt;Different teams have different ideas about how much details need to be specified in the requirements.&lt;/p&gt;
&lt;p&gt;Some teams keep them as vague wishes and others specify pixel-perfect prescriptions.&lt;/p&gt;
&lt;p&gt;It&amp;rsquo;s useful for the product team to describe the desired behavior with some clear examples. Builders then translate those examples into automatable scenarios written in domain language. And the team then iterates until the tests clearly capture the business intent (rather than technical details).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
