<?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 splitting integration test and Unit tests in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/splitting-integration-test-and-Unit-tests/m-p/83607#M52731</link>
    <description>&lt;P&gt;I've inherited a load of Junit test, but these tests (apart from most not working) are a mixture of actual unit test and integration tests (requiring external systems, db etc).&lt;/P&gt;&lt;P&gt;So I'm trying to think of a way to actually separate them out, so that I can run the unit test nice and quickly and the integration tests after that.&lt;/P&gt;&lt;P&gt;The options are..&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Split them into separate directories.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Move to Junit4 (from v3) and annotate the classes to separate them.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Use a file naming convention to tell what a class is , i.e. AdapterATest and AdapterAIntergrationTest.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;3 has the issue that Eclipse has the option to "Run all tests in the selected project/package or folder". So it would make it very hard to just run the integration tests.&lt;/P&gt;&lt;P&gt;2: runs the risk that developers might start writing integration tests in unit test classes and it just gets messy.&lt;/P&gt;&lt;P&gt;1: Seems like the neatest solution, but my gut says there must be a better solution out there.&lt;/P&gt;&lt;P&gt;So that is my question, how do you lot break apart integration tests and proper unit tests?&lt;/P&gt;</description>
    <pubDate>Tue, 02 Aug 2022 05:51:46 GMT</pubDate>
    <dc:creator>VeroniTasingoli</dc:creator>
    <dc:date>2022-08-02T05:51:46Z</dc:date>
    <item>
      <title>splitting integration test and Unit tests</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/splitting-integration-test-and-Unit-tests/m-p/83607#M52731</link>
      <description>&lt;P&gt;I've inherited a load of Junit test, but these tests (apart from most not working) are a mixture of actual unit test and integration tests (requiring external systems, db etc).&lt;/P&gt;&lt;P&gt;So I'm trying to think of a way to actually separate them out, so that I can run the unit test nice and quickly and the integration tests after that.&lt;/P&gt;&lt;P&gt;The options are..&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;Split them into separate directories.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Move to Junit4 (from v3) and annotate the classes to separate them.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Use a file naming convention to tell what a class is , i.e. AdapterATest and AdapterAIntergrationTest.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;3 has the issue that Eclipse has the option to "Run all tests in the selected project/package or folder". So it would make it very hard to just run the integration tests.&lt;/P&gt;&lt;P&gt;2: runs the risk that developers might start writing integration tests in unit test classes and it just gets messy.&lt;/P&gt;&lt;P&gt;1: Seems like the neatest solution, but my gut says there must be a better solution out there.&lt;/P&gt;&lt;P&gt;So that is my question, how do you lot break apart integration tests and proper unit tests?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Aug 2022 05:51:46 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/splitting-integration-test-and-Unit-tests/m-p/83607#M52731</guid>
      <dc:creator>VeroniTasingoli</dc:creator>
      <dc:date>2022-08-02T05:51:46Z</dc:date>
    </item>
  </channel>
</rss>

