<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Developer on ScipioERP</title><link>https://www.scipioerp.com/community/developer/</link><description>Recent content in Developer on ScipioERP</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.scipioerp.com/community/developer/index.xml" rel="self" type="application/rss+xml"/><item><title>Services</title><link>https://www.scipioerp.com/community/developer/services/</link><pubDate>Mon, 16 May 2016 00:00:00 +0000</pubDate><guid>https://www.scipioerp.com/community/developer/services/</guid><description>&lt;p&gt;Roughly speaking, a service is a piece of code (Java, Simple-method, Groovy, etc.) that can be run inside of the SCIPIO framework. SCIPIO services can also be “exported” as web services (SOAP, REST, XML-RPC, etc.) using the export=”true” option (attribute of the service element in it’s definition). Services can be chained (i.e. call each others), triggered by ECAs (&lt;a href="https://www.scipioerp.com/community/developer/events-actions/"&gt;Event Condition Action&lt;/a&gt;
) and run asynchronously which gives them a lot of power and allow’s them to be implemented instantly. They always carry the session data in a context variable and can be rolled back if they threw an error (services are transactional with timeout).&lt;/p&gt;</description></item><item><title>Testing</title><link>https://www.scipioerp.com/community/developer/testing/</link><pubDate>Wed, 16 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.scipioerp.com/community/developer/testing/</guid><description>&lt;p&gt;Scipio ERP runs its tests inside a running framework, not outside it. The test
runner boots the container stack, so a test case reaches the real delegator and
the real dispatcher. A service test therefore proves the service, its entity
model and its ECA rules together.&lt;/p&gt;
&lt;h2 id="run-the-tests"&gt;Run the tests&lt;a class="heading-anchor" href="#run-the-tests" aria-label="Link to this section"&gt;#&lt;/a&gt;
&lt;/h2&gt;
&lt;div class="codeblock"&gt;
 &lt;div class="codeblock__bar"&gt;
 &lt;span class="window__dot window__dot--live"&gt;&lt;/span&gt;
 &lt;span class="window__dot"&gt;&lt;/span&gt;
 &lt;span class="window__dot"&gt;&lt;/span&gt;
 &lt;span class="codeblock__lang"&gt;text&lt;/span&gt;
 &lt;/div&gt;
 &lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;gradlew.bat runTest&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;p&gt;That builds every subproject, boots the test container and runs every suite of
every component. Three properties narrow it:&lt;/p&gt;</description></item></channel></rss>