<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to Home</title><link>https://sourceforge.net/p/unitilscompositetest/wiki/Home/</link><description>Recent changes to Home</description><atom:link href="https://sourceforge.net/p/unitilscompositetest/wiki/Home/feed" rel="self"/><language>en</language><lastBuildDate>Tue, 04 Feb 2014 12:36:51 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/unitilscompositetest/wiki/Home/feed" rel="self" type="application/rss+xml"/><item><title>Discussion for Home page</title><link>https://sourceforge.net/p/unitilscompositetest/wiki/Home/</link><description>&lt;div class="markdown_content"&gt;&lt;h1 id="unitils-compositetest-module"&gt;Unitils compositeTest Module&lt;/h1&gt;
&lt;p&gt;When automating complex testscenarios (like end-to-end tests), you may need to execute a combination of batches, webservice&lt;br /&gt;
calls, web application interactions,  etc, maybe even on different points in time. In unitils, we have support for all those components, &lt;br /&gt;
but you could not orchestrate them easy. That is where the compositeTest module comes in.&lt;/p&gt;
&lt;p&gt;Now you can define each step as if it was a standalone test : you can specify the time with unitils-jodatime, prepare the database&lt;br /&gt;
via dbunit, call a batch/send a webservice message/do something in a webpage. In fact, any annotation based module that you use&lt;br /&gt;
in a normal test also works for the testpart. And of course, you can do the necessary asserts for that part of your complicated scenario directly in the testpart. &lt;/p&gt;
&lt;p&gt;In the end, you simply specify the sequence in which the parts are executed. This also makes it easy to reuse certain blocks to in multiple scenario's.&lt;/p&gt;
&lt;p&gt;If you would like to get a report for a testpart, no problem : each step is in fact a standalone test, but not reported as such. In the default behaviour, &lt;br /&gt;
you will only get a failed/passed for the test(s) that execute the parts. If you want a testpart to report its status as well in a standalone manner, you can specify this in the annotation.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Willemijn Wouters</dc:creator><pubDate>Tue, 04 Feb 2014 12:36:51 -0000</pubDate><guid>https://sourceforge.netc9a7648875bc15c65f7ca399ff1573a3c1dd1c42</guid></item><item><title>Home modified by Willemijn Wouters</title><link>https://sourceforge.net/p/unitilscompositetest/wiki/Home/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Welcome to your wiki!&lt;/p&gt;
&lt;p&gt;This is the default page, edit it as you see fit. To add a new page simply reference it within brackets, e.g.: &lt;span&gt;[SamplePage]&lt;/span&gt;.&lt;/p&gt;
&lt;p&gt;The wiki uses &lt;a class="" href="/p/unitilscompositetest/wiki/markdown_syntax/"&gt;Markdown&lt;/a&gt; syntax.&lt;/p&gt;
&lt;p&gt;&lt;h6&gt;Project Members:&lt;/h6&gt;
&lt;ul class="md-users-list"&gt;
&lt;li&gt;&lt;a href="/u/willemijnw/"&gt;Willemijn Wouters&lt;/a&gt; (admin)&lt;/li&gt;
&lt;/ul&gt;&lt;br /&gt;
&lt;/p&gt;&lt;p&gt;&lt;span class="download-button-52dd3485bcf63a4c532f8842" style="margin-bottom: 1em; display: block;"&gt;&lt;/span&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Willemijn Wouters</dc:creator><pubDate>Mon, 20 Jan 2014 14:36:54 -0000</pubDate><guid>https://sourceforge.net6be8280b7a9b5d95878a6f68ae50f24779ce3478</guid></item></channel></rss>