<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog on Adam Hepner</title>
    <link>https://blog.adamhepner.pl/</link>
    <description>Recent content in Blog on Adam Hepner</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <copyright>Copyright © 2018. All rights reserved.</copyright>
    <lastBuildDate>Mon, 23 Mar 2020 22:05:00 +0100</lastBuildDate>
    <atom:link href="https://blog.adamhepner.pl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>New Way to Search Testing Terms</title>
      <link>https://blog.adamhepner.pl/new-way-to-search-testing-terms/</link>
      <pubDate>Mon, 23 Mar 2020 22:05:00 +0100</pubDate>
      <guid>https://blog.adamhepner.pl/new-way-to-search-testing-terms/</guid>
      <description>&lt;figure&gt;&lt;img src=&#34;https://blog.adamhepner.pl/static/joshua-hoehne-1UDjq8s8cy0-unsplash.jpg&#34;&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;h1 id=&#34;the-why&#34;&gt;The why&lt;/h1&gt;&#xA;&lt;p&gt;I’ve been writing an &lt;a href=&#34;https://wonderproxy.com/blog/the-why-of-test-parametrization/&#34;&gt;article about test automation&lt;/a&gt;, and wanted to just explain some basic terms. I thought — well, &lt;a href=&#34;https://istqb.org&#34;&gt;ISTQB&lt;/a&gt; has a glossary on their page, I’ll link there. As it turns out, the glossary is horribly and unnecessarily complicated page to use, and it took me good couple minutes to locate a hidden link that leads to a specific term’s permalink.&lt;/p&gt;&#xA;&lt;h1 id=&#34;the-what&#34;&gt;The what&lt;/h1&gt;&#xA;&lt;p&gt;So I decided to try to do better than that, scraped their search results and published it on a statically generated site here: &lt;a href=&#34;https://istqb-glossary.page&#34;&gt;https://istqb-glossary.page&lt;/a&gt;. (disclaimer: at the moment I don’t claim any content on the page, all the terms point to &lt;a href=&#34;https://glossary.istqb.org&#34;&gt;ISTQB Glossary&lt;/a&gt; as their canonical links)&lt;/p&gt;</description>
    </item>
    <item>
      <title>Parameterizing Your Robot Framework Tests</title>
      <link>https://blog.adamhepner.pl/parameterizing-your-robot-framework-tests/</link>
      <pubDate>Wed, 11 Mar 2020 12:44:17 +0100</pubDate>
      <guid>https://blog.adamhepner.pl/parameterizing-your-robot-framework-tests/</guid>
      <description>&lt;p&gt;This is part 2 of 3 of the Getting Started with Robot Framework Series. You should &lt;a href=&#34;https://wonderproxy.com/blog/test-with-robot-and-selenium-part-1/&#34;&gt;read the first part&lt;/a&gt;, but also the &lt;a href=&#34;https://wonderproxy.com/blog/the-why-of-test-parametrization/&#34;&gt;companion article on why parameterizing test cases is important&lt;/a&gt; before continuing, as it contains the basis for work done in this article.&lt;/p&gt;&#xA;&lt;p&gt;If you&amp;rsquo;re too impatient to read the whole thing (it is quite lengthy!) or just want the juice, here&amp;rsquo;s &lt;a href=&#34;https://github.com/AdamHepner/wonderproxy-article-001-code/tree/code_for_article_2&#34;&gt;the code&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;goal-of-this-installment&#34;&gt;Goal of this installment&lt;/h2&gt;&#xA;&lt;p&gt;After you have worked through this part of the series, you will have&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Why of Test Parameterization</title>
      <link>https://blog.adamhepner.pl/the-why-of-test-parameterization/</link>
      <pubDate>Wed, 11 Mar 2020 12:18:07 +0100</pubDate>
      <guid>https://blog.adamhepner.pl/the-why-of-test-parameterization/</guid>
      <description>&lt;h1 id=&#34;the-why-of-test-parametrization&#34;&gt;The why of test parametrization&lt;/h1&gt;&#xA;&lt;p&gt;This article dives deeper into reasons and methods for parametrization in test automation. After you have completed it, you will have a deeper understanding of:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;What types of test parametrization techniques are available to you&lt;/li&gt;&#xA;&lt;li&gt;How proper test design works hand in hand with test parametrization&lt;/li&gt;&#xA;&lt;li&gt;How various approaches toward test design drive usage of different parametrization approaches&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The target audience of this article is people already performing test automation activities, but who have yet to feel confident in their approach to the subject. Consider this article a friendly chat over coffee about the relationship between your automated tests and their parameters.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hugo</title>
      <link>https://blog.adamhepner.pl/hugo/</link>
      <pubDate>Thu, 28 Nov 2019 12:19:18 +0100</pubDate>
      <guid>https://blog.adamhepner.pl/hugo/</guid>
      <description>&lt;p&gt;This is the first in a series of short posts where I will describe some of the tools that I use daily. There is no particular order to things, just a stream of thought if you will.&lt;/p&gt;&#xA;&lt;p&gt;So, &lt;a href=&#34;https://gohugo.io/&#34;&gt;Hugo&lt;/a&gt;. Static site generator, written in &lt;a href=&#34;https://golang.org/&#34;&gt;Go&lt;/a&gt; (one of my favourite programming languages), blazingly fast, easy to use, plays well with &lt;a href=&#34;https://www.netlify.com/&#34;&gt;Netlify&lt;/a&gt;, and &lt;a href=&#34;https://www.stackbit.com/&#34;&gt;Stackbit&lt;/a&gt;. What I love about it in particular, is that there&amp;rsquo;s a single executable provided, that allows you to easily manage your site. You can use it to &lt;a href=&#34;https://themes.gohugo.io/reveal-hugo/&#34;&gt;create reveal.js-style presentations&lt;/a&gt;, or even create a &lt;a href=&#34;https://forestry.io/blog/build-a-json-api-with-hugo/&#34;&gt;simple API&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Thanks to Great Expectations</title>
      <link>https://blog.adamhepner.pl/thanks-to-great-expectations/</link>
      <pubDate>Tue, 19 Nov 2019 09:56:27 +0100</pubDate>
      <guid>https://blog.adamhepner.pl/thanks-to-great-expectations/</guid>
      <description>&lt;p&gt;This is just a quick shout out to the &lt;a href=&#34;https://www.superconductivehealth.com/&#34;&gt;Great Expectations Team (Superconductive Health)&lt;/a&gt;. I happened to use their library to do some testing a few years ago, as I was part of the &amp;ldquo;&lt;a href=&#34;https://www.otto.de/jobs/technology/techblog/artikel/sind-wir-wirklich-nur-testmanagerinnen_2016-06-08.php&#34;&gt;Quality Specialists&lt;/a&gt;&amp;rdquo; team at &lt;a href=&#34;https://www.otto.de/&#34;&gt;Otto&lt;/a&gt;. Fun days, fun activity.&lt;/p&gt;&#xA;&lt;p&gt;Basically, I had a bunch of relatively big data files that needed explorative control for issues. I decided to use &lt;a href=&#34;https://jupyter.org/&#34;&gt;Jupyter Notebooks&lt;/a&gt;, &lt;a href=&#34;https://pandas.pydata.org/&#34;&gt;Pandas&lt;/a&gt; and &lt;a href=&#34;https://github.com/great-expectations/great_expectations&#34;&gt;Great Expectations&lt;/a&gt; for the explorative parts, and just replaced Jupyter Notebooks with &lt;a href=&#34;https://docs.pytest.org/en/latest/&#34;&gt;pytest&lt;/a&gt; for semi-automated verification when doing retests. I remeber work with Great Expectations to be very nice, and even recommended to keep working with it to my &lt;a href=&#34;https://www.linkedin.com/in/robin-van/&#34;&gt;replacement colleague&lt;/a&gt; (he&amp;rsquo;s an all-around great guy, very quick learner!) as I switched teams. During the work I submitted a &lt;a href=&#34;https://github.com/great-expectations/great_expectations/pull/324&#34;&gt;tiny pull request&lt;/a&gt;, since I noticed a formatting issue in their documentation.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fix File Encoding Using Go</title>
      <link>https://blog.adamhepner.pl/fix-file-encoding-using-go/</link>
      <pubDate>Fri, 01 Nov 2019 21:56:41 +0100</pubDate>
      <guid>https://blog.adamhepner.pl/fix-file-encoding-using-go/</guid>
      <description>&lt;p&gt;This is just a short entry on how to fix file encodings using Go. The reason for it is the following: I currently develop a small test automation augmentation for my customer, and it utilizes a third-party tool. For variuous reasons this third-party tool needs to touch the test data files, and in doing so, it completely garbles those files. After analysis, it turned out, that the files are read in as UTF-8, but &lt;strong&gt;interpreted&lt;/strong&gt; as Windows1252, yet written out again as UTF-8. This leads to very weird situation, where my &lt;em&gt;Umlauts&lt;/em&gt; are being converted into gibberisch (like: &lt;code&gt;ü&lt;/code&gt; -&amp;gt; &lt;code&gt;Ã¼&lt;/code&gt;). Fortunately, I also perform some additional postprocessing, and touch every line in each of those files under question, so I just needed to figure out how to fix the situation.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Running your first test with Robot Framework using docker</title>
      <link>https://blog.adamhepner.pl/running-your-first-test-with-robot-framework-using-docker/</link>
      <pubDate>Mon, 27 May 2019 08:54:35 +0200</pubDate>
      <guid>https://blog.adamhepner.pl/running-your-first-test-with-robot-framework-using-docker/</guid>
      <description>&lt;p&gt;Note: this article had originally been published on the [WonderProxy Blog](Running your first test with Robot Framework using docker) in March 2019.&lt;/p&gt;&#xA;&lt;h2 id=&#34;intro&#34;&gt;Intro&lt;/h2&gt;&#xA;&lt;p&gt;This is the first in a series of 3 articles. When you complete them all, you will have a functional and extensible, albeit basic, test automation solution for web applications. This solution will be prepared for inclusion in a &lt;a href=&#34;https://en.wikipedia.org/wiki/CI/CD&#34;&gt;CI/CD Pipeline&lt;/a&gt;, as well as for local execution.&lt;/p&gt;&#xA;&lt;p&gt;The complete solution will use &lt;a href=&#34;https://robotframework.org/#introduction&#34;&gt;Robot Framework&lt;/a&gt; as a generic test automation tool, and use &lt;a href=&#34;https://www.seleniumhq.org/docs/03_webdriver.jsp&#34;&gt;Selenium Webdriver&lt;/a&gt; to perform very basic browser automation. Two methods of parametrization of test runs will be introduced:&lt;/p&gt;</description>
    </item>
    <item>
      <title>On working with code examples</title>
      <link>https://blog.adamhepner.pl/20190122-on-working-with-code-examples/</link>
      <pubDate>Tue, 22 Jan 2019 14:40:26 +0100</pubDate>
      <guid>https://blog.adamhepner.pl/20190122-on-working-with-code-examples/</guid>
      <description>&lt;p&gt;I have been busy the whole January with a development task for one of my customers. We had settled on delivering the solution with Go, even though my experience with this programming language had been very limited. Decision had been based on of the quality aspects, that is - maintainability. My customer works daily with Go, and very sporadically with other languages. Had I delivered solution in Python, for example, it would be easy for me to deliver, but difficult for them to keep effectively working with the solution afterwards, should our relationship head south at any point in time.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Java Unit Test Organisation Proposition</title>
      <link>https://blog.adamhepner.pl/java-unit-test-organisation-proposition/</link>
      <pubDate>Wed, 17 Oct 2018 22:58:46 +0200</pubDate>
      <guid>https://blog.adamhepner.pl/java-unit-test-organisation-proposition/</guid>
      <description></description>
    </item>
    <item>
      <title>JUnit5 Evaluation</title>
      <link>https://blog.adamhepner.pl/junit5-evaluation/</link>
      <pubDate>Wed, 17 Oct 2018 22:58:26 +0200</pubDate>
      <guid>https://blog.adamhepner.pl/junit5-evaluation/</guid>
      <description></description>
    </item>
    <item>
      <title>Starting a New Website with Hugo</title>
      <link>https://blog.adamhepner.pl/starting-a-new-website-with-hugo/</link>
      <pubDate>Wed, 17 Oct 2018 22:57:31 +0200</pubDate>
      <guid>https://blog.adamhepner.pl/starting-a-new-website-with-hugo/</guid>
      <description></description>
    </item>
    <item>
      <title>Hello World</title>
      <link>https://blog.adamhepner.pl/hello-world/</link>
      <pubDate>Wed, 17 Oct 2018 22:03:43 +0200</pubDate>
      <guid>https://blog.adamhepner.pl/hello-world/</guid>
      <description>&lt;p&gt;So, hello everyone. My name is &lt;a href=&#34;https://adamhepner.pl&#34;&gt;Adam Hepner&lt;/a&gt;, and I&amp;rsquo;ve long been thinking about getting some testing-related publishing done. Usually it&amp;rsquo;s just life that gets in the way, but I hope that with a little bit of deliberate practice I might get this thing going.&lt;/p&gt;&#xA;&lt;p&gt;Some things that this blog will be about:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;case studies and lessons learned in software testing&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://www.ministryoftesting.com&#34;&gt;Ministry of Testing&lt;/a&gt; &lt;a href=&#34;https://club.ministryoftesting.com/c/bloggers-club&#34;&gt;bloggers&amp;rsquo; club&lt;/a&gt; challenges&lt;/li&gt;&#xA;&lt;li&gt;coding and testing &lt;a href=&#34;https://jamesclear.com/deliberate-practice-theory&#34;&gt;deliberate practice&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;maybe a bit about my parenting&lt;/li&gt;&#xA;&lt;li&gt;maybe something about my hobbies&lt;/li&gt;&#xA;&lt;li&gt;probably other things as well.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;So, yeah, that&amp;rsquo;s it for now. Let&amp;rsquo;s see how long this one lives.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
