<?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 Janik von Rotz</title>
    <link>https://janikvonrotz.ch/tags/testing/</link>
    <description>Recent content in Testing on Janik von Rotz</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 05 Dec 2019 10:16:19 +0100</lastBuildDate>
    <atom:link href="https://janikvonrotz.ch/tags/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Apollo Graphql integration testing in practice</title>
      <link>https://janikvonrotz.ch/2019/12/05/apollo-graphql-integration-testing-in-practice/</link>
      <pubDate>Thu, 05 Dec 2019 10:16:19 +0100</pubDate>
      <guid>https://janikvonrotz.ch/2019/12/05/apollo-graphql-integration-testing-in-practice/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://www.apollographql.com/docs&#34;&gt;Apollo Graphql documention&lt;/a&gt; offers a pretty comprehensive guide on how to &lt;a href=&#34;https://www.apollographql.com/docs/apollo-server/testing/testing&#34;&gt;test your Graphql API&lt;/a&gt;. But sure its different once you implement tests for your non generic project. That is why I wrote this post. First I would like to introduce you to integration tests and how they are different from the other testing levels. And then I&amp;rsquo;ll give you a hands on experience for writing integration tests for Apollo Graphql with &lt;a href=&#34;https://github.com/avajs/ava&#34;&gt;Ava&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Autodeploy to Github Pages with Travis CI</title>
      <link>https://janikvonrotz.ch/2015/11/11/autodeploy-to-github-pages-with-travisci/</link>
      <pubDate>Wed, 11 Nov 2015 09:37:05 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2015/11/11/autodeploy-to-github-pages-with-travisci/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://pages.github.com/&#34;&gt;Github pages&lt;/a&gt; are a common way to create a website for your open-source project.&#xA;Github provides a website generator tool which simply reads the README file from your repository.&#xA;The big disadvantage is that there&amp;rsquo;s no auto deployment for your this kind of website. You always have to run the generator manually.&#xA;To solve this problem we need a third-party computing engine that automatically updates our page. This is the perfect job for &lt;a href=&#34;https://travis-ci.org&#34;&gt;Travis CI&lt;/a&gt;.&#xA;Travis CI is a Github integrated continuous testing platform that runs tests for different development frameworks. It triggers a test whenever you make a commit on your Travis registered repository. We will use Travis to update our page whenever we make a commit to our repository.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Thank you internet for: Peek by UserTesting</title>
      <link>https://janikvonrotz.ch/2014/05/15/thank-your-internet-for-peek-by-usertesting/</link>
      <pubDate>Thu, 15 May 2014 12:44:00 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2014/05/15/thank-your-internet-for-peek-by-usertesting/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;http://peek.usertesting.com/&#34;&gt;Peek&lt;/a&gt; is a free service offered by &lt;a href=&#34;http://www.usertesting.com/&#34;&gt;User Testing&lt;/a&gt; where you can get real people to test your websites usability.&lt;/p&gt;&#xA;&lt;p&gt;I have to admit, first I didn&amp;rsquo;t really believe that there will be real person visiting my site and give my a feedback. But within in one hour I have been suprised.&lt;/p&gt;&#xA;&lt;p&gt;Here&amp;rsquo;s the video done by a random guy from the internet:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
