<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Automated Unit testing for talend open studio data integration in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Automated-Unit-testing-for-talend-open-studio-data-integration/m-p/2330937#M99969</link>
    <description>Hi jlolling,
&lt;BR /&gt;Thanks for your reply.
&lt;BR /&gt;But I lost you when you were talking about master output.
&lt;BR /&gt;Do you have an example or a documentation? Also, do you have any idea on how TUJ Automation can be used?
&lt;BR /&gt;Thanks</description>
    <pubDate>Mon, 23 May 2016 06:23:39 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2016-05-23T06:23:39Z</dc:date>
    <item>
      <title>Automated Unit testing for talend open studio data integration</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Automated-Unit-testing-for-talend-open-studio-data-integration/m-p/2330935#M99967</link>
      <description>Hi,
&lt;BR /&gt;I want to know how to create a framework to support automated unit testing for talend jobs.
&lt;BR /&gt;Can someone help me with the list of available options?
&lt;BR /&gt;Your help is highly appreciated
&lt;BR /&gt;Thanks</description>
      <pubDate>Thu, 19 May 2016 12:57:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Automated-Unit-testing-for-talend-open-studio-data-integration/m-p/2330935#M99967</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-05-19T12:57:17Z</dc:date>
    </item>
    <item>
      <title>Re: Automated Unit testing for talend open studio data integration</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Automated-Unit-testing-for-talend-open-studio-data-integration/m-p/2330936#M99968</link>
      <description>We usually test the job simply in the same way as we test complete programs. We export the job as standalone job and create a master output (a database table/file or what ever) check that carefully and rerun the job. You can do this with JUnit or - what we do - we use the robot framework because it gives us the opportunity to extend that and the actual test cases can be defined in a nearly natural language.</description>
      <pubDate>Thu, 19 May 2016 17:41:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Automated-Unit-testing-for-talend-open-studio-data-integration/m-p/2330936#M99968</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-05-19T17:41:38Z</dc:date>
    </item>
    <item>
      <title>Re: Automated Unit testing for talend open studio data integration</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Automated-Unit-testing-for-talend-open-studio-data-integration/m-p/2330937#M99969</link>
      <description>Hi jlolling,
&lt;BR /&gt;Thanks for your reply.
&lt;BR /&gt;But I lost you when you were talking about master output.
&lt;BR /&gt;Do you have an example or a documentation? Also, do you have any idea on how TUJ Automation can be used?
&lt;BR /&gt;Thanks</description>
      <pubDate>Mon, 23 May 2016 06:23:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Automated-Unit-testing-for-talend-open-studio-data-integration/m-p/2330937#M99969</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-05-23T06:23:39Z</dc:date>
    </item>
  </channel>
</rss>

