<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>testing</title><description/><link>https://kevinquillen.com</link><language>en</language><item><title>Testing Drupal with Cypress in Docker</title><link>https://kevinquillen.com/testing-drupal-cypress-docker</link><guid isPermaLink="false">327 at https://kevinquillen.com</guid><description>
&lt;span property=&quot;schema:name&quot;&gt;Testing Drupal with Cypress in Docker&lt;/span&gt;

            &lt;div property=&quot;schema:text&quot; class=&quot;text-content clearfix field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;In a &lt;a href=&quot;https://kevinquillen.com/preserving-cookies-pantheon&quot;&gt;previous post&lt;/a&gt;, I discussed how to use custom cookies on Pantheon and how to provide a browser based functional test using the WebDriverTestBase class from Drupal 8.&lt;/p&gt;

&lt;p&gt;While it worked great, these tests can be a bit of a bear to get up and running locally. Installing Selenium and chromedriver can be daunting and unwieldy and difficult to replicate across members of the team so they can write and run tests locally. Leveraging the same stack&amp;nbsp;in CI can be an equal challenge.&lt;/p&gt;&lt;/div&gt;
      
&lt;span rel=&quot;schema:author&quot;&gt;&lt;span lang about=&quot;https://kevinquillen.com/user/1&quot; typeof=&quot;schema:Person&quot; property=&quot;schema:name&quot; datatype&gt;Kevin&lt;/span&gt;&lt;/span&gt;

&lt;span property=&quot;schema:dateCreated&quot; content=&quot;2020-02-24T15:00:35+00:00&quot;&gt;&lt;time datetime=&quot;2020-02-24T10:00:35-05:00&quot; title=&quot;Monday, February 24, 2020 - 10:00&quot;&gt;February 24th, 2020&lt;/time&gt;
&lt;/span&gt;
</description><pubDate>Mon, 24 Feb 2020 15:00:35 GMT</pubDate><dc:creator>Kevin</dc:creator></item><item><title>Creating a Custom Token in Drupal 8</title><link>https://kevinquillen.com/creating-custom-token-drupal-8</link><guid isPermaLink="false">325 at https://kevinquillen.com</guid><description>
&lt;span property=&quot;schema:name&quot;&gt;Creating a Custom Token in Drupal 8&lt;/span&gt;

            &lt;div property=&quot;schema:text&quot; class=&quot;text-content clearfix field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Tokens represent an inline&amp;nbsp;replacement&amp;nbsp;when evaluating or rendering text. In Drupal, the Token module goes all the way back to Drupal 4.x and &lt;a href=&quot;https://www.drupal.org/project/token&quot;&gt;still exists today for Drupal 8&lt;/a&gt; (and soon, Drupal 9).&lt;/p&gt;&lt;/div&gt;
      
&lt;span rel=&quot;schema:author&quot;&gt;&lt;span lang about=&quot;https://kevinquillen.com/user/1&quot; typeof=&quot;schema:Person&quot; property=&quot;schema:name&quot; datatype&gt;Kevin&lt;/span&gt;&lt;/span&gt;

&lt;span property=&quot;schema:dateCreated&quot; content=&quot;2020-02-03T19:22:24+00:00&quot;&gt;&lt;time datetime=&quot;2020-02-03T14:22:24-05:00&quot; title=&quot;Monday, February 3, 2020 - 14:22&quot;&gt;February 3rd, 2020&lt;/time&gt;
&lt;/span&gt;
</description><pubDate>Mon, 03 Feb 2020 19:22:24 GMT</pubDate><dc:creator>Kevin</dc:creator></item><item><title>Thoughtfully Updating Legacy Code </title><link>https://kevinquillen.com/thoughtfully-updating-legacy-code</link><guid isPermaLink="false">324 at https://kevinquillen.com</guid><description>
&lt;span property=&quot;schema:name&quot;&gt;Thoughtfully Updating Legacy Code &lt;/span&gt;

            &lt;div property=&quot;schema:text&quot; class=&quot;text-content clearfix field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Earlier this month, a round of updates were made to a client site and deployed to production. A critical bug came in saying that donut charts in visualizations were now showing the wrong numbers and that this was a top priority since it was visible to the public.&lt;/p&gt;&lt;/div&gt;
      
