<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Testing on Rihards Steinbergs</title><link>https://rihards.com/blog/testing/</link><description>Recent content in Testing on Rihards Steinbergs</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Rihards Steinbergs</copyright><lastBuildDate>Sun, 05 May 2019 16:07:03 +0000</lastBuildDate><atom:link href="https://rihards.com/blog/testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Acquia Dev Desktop access from local network</title><link>https://rihards.com/2019/acquia-dev-desktop-local-network/</link><pubDate>Sun, 05 May 2019 16:07:03 +0000</pubDate><guid>https://rihards.com/2019/acquia-dev-desktop-local-network/</guid><description>&lt;p&gt;While typically I prefer something like &lt;a href="https://www.drupalvm.com/" rel="external noopener nofollow" target="_blank"&gt;Drupal VM&lt;/a&gt; over &lt;a href="https://www.acquia.com/drupal/acquia-dev-desktop" rel="external noopener nofollow" target="_blank"&gt;Acquia Dev Desktop&lt;/a&gt; (and that&amp;rsquo;s a different topic) I&amp;rsquo;ve found myself using Dev Desktop more recently, due to how easy, reliably, and quickly it can spin up new copies of Drupal.&lt;/p&gt;&#10;&lt;p&gt;For a project I just recently had to test and fix some Internet Explorer issues. Usually I&amp;rsquo;d use something like BrowserStack, but it happened to be so that I was working from home where I have access to my PC, so I thought why not use that. It would be native testing and overall a smoother experience than BrowserStack (debugging IE11 on BrowserStack can get very frustrating).&lt;/p&gt;</description></item><item><title>Bitbucket Pipelines, PHPUnit, PHPCS and CodeCeption</title><link>https://rihards.com/2017/bitbucket-pipelines-phpunit-codeception/</link><pubDate>Wed, 22 Mar 2017 17:01:07 +0000</pubDate><guid>https://rihards.com/2017/bitbucket-pipelines-phpunit-codeception/</guid><description>&lt;h3 id="background-information"&gt;Background information&lt;/h3&gt;&#10;&lt;p&gt;For a while now I&amp;rsquo;ve been thinking about starting a new project, and as with most such cases I&amp;rsquo;ve been thinking that I need to do things better and more proper this time around.&lt;/p&gt;&#10;&lt;p&gt;One of those things has always been the automated testing parts of the project that have fallen behind or lacking in many ways.&lt;/p&gt;&#10;&lt;p&gt;So I set a small private repository on Bitbucket to see what my options are, what I could work with, etc. and started looking into the various tools like &lt;a href="https://jenkins.io/" rel="external noopener nofollow" target="_blank"&gt;Jenkins&lt;/a&gt;, &lt;a href="https://travis-ci.org/" rel="external noopener nofollow" target="_blank"&gt;Travis&lt;/a&gt;, and &lt;a href="https://circleci.com/" rel="external noopener nofollow" target="_blank"&gt;CircleCI&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>