Skip to Content

Changes for page Tips and Tricks

Last modified by chrisby on 2024/04/01 13:11
From version 1.30
edited by chrisby
on 2024/04/01 12:54
Change comment: There is no comment for this version
To version 1.31
edited by chrisby
on 2024/04/01 12:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,6 @@
1 1  Here are a few general guideline that help to write better test code as well as influencing the design of the production code.
2 2  
3 -* **Frequent Execution**: Run tests frequently, 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.
3 +* **Frequent Execution**: Run tests frequently, 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>>doc:Software Engineering.Agile.Extreme Programming.Continuous Integration.WebHome]] practices are helpful for enforcing testing of code uploaded by other developers.
4 4  * Use **functional programming** for data processing tasks because it is less prone to errors and side effects.
5 5  * It's common to create **test users and test data** to facilitate the testing process.
6 6  * Don't reinvent the wheel and **use existing test libraries**. There are proven solutions that minimize the effort of creating tests.