<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CamiTK Developer Guide on CamiTK</title>
    <link>https://camitk.timc.fr/docs/camitkdeveloper/</link>
    <description>Recent content in CamiTK Developer Guide on CamiTK</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://camitk.timc.fr/docs/camitkdeveloper/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CamiTK Programming Guidelines</title>
      <link>https://camitk.timc.fr/docs/camitkdeveloper/camitk-coding-conventions/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://camitk.timc.fr/docs/camitkdeveloper/camitk-coding-conventions/</guid>
      <description>&lt;p&gt;The programming guidelines are &lt;a href=&#34;https://camitk.timc.fr/guidelines/CamiTK%20Programming%20Guidelines%20v1.pdf&#34;&gt;available in PDF&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;If you intend to develop long term and reusable CEP or a CEP that you would like us to include in the CamiTK Community Edition, please read and conform to these guidelines.&lt;/p&gt;</description>
    </item>
    <item>
      <title>CamiTK testing framework technical overview</title>
      <link>https://camitk.timc.fr/docs/camitkdeveloper/testing-framework/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://camitk.timc.fr/docs/camitkdeveloper/testing-framework/</guid>
      <description>&lt;!--&#xA;[![By CamiTK Team](https://img.shields.io/badge/by-CamiTK%20Team-green.svg?longCache=true&amp;style=plastic)](http://camitk.imag.fr/)&#xA;--&gt;&#xA;&lt;p&gt;CamiTK provides some tools to test your code at different granularity levels. In this wiki page you will find information about our testing process, what we test and how you can use our already defined tests.&lt;/p&gt;&#xA;&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Testing a software code is always a good practice to make sure that the code behave accordingly to the specification, to detect bugs and errors and regression. It can also be very helpful to check that code integration is operational.&#xA;Several types of tests exist depending on the granularity level of the tests. There are classically three categories of tests:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
