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=11080-f7a525ea031929c0d1c41442342700ddbd7a03f1,erp5=49829-6e0cad4861c9770245ffed3c789f92839d9fdfe8 2018/12/07 05:57:58.720110 UTC ERP5-MASTER 5981 6 0 203 FAIL Completed
slapos.cookbook=11080-f7a525ea031929c0d1c41442342700ddbd7a03f1,erp5=49816-e6573300606a60dd701a9c304f8ca4eab77b59d5 2018/12/06 20:17:38.372622 UTC ERP5-MASTER 5980 2 1 202 FAIL Completed
slapos.cookbook=11077-9c0c1e8076842750abccc0588f81f0a33228248c,erp5=49816-e6573300606a60dd701a9c304f8ca4eab77b59d5 2018/12/06 12:51:19.786381 UTC ERP5-MASTER 5980 4 0 203 FAIL Completed
slapos.cookbook=11076-b69079da315f50750a1886683e004cfeae36b1f6,erp5=49816-e6573300606a60dd701a9c304f8ca4eab77b59d5 2018/12/06 04:16:7.363815 UTC ERP5-MASTER 5980 7 0 202 FAIL Completed
slapos.cookbook=11075-e4e5824f72ae2b52b7950858f11373792c0730bf,erp5=49816-e6573300606a60dd701a9c304f8ca4eab77b59d5 2018/12/05 19:05:28.313369 UTC ERP5-MASTER 5980 4 0 202 FAIL Completed
slapos.cookbook=11069-17066d8bd4b7fe485949c1301cd66593fda19468,erp5=49814-a185fe60e39a1cf0f3513765f4936d05e205e9b0 2018/12/05 09:20:8.847929 UTC ERP5-MASTER 5980 3 0 203 FAIL Completed
slapos.cookbook=11069-17066d8bd4b7fe485949c1301cd66593fda19468,erp5=49812-cde69e3d3e8a51b41bab61c8547b23ac4ea4ef7e 2018/12/04 20:00:5.924087 UTC ERP5-MASTER 5980 3 0 202 FAIL Completed
slapos.cookbook=11067-0e28c90ee2831737c6036ca24b292643fca4aff4,erp5=49812-cde69e3d3e8a51b41bab61c8547b23ac4ea4ef7e 2018/12/04 10:47:32.294984 UTC ERP5-MASTER 5980 3 0 201 FAIL Completed
slapos.cookbook=11067-0e28c90ee2831737c6036ca24b292643fca4aff4,erp5=49804-ee05c9c4bf166e740699794f8f31e551a2b1e974 2018/12/04 02:47:58.218023 UTC ERP5-MASTER 5980 3 0 201 FAIL Completed
slapos.cookbook=11067-0e28c90ee2831737c6036ca24b292643fca4aff4,erp5=49783-a59ce6b39f340437fbef386980f96aab4b348879 2018/12/03 21:18:16.189834 UTC ERP5-MASTER 6004 8 0 201 FAIL Completed
slapos.cookbook=11059-8c792da1edc894a1ce0c5d6df39ab57a134e4cf1,erp5=49783-a59ce6b39f340437fbef386980f96aab4b348879 2018/12/03 13:11:49.868570 UTC ERP5-MASTER 6004 6 1 202 FAIL Completed
slapos.cookbook=11055-ee1ac16c1ec45100b38411ea2655874419d4893b,erp5=49783-a59ce6b39f340437fbef386980f96aab4b348879 2018/12/03 03:42:9.671610 UTC ERP5-MASTER 6004 23 0 201 FAIL Completed
slapos.cookbook=11054-399d5192b9e5eb3ea6d5f9319913ec9699bac4be,erp5=49783-a59ce6b39f340437fbef386980f96aab4b348879 2018/12/01 00:18:4.778156 UTC ERP5-MASTER 6004 3 1 202 FAIL Completed
slapos.cookbook=11038-59e5ce886bcbdbb6576e5e1ccb0f01460920a39f,erp5=49779-c94c988f6644e6ab91d232e65e0a35cda0eed460 2018/11/29 10:38:6.120757 UTC ERP5-MASTER 6004 5 0 201 FAIL Completed
slapos.cookbook=11038-59e5ce886bcbdbb6576e5e1ccb0f01460920a39f,erp5=49778-db3f3acf896a6bc11997059035a183d128720e04 2018/11/27 16:26:2.675704 UTC ERP5-MASTER 6004 3 0 201 FAIL Completed