<?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 Any examples of integration tests with good maintainability on Github? in Integration and Testing</title>
    <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Any-examples-of-integration-tests-with-good-maintainability-on/m-p/74778#M46535</link>
    <description>&lt;DIV class="_3xX726aBn29LDbsDtzr_6E _1Ap4F5maDtT1E1YuCiaO0r D3IL3FD0RFy_mkKLPwL4"&gt;&lt;DIV class="_292iotee39Lmt0MkQZ2hPV RichTextJSON-root"&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;By maintainability, I mean shows good patterns and how to setup the data for each tests. A problem that I often run into is, integration tests often requires existing data to be there. For example, if I want to test AccountService.payAccount(), perhaps I'd need existing users, accounts, anything related to accounts (bank accounts, history, etc). What's a good pattern of setting that up for each integration test?&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Sat, 23 Jan 2021 20:27:55 GMT</pubDate>
    <dc:creator>polymacin29</dc:creator>
    <dc:date>2021-01-23T20:27:55Z</dc:date>
    <item>
      <title>Any examples of integration tests with good maintainability on Github?</title>
      <link>https://community.developer.cybersource.com/t5/Integration-and-Testing/Any-examples-of-integration-tests-with-good-maintainability-on/m-p/74778#M46535</link>
      <description>&lt;DIV class="_3xX726aBn29LDbsDtzr_6E _1Ap4F5maDtT1E1YuCiaO0r D3IL3FD0RFy_mkKLPwL4"&gt;&lt;DIV class="_292iotee39Lmt0MkQZ2hPV RichTextJSON-root"&gt;&lt;P class="_1qeIAgB0cPwnLhDF9XSiJM"&gt;By maintainability, I mean shows good patterns and how to setup the data for each tests. A problem that I often run into is, integration tests often requires existing data to be there. For example, if I want to test AccountService.payAccount(), perhaps I'd need existing users, accounts, anything related to accounts (bank accounts, history, etc). What's a good pattern of setting that up for each integration test?&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Sat, 23 Jan 2021 20:27:55 GMT</pubDate>
      <guid>https://community.developer.cybersource.com/t5/Integration-and-Testing/Any-examples-of-integration-tests-with-good-maintainability-on/m-p/74778#M46535</guid>
      <dc:creator>polymacin29</dc:creator>
      <dc:date>2021-01-23T20:27:55Z</dc:date>
    </item>
  </channel>
</rss>

