<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>Technical Blog</title>
    <link>https://grep.elasticpath.com/community/techblog/blog</link>
    <description />
    <pubDate>Wed, 18 May 2011 03:53:01 GMT</pubDate>
    <generator>Clearspace 2.5.7 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2011-05-18T03:53:01Z</dc:date>
    <item>
      <title>The Importance of tearDown() in JUnit 3</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/06/14/the-importance-of-teardown-in-junit-3</link>
      <description>Why is memory never enough? &amp;nbsp; Our customer project has a few dozens of integration JUnit tests.  Those are tests coded as JUnit tests loading the core application Spring context to verify the correct behavior of certain parts of our application.</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">testing</category>
      <pubDate>Tue, 14 Jun 2011 23:32:07 GMT</pubDate>
      <author>yanko.zhivkov@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/06/14/the-importance-of-teardown-in-junit-3</guid>
      <dc:date>2011-06-14T23:32:07Z</dc:date>
      <clearspace:dateToText>8 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/the-importance-of-teardown-in-junit-3</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1141</wfw:commentRss>
    </item>
    <item>
      <title>How-to: Use com.elasticpath.test.application in your Maven project for integration testing</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2011/03/25/how-to-use-comelasticpathtestapplication-in-your-maven-project-for-integration-testing</link>
      <description>Overview: Elastic Path 6.2.2 comes with a little known project called "com.elasticpath.test.application". This project is used as a connector to enable integration testing by exposing the spring application context to hook up Elastic Path core services</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">customization</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">testing</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">maven</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">6.2.2</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">test.application</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">com.elasticpath.test.application</category>
      <pubDate>Fri, 25 Mar 2011 18:33:21 GMT</pubDate>
      <author>tommy.chan@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2011/03/25/how-to-use-comelasticpathtestapplication-in-your-maven-project-for-integration-testing</guid>
      <dc:date>2011-03-25T18:33:21Z</dc:date>
      <clearspace:dateToText>1 year, 1 week ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/how-to-use-comelasticpathtestapplication-in-your-maven-project-for-integration-testing</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1133</wfw:commentRss>
    </item>
    <item>
      <title>Troubleshooting load-related issues with JMeter</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2010/07/09/troubleshooting-load-related-issues-with-jmeter</link>
      <description>Recently, I needed to reproduce a problem that was only occurring when the storefront was under heavy load. As a developer, I cannot easily generate realistic load in my environment and I don't have access to a live production system, so I used JMeter</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">performance</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">storefront</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">testing</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">load</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">jmeter</category>
      <pubDate>Sat, 10 Jul 2010 00:39:50 GMT</pubDate>
      <author>edison.shimabukuro@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2010/07/09/troubleshooting-load-related-issues-with-jmeter</guid>
      <dc:date>2010-07-10T00:39:50Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/troubleshooting-load-related-issues-with-jmeter</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1112</wfw:commentRss>
    </item>
    <item>
      <title>Automated Selenium Testing with Maven</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2010/06/16/automated-selenium-testing-with-maven</link>
      <description>(Or: How to Copy and Paste XML Your Way to Greatness) &amp;nbsp; We have a truckload of Selenium tests that poke and probe away at the user interface of our project here at EP. We realized it would be awesome if this testing could just automagically happen</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">testing</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">maven</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">hudson</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">selenium</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">tomcat</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">testng</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">cargo</category>
      <pubDate>Thu, 17 Jun 2010 01:25:38 GMT</pubDate>
      <author>james.atwill@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2010/06/16/automated-selenium-testing-with-maven</guid>
      <dc:date>2010-06-17T01:25:38Z</dc:date>
      <clearspace:dateToText>1 year, 7 months ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/automated-selenium-testing-with-maven</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1111</wfw:commentRss>
    </item>
    <item>
      <title>Single vs. Multi Page Checkout</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2010/03/09/single-vs-multi-page-checkout</link>
      <description>A while back, I wrote about our decision to  change to a two-page checkout process , with the main goal being to reduce checkout process abandonment. We piloted this checkout process on the  Hockey Canada store  and the results were extremely positive,</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">storefront</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">testing</category>
      <pubDate>Tue, 09 Mar 2010 17:04:04 GMT</pubDate>
      <author>janislanka@gmail.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2010/03/09/single-vs-multi-page-checkout</guid>
      <dc:date>2010-03-09T17:04:04Z</dc:date>
      <clearspace:dateToText>1 year, 12 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/single-vs-multi-page-checkout</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1095</wfw:commentRss>
    </item>
    <item>
      <title>Checkout Revisited</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2009/10/01/checkout-revisited</link>
      <description>The checkout process is quite possibly the  scariest part  of the online shopping experience. Customers get anxious about divulging sensitive personal information, not to mention parting with their hard-earned cash. Long and complicated customer</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">storefront</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">testing</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">checkout</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">design</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">ui</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">wireframes</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">conversion</category>
      <pubDate>Thu, 01 Oct 2009 20:58:52 GMT</pubDate>
      <author>janislanka@gmail.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2009/10/01/checkout-revisited</guid>
      <dc:date>2009-10-01T20:58:52Z</dc:date>
      <clearspace:dateToText>2 years, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/checkout-revisited</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1084</wfw:commentRss>
    </item>
    <item>
      <title>Using Selenium-RC with Squish for combined storefront/CM client testing</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2009/07/09/using-selenium-rc-with-squish-for-combined-storefrontcm-client-testing</link>
      <description>If you've been reading the blog posts by the Elastic Path QA team, you already know that we use  Selenium-RC  to automate storefront testing and  Squish  for automated Commerce Manager client testing.  Selenium Remote Control ( Selenium-RC)  is an</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">storefront</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">qa</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">testing</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">cm_client</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">selenium</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">automated_testing</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">squish</category>
      <pubDate>Thu, 09 Jul 2009 16:29:11 GMT</pubDate>
      <author>danny.yan@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2009/07/09/using-selenium-rc-with-squish-for-combined-storefrontcm-client-testing</guid>
      <dc:date>2009-07-09T16:29:11Z</dc:date>
      <clearspace:dateToText>2 years, 7 months ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/using-selenium-rc-with-squish-for-combined-storefrontcm-client-testing</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1072</wfw:commentRss>
    </item>
    <item>
      <title>Under the Hood of Elastic Path's Automated FIT Testing Framework</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2009/04/03/under-the-hood-of-elastic-paths-automated-fit-testing-framework</link>
      <description>In addition to manual test cases and unit tests, Elastic Path relies on FIT (Framework for Integrated Test). FIT allows testers to write tests without writing any code. FIT is a good framework for use with EP because we usually have a set of defined</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">qa</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">testing</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">fit</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">fixture</category>
      <pubDate>Sat, 04 Apr 2009 00:18:06 GMT</pubDate>
      <author>tommy.chan@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2009/04/03/under-the-hood-of-elastic-paths-automated-fit-testing-framework</guid>
      <dc:date>2009-04-04T00:18:06Z</dc:date>
      <clearspace:dateToText>2 years, 10 months ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/under-the-hood-of-elastic-paths-automated-fit-testing-framework</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1056</wfw:commentRss>
    </item>
    <item>
      <title>Get more out of your unit tests with JUnitPerf</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2009/03/03/get-more-out-of-your-unit-tests-with-junitperf</link>
      <description>Performance testing is a task often left to the last stages of software development, after the code is checked in, passed QA for functional testing, and no longer fresh in the minds of developers who wrote it. With JUnitPerf, you can leverage your</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">performance</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">junit</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">testing</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">java</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">junitperf</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">unit</category>
      <pubDate>Wed, 04 Mar 2009 00:07:07 GMT</pubDate>
      <author>daniel.wu@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2009/03/03/get-more-out-of-your-unit-tests-with-junitperf</guid>
      <dc:date>2009-03-04T00:07:07Z</dc:date>
      <clearspace:dateToText>2 years, 12 months ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/get-more-out-of-your-unit-tests-with-junitperf</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1036</wfw:commentRss>
    </item>
    <item>
      <title>Automated Testing With Selenium</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2009/02/23/automated-testing-with-selenium</link>
      <description>Selenium is a suite of free, community-developed tools for automated testing of web applications. It provides test recording and playback, and supports test playback in both Firefox and Internet Explorer. For our testing purposes, we use two tools in</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">qa</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">testing</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">selenium</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">automated_testing</category>
      <pubDate>Mon, 23 Feb 2009 16:52:51 GMT</pubDate>
      <author>kevin.cleathero@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2009/02/23/automated-testing-with-selenium</guid>
      <dc:date>2009-02-23T16:52:51Z</dc:date>
      <clearspace:dateToText>2 years, 11 months ago</clearspace:dateToText>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/automated-testing-with-selenium</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1039</wfw:commentRss>
    </item>
    <item>
      <title>Testing EP Web Services with SoapUI and Groovy</title>
      <link>https://grep.elasticpath.com/community/techblog/blog/2009/02/09/testing-ep-web-services-with-soapui-and-groovy</link>
      <description>Elastic Path supports web services via the Simple Object Access Protocol (SOAP), and provides support for obtaining and updating information for orders. The problem is, how do we actually test the web services component? One could write a custom SOAP</description>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">web_services</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">qa</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">testing</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">wsdl</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">soap</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">soapui</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">groovy</category>
      <category domain="https://grep.elasticpath.com/community/techblog/blog/tags">xpath</category>
      <pubDate>Tue, 10 Feb 2009 00:02:59 GMT</pubDate>
      <author>tommy.chan@elasticpath.com</author>
      <guid>https://grep.elasticpath.com/community/techblog/blog/2009/02/09/testing-ep-web-services-with-soapui-and-groovy</guid>
      <dc:date>2009-02-10T00:02:59Z</dc:date>
      <clearspace:dateToText>2 years, 12 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
      <wfw:comment>https://grep.elasticpath.com/community/techblog/blog/comment/testing-ep-web-services-with-soapui-and-groovy</wfw:comment>
      <wfw:commentRss>https://grep.elasticpath.com/community/techblog/blog/feeds/comments?blogPost=1034</wfw:commentRss>
    </item>
  </channel>
</rss>