&lt;span rel=&quot;schema:author&quot;&gt;&lt;span lang about=&quot;https://kevinquillen.com/user/1&quot; typeof=&quot;schema:Person&quot; property=&quot;schema:name&quot; datatype&gt;Kevin&lt;/span&gt;&lt;/span&gt;

&lt;span property=&quot;schema:dateCreated&quot; content=&quot;2019-12-30T20:15:33+00:00&quot;&gt;&lt;time datetime=&quot;2019-12-30T15:15:33-05:00&quot; title=&quot;Monday, December 30, 2019 - 15:15&quot;&gt;December 30th, 2019&lt;/time&gt;
&lt;/span&gt;
</description><pubDate>Mon, 30 Dec 2019 20:15:33 GMT</pubDate><dc:creator>Kevin</dc:creator></item><item><title>First Steps with Erlang (Update)</title><link>https://kevinquillen.com/first-steps-erlang-update</link><guid isPermaLink="false">270 at https://kevinquillen.com</guid><description>
&lt;span property=&quot;schema:name&quot;&gt;First Steps with Erlang (Update)&lt;/span&gt;

            &lt;div property=&quot;schema:text&quot; class=&quot;text-content clearfix field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Shortly after publishing my last post about Erlang, I noticed a bug in the code which would not have happened if I wrote unit test(s) first. I did not do that simply because I just started learning, and didn’t want too many barriers up front to getting started (its hard to write tests when you are learning new syntax and methodology).&lt;/p&gt;

&lt;p&gt;Yet when I saw the bug, I couldn’t let that slide, as here again is another reinforcement of having tests. So I opened the project back up, pretended I have no awareness of the bug, and went from there.&lt;/p&gt;&lt;/div&gt;
      
&lt;span rel=&quot;schema:author&quot;&gt;&lt;span lang about=&quot;https://kevinquillen.com/user/1&quot; typeof=&quot;schema:Person&quot; property=&quot;schema:name&quot; datatype&gt;Kevin&lt;/span&gt;&lt;/span&gt;

&lt;span property=&quot;schema:dateCreated&quot; content=&quot;2018-11-02T12:00:00+00:00&quot;&gt;&lt;time datetime=&quot;2018-11-02T08:00:00-04:00&quot; title=&quot;Friday, November 2, 2018 - 08:00&quot;&gt;November 2nd, 2018&lt;/time&gt;
&lt;/span&gt;
</description><pubDate>Fri, 02 Nov 2018 12:00:00 GMT</pubDate><dc:creator>Kevin</dc:creator></item><item><title>Adding Tests to Legacy Drupal 7 Sites</title><link>https://kevinquillen.com/adding-tests-legacy-drupal-7-sites</link><guid isPermaLink="false">272 at https://kevinquillen.com</guid><description>
&lt;span property=&quot;schema:name&quot;&gt;Adding Tests to Legacy Drupal 7 Sites&lt;/span&gt;

            &lt;div property=&quot;schema:text&quot; class=&quot;text-content clearfix field field--name-body field--type-text-with-summary field--label-hidden field__item&quot;&gt;&lt;p&gt;Most developers at some point or another will inevitably need to add custom code to a site. In Drupal, this could be anything from extending core functionality, altering forms, or creating entirely new functionality.&lt;/p&gt;&lt;/div&gt;
      
&lt;span rel=&quot;schema:author&quot;&gt;&lt;span lang about=&quot;https://kevinquillen.com/user/1&quot; typeof=&quot;schema:Person&quot; property=&quot;schema:name&quot; datatype&gt;Kevin&lt;/span&gt;&lt;/span&gt;

&lt;span property=&quot;schema:dateCreated&quot; content=&quot;2018-10-29T12:00:00+00:00&quot;&gt;&lt;time datetime=&quot;2018-10-29T08:00:00-04:00&quot; title=&quot;Monday, October 29, 2018 - 08:00&quot;&gt;October 29th, 2018&lt;/time&gt;
&lt;/span&gt;
</description><pubDate>Mon, 29 Oct 2018 12:00:00 GMT</pubDate><dc:creator>Kevin</dc:creator></item></channel></rss>