<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[RSS Feed]]></title><description><![CDATA[RSS Feed]]></description><link>http://direct.ecency.com</link><image><url>http://direct.ecency.com/logo512.png</url><title>RSS Feed</title><link>http://direct.ecency.com</link></image><generator>RSS for Node</generator><lastBuildDate>Wed, 22 Apr 2026 04:22:13 GMT</lastBuildDate><atom:link href="http://direct.ecency.com/created/behaviordriven/rss.xml" rel="self" type="application/rss+xml"/><item><title><![CDATA[Little Known Ways to Behavior Driven Ansible Testing — Part 1]]></title><description><![CDATA[This is the first part of two part post … As a developer in order to implement CI(Continuous Integration) properly one of the first things that you should be implementing Unit test code which goes hand]]></description><link>http://direct.ecency.com/behaviordriven/@devonartis/little-known-ways-to-behavior-driven-ansible-testing-part-1</link><guid isPermaLink="true">http://direct.ecency.com/behaviordriven/@devonartis/little-known-ways-to-behavior-driven-ansible-testing-part-1</guid><category><![CDATA[behaviordriven]]></category><dc:creator><![CDATA[devonartis]]></dc:creator><pubDate>Wed, 13 Sep 2017 11:52:06 GMT</pubDate><enclosure url="https://images.ecency.com/p/6VvuHGsoU2QD2aHbJiivbVZV6nAA4BJrX2xi1YbtxN95Zc7FwUfajy6te2K5A9794zoiR2iFSvYUhiZbyi6hSHNS27x2XEEcoGaoPdTCC7GXwo1grwCMvQMSrjX8vz?format=match&amp;mode=fit" length="0" type="false"/></item></channel></rss>