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=11208-b50f216697631272f92b027a84b03cfb761b93d4,erp5=49926-7fb53e8fdeaf7ae82b6b20013b272a9713b9670b 2019/02/14 10:57:2.735921 UTC ERP5-MASTER 6027 9 0 195 FAIL Completed
slapos.cookbook=11208-b50f216697631272f92b027a84b03cfb761b93d4,erp5=49919-74ee68f5cbababa8d61c5d7b9ee735a2ff245648 2019/02/14 00:10:2.952860 UTC ERP5-MASTER 6023 9 0 195 FAIL Completed
slapos.cookbook=11208-b50f216697631272f92b027a84b03cfb761b93d4,erp5=49915-f75b7c3be1504bf682f4ab8427b2bff8ccabe7c3 2019/02/13 15:40:54.225955 UTC ERP5-MASTER 6023 11 0 196 FAIL Completed
slapos.cookbook=11208-b50f216697631272f92b027a84b03cfb761b93d4,erp5=49914-20fcbf6e9ba0e23f54d477f383469f2b770081c7 2019/02/13 04:53:15.158159 UTC ERP5-MASTER 6023 9 0 196 FAIL Completed
slapos.cookbook=11208-b50f216697631272f92b027a84b03cfb761b93d4,erp5=49913-e84d2b5191c2b71c90700395840917da0cdebe7d 2019/02/12 05:52:55.872284 UTC ERP5-MASTER 6023 11 0 195 FAIL Completed
slapos.cookbook=11208-b50f216697631272f92b027a84b03cfb761b93d4,erp5=49912-c0cd85248e2e037f6073ff883d475fad5f1d6cdc 2019/02/11 17:12:11.549339 UTC ERP5-MASTER 5994 11 0 197 FAIL Completed
slapos.cookbook=11208-b50f216697631272f92b027a84b03cfb761b93d4,erp5=49911-8978bbc76ad27873af4ea825a3dd4bca5838740d 2019/02/11 13:19:59.126918 UTC ERP5-MASTER 5994 10 0 196 FAIL Completed
slapos.cookbook=11208-b50f216697631272f92b027a84b03cfb761b93d4,erp5=49909-7f0614410b6089d78d2e1a4cbf68a5cce174b7a3 2019/02/10 13:30:30.956475 UTC ERP5-MASTER 5994 9 0 196 FAIL Completed
slapos.cookbook=11206-1707af404b007993060f9d7279b924d6482ed535,erp5=49909-7f0614410b6089d78d2e1a4cbf68a5cce174b7a3 2019/02/08 16:46:46.378445 UTC ERP5-MASTER 5994 11 27 196 FAIL Completed
slapos.cookbook=11203-ee87b773b720902a96245e3e5c5acc59d9296f78,erp5=49909-7f0614410b6089d78d2e1a4cbf68a5cce174b7a3 2019/02/08 08:59:16.596203 UTC ERP5-MASTER 5994 10 0 196 FAIL Completed
slapos.cookbook=11202-b5b794834bbd28d257a0ca74df94e137a4ba1f5d,erp5=49909-7f0614410b6089d78d2e1a4cbf68a5cce174b7a3 2019/02/07 23:52:10.065292 UTC ERP5-MASTER 5994 11 0 196 FAIL Completed
slapos.cookbook=11200-de75a7651fc9bb1e306e59da4c96870ed699507f,erp5=49909-7f0614410b6089d78d2e1a4cbf68a5cce174b7a3 2019/02/07 16:08:31.079604 UTC ERP5-MASTER 5994 9 0 195 FAIL Completed
slapos.cookbook=11200-de75a7651fc9bb1e306e59da4c96870ed699507f,erp5=49907-b418885fc2090d45a0e9b38f2cbc529cc5030d62 2019/02/06 16:06:55.315344 UTC ERP5-MASTER 5994 11 4 196 FAIL Completed
slapos.cookbook=11199-780f2de39d26c350dcc1fb933666fe7df04aec57,erp5=49907-b418885fc2090d45a0e9b38f2cbc529cc5030d62 2019/02/05 19:21:43.798882 UTC ERP5-MASTER 5994 9 0 195 FAIL Completed
slapos.cookbook=11194-358a5f482bc007cfe028dbacad5758d91078dc55,erp5=49907-b418885fc2090d45a0e9b38f2cbc529cc5030d62 2019/02/05 11:27:57.348469 UTC ERP5-MASTER 5994 10 0 196 FAIL Completed