Module Management

AngusTester Module Management provides hierarchical organization capabilities, enabling structured management of requirements, tasks, and test cases through a module tree, thereby improving feature maintainability and team collaboration efficiency.

Module Tree Structure

Core Module Operations

1. Add Module

Description: Create a new functional module as a root node
Steps:

1. Navigate to Project → Project List → Edit
2. Switch to Software Template in the edit page
3. Click the "Add Module" button
4. Enter a unique module name (≤50 characters)
5. Click "Confirm" to complete creation

⚠️ Naming Conventions:

• Avoid special characters
• Name should reflect functional domain

Quota Rules

Module quantity limits by version:

Version Type	Default Quota	Expansion Method
Cloud Edition	5000	Submit Ticket Request
On-Premise	5000	Contact system administrator for license adjustment

Tip: View real-time quota under Module Count on the Resource Quota page.

2. Add Submodule

Description: Create child nodes under existing modules
Steps:

1. Right-click the target parent module
2. Select "New Submodule"
3. Enter submodule name
4. Click "Confirm" to save

Hierarchy Rules:

• Maximum 5-level nesting
• Unique names required at same level

3. Edit Module

Description: Update module name information
Steps:

1. Locate target module
2. Right-click "Edit"
3. Modify module name
4. Click "Save"

⚠️ Impact Scope:
Automatically updates display names of all associated resources

4. View Modules

Description: Browse complete module tree structure
Steps:

1. Go to Project Details → Modules Tab
2. View tree structure:
   • Expand/collapse levels
   • View resource counts per module

5. Adjust Module Order

Description: Optimize module display priority
Options:

• Move Up: Increase display priority
• Move Down: Decrease display priority

Steps:

1. Select target module
2. Right-click "Move Up" or "Move Down"
3. System automatically refreshes position

⚠️ Level Restriction:
Only supports order adjustment within same level

6. Delete Module

Description: Remove unnecessary module nodes
Steps:

1. Right-click target module → "Delete"
2. Confirm deletion (secondary verification)
3. System removes module node

⚠️ Data Safety:

• Only deletes module node
• Associated tasks/cases remain unaffected
• Admins can trace via operation logs

Module Application Scenarios

1. Organize Test Tasks

Description: Group tasks by module
Steps:

1. When creating/editing tasks
2. Select target module in "Module" field
3. Switch to "Group by Module" view

2. Manage Test Cases

Description: Structurally organize test cases
Best Practices:

• Top-level: Business domain (e.g., User Management)
• Submodules: Features (e.g., Login/Registration)
• Leaf nodes: Specific functions (e.g., Forgot Password)

Path:

1. Specify module when creating cases
2. Filter cases using module tree
3. Export module-specific case sets

Module Field Information

Parameter	Field Name	Type	Required	Length Limit	Description
ID	id	long	Conditional	/	Unique identifier; Auto-generated; Mandatory for modifications
Project ID	projectId	long	Yes	/	Parent project identifier
Parent Module ID	pid	long	No	/	Parent module ID -1 indicates top-level module
Sort Value	sequence	int	Yes	/	Sorting weight (lower values appear first)
Module Names	names	list	Yes	/	Name collection Minimum one name required
Edit Permission	hasEditPermission	boolean	Read-only	/	Whether current user has edit permission
Creator ID	createdBy	long	Read-only	/	Module creator ID
Creator Name	createdByName	string	Read-only	/	Creator name
Creation Time	createdDate	datetime	Read-only	/	Module creation time