<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Yasmine on Micha Kops&#39; Tech Notes</title>
    <link>https://www.hascode.com/tags/yasmine/</link>
    <description>Recent content in Yasmine on Micha Kops&#39; Tech Notes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>Copyright © 2010 - 2025 Micha Kops. #e9d956c0c0154a221ad83c925346a8fa0e72f866</copyright>
    <lastBuildDate>Sun, 04 May 2014 00:00:00 +0200</lastBuildDate>
    <atom:link href="https://www.hascode.com/tags/yasmine/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Running JavaScript Tests with Maven, Jasmine and PhantomJS</title>
      <link>https://www.hascode.com/running-javascript-tests-with-maven-jasmine-and-phantomjs/</link>
      <pubDate>Sun, 04 May 2014 00:00:00 +0200</pubDate>
      <guid>https://www.hascode.com/running-javascript-tests-with-maven-jasmine-and-phantomjs/</guid>
      <description>&lt;div id=&#34;preamble&#34;&gt;
&lt;div class=&#34;sectionbody&#34;&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;Sometimes in a project there is the need to run tests for your client-side code, written in JavaScript from a Maven build.&lt;br/&gt;
One reason might be that Maven manages a complex build life-cycle in your project and you need a close integration for your JavaScript tests, another one might be that you’re in an environment where it is complicated to install and manage additional software like an integration- or build-server.&lt;/p&gt;
&lt;/div&gt;</description>
    </item>
  </channel>
</rss>
