Skip to Content

Changes for page Tips and Tricks

Last modified by chrisby on 2024/04/01 13:11
From version 1.3
edited by chrisby
on 2023/05/29 11:02
Change comment: There is no comment for this version
To version 1.4
edited by chrisby
on 2023/05/29 11:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
1 -* **Regularity:** Run tests regularly, ideally before every commit, for optimal quality assurance. In particular, run all relevant tests before pushing code or creating a pull/merge request. Continuous integration practices are helpful for enforcing testing of code uploaded by other developers.
1 +* **Regularity:** Run tests regularly, ideally before every commit, for optimal quality assurance. In particular, run all relevant tests before pushing code or creating a pull/merge request. 'Continuous integration' practices are helpful for enforcing testing of code uploaded by other developers.
2 2  * Use **functional programming** for data processing tasks because it is less prone to errors and side effects.
3 3  * It's common to create **test users and test data** to facilitate the testing process.
4 4  * Don't reinvent the wheel and **use existing test libraries**. There are proven solutions that minimize the effort of creating tests.