Most Powerful Open Source ERP

ERP5 Unit Tests

Introduction

ERP5 is used for many critical applications. Our customers relies on it to run their every day business, and they can not accept having regularly bugs coming again and again. Every software issue could have important consequences, especially if you think about banking, areospace applications and many others. Therefore Nexedi consider the quality as one of it's top priorities and decided to use automated testing since the early age of ERP5.

Unit / Functional Test

While the code of ERP5 is evolving, more and more unit and functional tests are added. When issues are reported, we write the test and fix the problem. Like this we make sure that the same issue is not going to happens again. Also, when new features are done, tests are added to make sure we will provide well working experience. We have both unit test and functional tests. Unit test are used to test isolated software component, while functional tests are used to verify scenarios more closed to user experience.

Development policy

We tried for years to keep the quantity of failures as low as possible. While the size of ERP5 was growing, it started to be more and more time consuming to track regressions. In particular, it's quite common that a change in some part of the code generate a regression in another place that seems unrelated without detailed analysis. And then it happened that we had several errors, and it was difficult to see new ones. Therefore, after our switch to git, we introduced the rule "contributions must not introduce ANY regression". So we started by fixing test failures, we checked all random issues, and we started to reject any code introducing failures. The idea is simply to check all unit test before contributing changes to the central place. This can easily be done thanks to our Testing Infrastructure. Thanks to this rule, about any revision of ERP5 could be considered as stable. This is really a great success. With a quantity of test growing, we have nearly 0 errors/failures all the time.

Testing Infracture

We are using what we call "ERP5 Test Nodes". It's some processes installed on many different machines thanks to SlapOS cloud tools. We define several list of tests to run, and ERP5 test nodes will look regularly to several git repositories to detect new commit, then they launch software constructions and finally tests are automatically run. Theses days we are using about 60 CPU cores to run tests for our various projects and for different versions.

ERP5 Test Results

You can find below the result of automatic test of ERP5 code. Hopefully you are able to see many test results at 0 errors/failures for several thousands of tests. Since we are humans and not perfect, It might happens that a change introduce a regression. But in this case, you could be sure that we will quickly look and solve it.

1 - 15 of sample of 1000 records
Revision Launch Date Title All Tests Failures Errors Skips Result Status
slapos.cookbook=11500-1dc67550ff981d35f93e7bd0efb797a13f1f6e46,erp5=50212-dacf12bb6ff84913aaec0090491f2b7e60b35a0f 2019/06/26 11:36:41.785560 UTC ERP5-MASTER 6042 13 0 200 FAIL Completed
slapos.cookbook=11499-9bf0016ebb2be1adcc3add7e4278ec795ce9d148,erp5=50212-dacf12bb6ff84913aaec0090491f2b7e60b35a0f 2019/06/26 09:35:45.694057 UTC ERP5-MASTER 6042 11 0 200 FAIL Completed
slapos.cookbook=11497-424717f6f69220e36602b8efd7e16b7c83c17b0c,erp5=50211-3fa50c21906ed5100e05db077edb5936c162608b 2019/06/25 12:49:22.175047 UTC ERP5-MASTER 6042 11 0 200 FAIL Completed
slapos.cookbook=11497-424717f6f69220e36602b8efd7e16b7c83c17b0c,erp5=50210-d0310869f0107a9c885747f9b2d81b417a0b2854 2019/06/25 00:11:34.283734 UTC ERP5-MASTER 6042 11 1 200 FAIL Completed
slapos.cookbook=11491-0710f1ea87975b2fbec77576041f409db3b184a1,erp5=50201-8a6c439447a16f7912f43dc417163b2710e1874b 2019/06/24 13:56:49.765194 UTC ERP5-MASTER 6040 12 1 200 FAIL Completed
slapos.cookbook=11709-33f4d533635dce059eb7521a55c42768c4bdef1f,erp5=50198-bf00e8c35532ecbba845f9c0b229ca6073206c6f 2019/06/24 07:53:41.527448 UTC ERP5-MASTER 6040 10 0 200 FAIL Completed
slapos.cookbook=11489-3ea8739c29ad9741cd4cfe58cacb10d0cc3603bd,erp5=50187-80994259537cc30d255d9230aabaf47dce621bf8 2019/06/20 17:16:16.546716 UTC ERP5-MASTER 6038 10 0 200 FAIL Completed
slapos.cookbook=11488-2a6967d6a90754e07a871c5694185f394ec03688,erp5=50187-80994259537cc30d255d9230aabaf47dce621bf8 2019/06/20 09:04:14.908582 UTC ERP5-MASTER 6037 11 1 200 FAIL Completed
slapos.cookbook=11485-712f5c6069d924b0e28acb1f170bd796d7da1ffa,erp5=50187-80994259537cc30d255d9230aabaf47dce621bf8 2019/06/20 07:27:18.010350 UTC ERP5-MASTER 6038 27 0 200 FAIL Completed
slapos.cookbook=11484-e703b43f83f1c4f6e02d19eb13737557ad9d6892,erp5=50187-80994259537cc30d255d9230aabaf47dce621bf8 2019/06/20 03:52:19.145872 UTC ERP5-MASTER 6038 10 0 200 FAIL Completed
slapos.cookbook=11484-e703b43f83f1c4f6e02d19eb13737557ad9d6892,erp5=50186-ea32ff153d7c20b3a5df697a3f7d55df68a7bed4 2019/06/19 18:41:32.074190 UTC ERP5-MASTER 6038 10 0 200 FAIL Completed
slapos.cookbook=11483-b96cdf9cd8f1cf9d859c1a11594c267218d2ff43,erp5=50186-ea32ff153d7c20b3a5df697a3f7d55df68a7bed4 2019/06/19 17:21:6.482828 UTC ERP5-MASTER 6038 11 0 200 FAIL Completed
slapos.cookbook=11481-685c2aa9f9a5d4d197265c0acd295d88e6135eea,erp5=50186-ea32ff153d7c20b3a5df697a3f7d55df68a7bed4 2019/06/19 10:49:52.156037 UTC ERP5-MASTER 6038 11 0 200 FAIL Completed
slapos.cookbook=11479-6c4e40511bfcbee1e9621e452e0ac69b2946a5c0,erp5=50186-ea32ff153d7c20b3a5df697a3f7d55df68a7bed4 2019/06/18 15:25:41.718963 UTC ERP5-MASTER 6038 10 0 200 FAIL Completed
slapos.cookbook=11478-d431f234ec2250c2a62ffc18ddd54a4712fbf9bf,erp5=50186-ea32ff153d7c20b3a5df697a3f7d55df68a7bed4 2019/06/18 07:09:28.406292 UTC ERP5-MASTER 6038 11 0 200 FAIL Completed