<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Maurizio Mangione on Medium]]></title>
        <description><![CDATA[Stories by Maurizio Mangione on Medium]]></description>
        <link>https://medium.com/@granze?source=rss-ec7d469e0827------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pRXLtyCEvD4mHEuEBHGnng.jpeg</url>
            <title>Stories by Maurizio Mangione on Medium</title>
            <link>https://medium.com/@granze?source=rss-ec7d469e0827------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 10:50:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@granze/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Are Web Components a thing?]]></title>
            <link>https://medium.com/google-developer-experts/are-web-components-a-thing-5a116b1da7e4?source=rss-ec7d469e0827------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a116b1da7e4</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[custom-elements]]></category>
            <category><![CDATA[web-components]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[shadow-dom]]></category>
            <dc:creator><![CDATA[Maurizio Mangione]]></dc:creator>
            <pubDate>Tue, 23 Oct 2018 14:55:06 GMT</pubDate>
            <atom:updated>2018-10-24T12:46:05.383Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VueUSoUr5GaI5L0m" /><figcaption>“brown block lot” by <a href="https://unsplash.com/@mangofantasy?utm_source=medium&amp;utm_medium=referral">Tim Johnson</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Talking to people that are not really into Web Components I found out that they feel like Web Components are not going anywhere. This probably because there was a huge hype around them since, let’s say, a year ago but not that much over the past months.</p><p>For those who paid attention, a really important news came out lately. First of all, Microsoft announced they started working on the implementation of Custom Elements and Shadow DOM. This is huge because, since a couple of weeks ago, there were no signs from the Edge Team. <br>The support in Firefox has finally landed in version 63 out today! From my point of view then, the future looks really bright.</p><p>Even though Web Components specification is being around for years now, it seems that a lot of developers weren&#39;t able to grasp the basics of this standard. There are a lot of misconceptions and myths around this spec. Let’s try to clarify some aspects.</p><h3>You can’t pass objects as properties (true or false?)</h3><h3>MICHAEL JACKSON on Twitter</h3><p>🎯 Adam nailed it here. This is a huge thing that web components could learn from React that would increase their usability 100x. https://t.co/veDQlZgWVC</p><p>I was puzzled after reading this tweet because I realized that even experience developers didn’t get how Custom Elements work. I’m not asserting they have to like them, but that you can’t pass an object as a property is a totally <strong>false</strong> statement.<br>So, how do I pass an object as a property then? Short answer: via <em>properties</em>! :)<br>Take a look at the following image to get a better idea.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OYVxzLdjkUpxK7XYY9yDjg.png" /><figcaption>Property values are managed with getters and setters</figcaption></figure><p>In the example above, we define a Custom Element containing a property called myObj. To pass an object to a property you first need to select your element</p><p>let el = document.querySelector(&#39;my-el&#39;)</p><p>and then assign a value, in this case a standard object, using the dot notation</p><p>el.myObj = {a: &#39;test&#39;}</p><p>That’s it.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fcodepen.io%2Fgranze%2Fembed%2Fpreview%2FVEzmNZ%3Fheight%3D600%26slug-hash%3DVEzmNZ%26default-tabs%3Djs%2Cresult%26host%3Dhttps%3A%2F%2Fcodepen.io&amp;url=https%3A%2F%2Fcodepen.io%2Fgranze%2Fpen%2FVEzmNZ&amp;image=https%3A%2F%2Fs3-us-west-2.amazonaws.com%2Fi.cdpn.io%2F2205519.VEzmNZ.small.85f07e03-824f-42dd-9f43-75671748a35a.png&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=codepen" width="800" height="600" frameborder="0" scrolling="no"><a href="https://medium.com/media/fe1d752c12a5fbb324f00b10b45deac1/href">https://medium.com/media/fe1d752c12a5fbb324f00b10b45deac1/href</a></iframe><h3>Why people are still confused about that?</h3><p>The issue is that most developers talk about ‘<em>properties’</em> when they actually mean ‘<em>attributes’.</em> The two can be related to each other, for example I can reflect properties to attributes but this isn’t needed all the time.</p><p>With attributes you can pass only strings or use them as a boolean value. In the latter case, an attribute returns true if it exists, false if not.<br>To be clear, in the following example <strong>att === true</strong>.</p><p>&lt;my-component att=&quot;false&quot;&gt;&lt;/my-component&gt;</p><p>Is it misleading or not ergonomic? You can have your own opinion about that but this is how HTML always worked. From my point of view, this is <em>consistent</em>.</p><h3>Is Custom Elements’ API bad?</h3><p>Some people are complaining about the verbosity of the Custom Elements API and they think that is totally useless and bad designed. <br>The verbosity part here is true. Take the Codepen example and imagine you have ten properties instead of one. You’ll end up with ten getter and ten setter, in most cases they differ just for the name of the property but they do the same thing for each of them.<br>This is not convenient for sure, on the other hand, I don’t think this means the API is bad.<br>This is a low-level API and isn’t always handy to use it directly, but you can build on top of that. You don’t have to develop an entire framework or library, you can just write some abstractions. If you don&#39;t feel like to do your own abstraction, try <a href="https://github.com/WebReflection/hyperHTML-Element">hyperHTML-Element</a> or <a href="https://github.com/Polymer/lit-element">lit-element</a> they are great!</p><p>That said, if you are still comparing Web Components against React, Vue, Polymer, whatever-framework, you’re missing the point and, honestly, is not fair.</p><h3>Web Components work everywhere</h3><p>This statement is unfortunately not quite accurate. Is true that this is the big promise of Web Components, but <em>things don’t always work seamlessly. <br></em>If you want to learn more about interoperability between Web Components, libraries and frameworks, I strongly suggest you to take a look at <a href="https://custom-elements-everywhere.com/">Custom Element Everywhere</a> by <a href="https://medium.com/u/d712d6fb229b">Rob Dodson</a>. You will find out where they work, where they don&#39;t and the potential fixes.</p><h3>So, are Web Components a thing?</h3><p>From my point of view yes, absolutely. Maybe they are not for you (yet), but this doesn’t mean they are bad or useless. <br>I think this is a good moment to start playing with Custom Elements and Shadow DOM. Getting to know Web Components in depth maybe will be useful to change your mind in case you are still skeptical about this standard.</p><p>If you are interested in this topic and you want to stay in touch, <a href="https://twitter.com/granze">follow me on Twitter.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a116b1da7e4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-developer-experts/are-web-components-a-thing-5a116b1da7e4">Are Web Components a thing?</a> was originally published in <a href="https://medium.com/google-developer-experts">Google Developer Experts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Polymer Testing Tips]]></title>
            <link>https://medium.com/google-developer-experts/polymer-testing-tips-f217ba94a64?source=rss-ec7d469e0827------2</link>
            <guid isPermaLink="false">https://medium.com/p/f217ba94a64</guid>
            <category><![CDATA[polymer]]></category>
            <category><![CDATA[unit-testing]]></category>
            <category><![CDATA[web-components]]></category>
            <dc:creator><![CDATA[Maurizio Mangione]]></dc:creator>
            <pubDate>Tue, 05 Jan 2016 14:11:07 GMT</pubDate>
            <atom:updated>2016-01-07T10:18:38.480Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2DqXGPDiF0mpcgYvUhIwMQ.jpeg" /></figure><p>In my <a href="https://medium.com/@granze/polymer-unit-testing-d6a69910dc31">previous article</a>, I wrote about how to get started with unit testing in Polymer. The goal was to setup the testing environment and to write your first tests using best practices and taking advantage of the nice tools Polymer offers.</p><p>In this article, I’ll cover more advanced topics such as user interaction simulation, automatic testing with Continuous Integration, testing on multiple OS/browsers and more useful tips.</p><h3>Mock User Interactions</h3><p><a href="https://github.com/PolymerElements/iron-test-helpers">Iron Test Helpers</a> provides a set of methods to simulate mouse or keyboard interaction with an element.</p><p>In the example below, you want to be sure that your start button will be disabled after clicking it to avoid users to click on it twice. To do this, you just need to attach a listener to the button reference and use the <strong>tap</strong> method to simulate the click/tap action.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/00d14d6bec682648edc9624cd3bdddce/href">https://medium.com/media/00d14d6bec682648edc9624cd3bdddce/href</a></iframe><h3>Accessibility tests</h3><p>Accessibility is a very important aspect to keep in mind when building new elements or applications. The good news is that testing accessibility in Polymer is a piece of cake.</p><p>The <strong>a11ySuite()</strong> method built in the WCT, runs accessibility audits for a given <em>&lt;test-fixture&gt;</em>. Pass the element reference as an argument to the a11Suite<strong> </strong>method and you are done. That’s easy, isn’t it?</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/6dcb2d0cc69a3a7dbc5a09be1a4e389b/href">https://medium.com/media/6dcb2d0cc69a3a7dbc5a09be1a4e389b/href</a></iframe><blockquote>You can run the same tests using the Accessibility Developer Tools <a href="https://chrome.google.com/webstore/detail/accessibility-developer-t/fpkknkljclfencbdbgkenhalefipecmb">Chrome extension</a>.</blockquote><h3>Test both Shadow and Shady DOM</h3><p>Unfortunately, not all browsers support Shadow DOM yet, for that reason Polymer uses <a href="https://www.polymer-project.org/1.0/articles/shadydom.html">Shady DOM</a> instead by default. Shady DOM is compatible with Shadow DOM, but the rendered DOM tree is different. So, if you want to be sure your element works fine in both cases, you need to test it properly.</p><p>To do this, you just need to call your test suite twice: once as you normally do and once passing <strong>dom=shadow</strong> as a query parameter.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b2a99de9920669cb3bb139c9833d4cb7/href">https://medium.com/media/b2a99de9920669cb3bb139c9833d4cb7/href</a></iframe><h3>CI Integration and Travis Badge</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*Ykmd8AevFEIBlr3_k600sA.png" /></figure><p>WCT needs a real browser to run and, in the past, I was wondering about how to run my Polymer tests in a continuous integration environment like Travis. Well, It’s easier than you may image, it’s a matter of adding a couple more lines to your <strong>.travis.yml</strong> file.</p><p>First of all, you need to install Bower, web-component-tester, and your element dependencies.<br>Since Travis has xvfb (X Virtual Framebuffer) and Firefox installed, you just need to export the display and start xvfb.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d2ce1b7be7291ce4a2b0484f86e5f535/href">https://medium.com/media/d2ce1b7be7291ce4a2b0484f86e5f535/href</a></iframe><h3>Remote Testing with Sauce Labs</h3><p><a href="https://saucelabs.com/">Sauce Labs</a> allows you to run tests on multiple OS/Browsers in the cloud, and it’s free for open source projects. To start using the service, you need to <a href="https://saucelabs.com/signup">sign up</a> first.</p><p>WCT has a built-in plugin for Sauce Labs so, the only thing you need to do, is to pass some options to WCT:</p><pre>wct --sauce &#39;default&#39; --sauce-username &lt;username&gt; --sauce-access-key &lt;access-key&gt;</pre><p>In the first option (<em>sauce</em>) you can pass a list of OS/browsers you want to run the tests on or, as in the example above, you can set the value to ‘default’ to run the tests in the predefined browsers.</p><p>Since you have to be authenticated for the test, you need to pass you username and access key as well. You can find this information in your <a href="https://saucelabs.com/beta/user-settings">user settings page</a>.</p><p>If you want to specify your own list of browser, a handy way to do it is to list them in a file called <strong>wct.conf.json</strong> you can put in the root of your project.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/fd619c2e52ef072b163ce6cba129a6e4/href">https://medium.com/media/fd619c2e52ef072b163ce6cba129a6e4/href</a></iframe><h3>Travis + Sauce Labs</h3><p>If you are interested in learning how to integrate Travis CI with Sauce Labs, watch Rob Dodson in the following Polycasts episode.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fafy_EEq_4Go%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dafy_EEq_4Go%26feature%3Dyoutu.be&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fafy_EEq_4Go%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d57158e3bc57166122ad3ba7ec804a2f/href">https://medium.com/media/d57158e3bc57166122ad3ba7ec804a2f/href</a></iframe><h3><strong>Learn more</strong></h3><p>Most of all example in this article are taken from the <strong>&lt;flip-clock&gt;</strong> element I wrote. I suggest you to browse <a href="https://github.com/Granze/flip-clock">the code</a> on Github to get a better overview.</p><p>You can learn more about testing Polymer elements watching these great Polycasts episodes.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FYBNBr9ECXLo%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DYBNBr9ECXLo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FYBNBr9ECXLo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bf679a9ca6f4520e66dc524962ad0775/href">https://medium.com/media/bf679a9ca6f4520e66dc524962ad0775/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F_9qARcdCAn4%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D_9qARcdCAn4%26feature%3Dyoutu.be&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F_9qARcdCAn4%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/687218bd1fd2784169fc919389c3428a/href">https://medium.com/media/687218bd1fd2784169fc919389c3428a/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f217ba94a64" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-developer-experts/polymer-testing-tips-f217ba94a64">Polymer Testing Tips</a> was originally published in <a href="https://medium.com/google-developer-experts">Google Developer Experts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Polymer Unit Testing]]></title>
            <link>https://medium.com/google-developer-experts/polymer-unit-testing-d6a69910dc31?source=rss-ec7d469e0827------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6a69910dc31</guid>
            <category><![CDATA[polymer]]></category>
            <category><![CDATA[web-components]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Maurizio Mangione]]></dc:creator>
            <pubDate>Fri, 14 Aug 2015 16:14:28 GMT</pubDate>
            <atom:updated>2015-09-02T14:02:25.564Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<p>In the front-end world, testing is a weird topic. Developers know how much testing is important, but lots of them don’t embrace this practice. This is because testing is often perceived as a time consuming and a difficult task.</p><p>Sometimes the harder part is just getting started, and this is not only specific to testing. For this reason, in this article we will go through the basics, leaving more advanced topics and some details out. Once you have grasped the core concepts and got your first tests working, I bet you’ll be more motivated to dig deeper into the topic.</p><h4>Web component tester</h4><p>Polymer comes with an handy tool called web-component-tester (WCT), that will make testing your elements really easy.</p><p>If you are used to test your applications, your first thought is that you don’t want to learn a new tool, right? The good news is that you probably already know the tools WCT is built on. If you are already familiar with <a href="http://mochajs.org/">Mocha</a>, <a href="http://chaijs.com/">Chai</a> and <a href="http://sinonjs.org/">Sinon</a>, you are good to go.<br>If you are new to testing and you never heard those names before, don’t worry and keep reading.</p><h3>Setup</h3><p>First, you need to install WCT via NPM globally.</p><pre>npm install -g web-component-tester</pre><p>As a test suite you can use an .html file like the following:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/13cd7c95ca27dd525d39df002b6719dd/href">https://medium.com/media/13cd7c95ca27dd525d39df002b6719dd/href</a></iframe><p>As you can see, your test suite looks almost the same as the HTML file you normally use to contain your Polymer elements. The only difference is you need to include <strong>browser.js</strong>, that is in charge of loading all the required libraries for you, and <strong>test-fixture-mocha.js</strong> of which I’ll talk in a moment.</p><h3>Writing a test</h3><p>In this article you will test a Polymer element called &lt;flip-clock&gt;.</p><figure><a href="https://github.com/Granze/flip-clock"><img alt="" src="https://cdn-images-1.medium.com/max/544/1*sKHQ9YlL_Uwz9_PXLEn7ow.png" /></a><figcaption>Check out the &lt;flip-clock&gt; source code on Github clicking on the image</figcaption></figure><p>The first thing you need to do, is to import the &lt;flip-clock&gt; element into the page. Along with it, import the &lt;test-fixture&gt; element as well.</p><blockquote>The &lt;test-fixture&gt; element can simplify the exercise of consistently resetting a test suite’s DOM. To use it, wrap the test suite’s DOM as a template.<br>You’ll find out later why it is crucial for this test.</blockquote><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/66226c29c9a853de52b945ad6ef5cdda/href">https://medium.com/media/66226c29c9a853de52b945ad6ef5cdda/href</a></iframe><p>You are ready to write the actual test.</p><p>Add inside a script tag the <em>describe</em> function with the element’s name under test, in this case &lt;flip-clock&gt;. In the <em>beforeEach</em> function we reference our element with its <em>id</em>. As you probably imagine, this function is called before each test.<br>The <em>context</em> function is not mandatory, but it is a convenient way to group up our tests.</p><pre>describe(&#39;&lt;flip-clock&gt;&#39;, function() {<br>  var clock;<br><br>  beforeEach(function() {<br>    clock = fixture(&#39;clock&#39;);<br>  });</pre><pre>  context(&#39;common tests&#39;, function() {<br>  <br>  });<br>});</pre><p>The element exposes the showButtons property and its default value is <em>false</em>. When it’s <em>true</em>, the command buttons show up. In order to toggle their visibility, you need to add the <em>show-button</em> attribute on your custom element.</p><p>First, set the <em>show-buttons</em> attribute on the element, then make sure the <em>showButtons</em> property is true. After that, check if the buttons, contained in a <em>div</em> with the <em>buttons</em> class, are actually visible.</p><blockquote>Since WCT uses <strong>Mocha</strong> and <strong>Chai</strong>, you can choose between all the interfaces those libraries provide. I personally like the Chai’s <em>BDD</em> style with the <a href="http://chaijs.com/api/bdd/"><strong><em>expect</em></strong></a> interface, but you can choose the one you like the most.</blockquote><pre><em>it</em>(&#39;should display the command buttons&#39;, function() {<br>  clock.setAttribute(&#39;show-buttons&#39;, &#39;true&#39;);<br>  expect(clock.showButtons).to.be.equal(true);<br>  expect(clock.querySelector(&#39;.buttons&#39;).attributes)<br>  .to.have.ownProperty(&#39;visible&#39;);<br>});</pre><p>Now repeat the test without setting the <em>show-buttons</em> attribute. In this case we expect the <em>showButtons</em> property to be false and the buttons are not visible.</p><pre><em>it</em>(&#39;should not display the command buttons&#39;, function() {<br>  expect(clock.showButtons).to.be.equal(false);<br>  expect(clock.querySelector(&#39;.buttons&#39;).attributes)<br>  .to.not.have.ownProperty(&#39;visible&#39;);<br>});</pre><p>You’ll end up with this code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cbe234ff9f481b847f4e47de6b67bf2d/href">https://medium.com/media/cbe234ff9f481b847f4e47de6b67bf2d/href</a></iframe><h3>Running a test</h3><p>To do that, open a terminal in the element’s root directory and launch the web component tester with the <em>wct </em>command<em>.</em> It will automatically run the tests in all the browsers installed on your machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*81jiojIYeoWtH8ocyPrcQg.png" /></figure><p>Wow, your first two tests just passed! But, What would have happened if you have had not used the &lt;test-fixture&gt; element? The short answer is: the second test would fail.<br>This because you set the show-buttons attribute to true and, in the following test, you expect <em>showButtons </em>to be false.<br>With &lt;text-fixture&gt; (and the <em>beforeEach</em> function) you will run every test on a “clean” element.</p><h3>What next?</h3><p>Take a look at the &lt;flip-clock&gt; project on <a href="https://github.com/Granze/flip-clock">Github</a> to learn more on how this element is built and to check out the other tests I wrote for this element.<br>You can find more information about &lt;test-fixture&gt; on its <a href="https://github.com/PolymerElements/test-fixture">repository</a>.</p><p>The web-component-tester <a href="https://github.com/Polymer/web-component-tester/blob/master/README.md">README.md</a> is also a great resource to get started.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6a69910dc31" width="1" height="1" alt=""><hr><p><a href="https://medium.com/google-developer-experts/polymer-unit-testing-d6a69910dc31">Polymer Unit Testing</a> was originally published in <a href="https://medium.com/google-developer-experts">Google Developer Experts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>