MalDec-EDR is a Unix system solution designed to detect anomalies and malware attacks using kernel-level mechanisms. For more information, please refer to the Documentation.
The standard practice is to have the latest stable production version available for customers in the main and tagged branch. The test branch serves as a mirror of the development branch, subjecting it to a battery of tests and quality assurance (QA) processes. Meanwhile, the development (dev) branch is dedicated to ongoing project development, enhancements, and adjustments.
+-----------+
| feature1 |
+-----------+
|
+-----------+
| feature3 |
+-----------+
|
+-----------+
| feature2 |
+-----------+
|
+-----------+ +-----------+ +-----------+
| dev | ---> | test | ---> | main |
+-----------+ +-----------+ +-----------+
|
+--------------------------+
| | |
+-----+ +-----+ +-----+
|1.0.0| |2.0.0| | ... |
+-----+ +-----+ +-----+
You need to test all components of MalDec-EDR, if possible detail the task of the components you tested, which paths you took and how we can perform the tests, if possible create a script of how the tests for your task work, more than 1 developer can carry out the review.
Every modification to the code, no matter how small, should ideally be accompanied by thorough unit tests. This practice is crucial for detecting potential errors introduced by other developers. The presence of unit tests serves as a safeguard, ensuring that any unintended changes are promptly identified and addressed.
Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.