<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>testthat on Maëlle Salmon&#39;s personal website</title>
    <link>https://masalmon.eu/tags/testthat/</link>
    <description>Recent content in testthat on Maëlle Salmon&#39;s personal website</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>Licence: &lt;a href=&#34;https://creativecommons.org/licenses/by-sa/2.0/&#34;&gt;CC BY-SA&lt;/a&gt;</copyright>
    <lastBuildDate>Tue, 24 Sep 2024 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://masalmon.eu/tags/testthat/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Cover and modify, some tips for R package development</title>
      <link>https://masalmon.eu/2024/09/24/cover-modify-r-packages/</link>
      <pubDate>Tue, 24 Sep 2024 00:00:00 +0000</pubDate>
      
      <guid>https://masalmon.eu/2024/09/24/cover-modify-r-packages/</guid>
      <description>I&amp;rsquo;ve recently been dealing with legacy code refactoring both in theory and in practice: while I&amp;rsquo;m continuing some work on the igraph R package, I&amp;rsquo;ve started reading Working Effectively with Legacy Code by Michael Feathers, that had been in my to-read pile for months. In this post, I&amp;rsquo;ll summarize some ideas from both the book and my work.
&amp;ldquo;Cover and modify&amp;rdquo; with &amp;ldquo;characterization tests&amp;rdquo; When you start modifying your rusty code, how do you ensure you do not break existing and important behaviour inadvertently?</description>
    </item>
    
  </channel>
</rss>