TestBrain divides your code into separate functional areas. This helps with the initial manual assignment of test groups to code areas, and with creating the RiskMap which shows which areas of the code have been touched by each commit.
In most cases, the functional code areas will match the folder structure of the source code. However, TestBrain gives you the flexibility to assign your files to functional areas in whatever way makes the most sense to your development and test teams. You may want to subdivide a folder into multiple functional areas, or combine multiple folders into a single functional area. You can assign code files to any functional area regardless of which source code file it is in.
To make TestBrain as useful to your team as possible, we recommend consulting with the development team to determine which source code files belong to what functionality. You can also create your functional areas to match the grouping of your tests and assigning the files and folders of the code to those functional areas.
Most users will set up the functional areas based on the source code folder structure, then make any necessary adjustments. However, you can create the functional areas individually and assign the relevant source code folder and files.
When a file name is changed or the file is moved to a different folder, it remains in the assigned area. When new files are added to a folder that has been assigned to a functional area, the new files are automatically added to the area
Once the functional code areas have been set up, use the Dependent Areas table to note any dependencies between the code areas.
To create functional areas there are two options:
- Creating each area individually (recommended) -https://appsurify.com/knowledge-base/create-functional-code-areas-individually/
- Creating via the folder structure – https://appsurify.com/knowledge-base/createfunctionalareasfolders/