<?xml version="1.0" encoding="UTF-8"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xml:lang="en"><title>Tags @ www.talios.com</title><rights>Copyright 2010 www.talios.com</rights><subtitle>(Tags) </subtitle><author><name>Mark Derricutt</name></author><updated>2010-01-17T02:10:00Z</updated><link rel="alternate" type="text/html" href="http://www.talios.com/"/><link rel="self" type="application/atom+xml" href="http://www.talios.com/tags/index.rss?t=CONCORDION"/><id>tag:www.talios.com,2010:1</id><entry><id>tag:www.talios.com,2009-05-30:links.412172571</id><title>Writing Stupid Specifications with Concordion</title><content type="html" xml:lang="en" xml:base="http://www.talios.com/writing_stupid_specifications_with_concordion_2.htm"><![CDATA[For a while I've been an avid lover of the concordion testing framework, but one thing I always struggled with was the separation of state/data between the specification and the fixture.  As a simple work around I added a simple "eval" command, which]]></content><link rel="alternate" type="text/html" href="http://www.talios.com/writing_stupid_specifications_with_concordion_2.htm"/><updated>2009-05-30T23:18:00Z</updated><published>2009-05-30T23:18:00Z</published></entry></feed>