Service Introduction

AngusTester's service management module helps teams efficiently organize and manage microservice interfaces, enabling API assetization and building clear API architecture to enhance interface maintainability and collaboration efficiency.

About Services

Services are the core units of API management, with each service corresponding to a microservice entity. Through the service module, you can:

• ✅ Structured Organization: Categorize interfaces by service, clarifying boundaries and dependencies
• ✅ Asset Management: Centrally manage all interfaces under a service, improving traceability
• ✅ Optimized Team Collaboration: Standardize service specifications to accelerate development and testing processes

Example Scenario: Create an independent service unit for an order microservice to centrally manage order creation, query, payment, and other interfaces

Value Benefits

Through AngusTester's service management module, teams can achieve:

• 🚀 Efficiency Improvement: Reduce interface maintenance time by 60%
• 🔍 Consistency Assurance: Ensure unified interface specifications within services
• ⚙️ Architecture Optimization: Clearly map microservice dependencies
• 📊 Controlled Quality: Quickly validate service health through batch testing

Best Practice Recommendations:

1. Create independent service units for each microservice
2. Synchronize interface definitions via OpenAPI specifications
3. Regularly perform service-level batch regression tests

Experience AngusTester Service Management Now →

Core Features

1. Interface Management: Flexible Creation and Import

Supports multiple interface creation methods to adapt to different work scenarios:

Method	Supported Formats	Core Advantages
Manual Creation	-	Customize interface details to meet specific needs
File Import	Swagger/OpenAPI	Automatically sync documentation, reducing manual input errors
Tool Sync	Postman Collections	Seamlessly migrate existing interfaces while preserving historical configurations

2. Batch Operations: Efficient Handling of Interface Assets

Significantly improve maintenance efficiency with batch functions:

• Batch Import/Export: Quickly migrate service assets (supports JSON/YAML formats)
• Batch Editing: Simultaneously modify paths/parameters/response settings for multiple interfaces
• Batch Testing: One-click automated testing for all interfaces under a service

Service Field Information

Parameter	Field Name	Type	Required	Length Limit	Description
ID	id	bigint	Conditional	/	Unique identifier; Automatically generated by the system; Required for modifications
Project ID	projectId	bigint	Yes	/	Associated project ID, required when creating a service
Service Name	name	string	Yes	<=100	Service name, e.g., User Center
Authorization Control	auth	boolean	No	/	Whether to enable authorization control, disabled by default
Service Source	source	enum	Read-only	/	Service Source Enum Values: • CREATED - Created • EDITOR - Editor • IMPORT - Imported • SYNC - Synced
Import Source	importSource	enum	Read-only	/	Valid when source=IMPORT: • OPENAPI - OpenAPI • POSTMAN - Postman • ANGUS - Angus
Service Status	status	enum	No	/	Current Status Enum Values: • UNKNOWN - Unknown • IN_DESIGN - In Design • IN_DEV - In Development • DEV_COMPLETED - Development Completed • RELEASED - Released
Contains Interfaces	hasApis	boolean	Read-only	/	Whether interfaces have been created
Mock Service ID	mockServiceId	bigint	No	/	Associated Mock Service ID
Interface Count	apisNum	bigint	Read-only	/	Total number of interfaces under the service
Interface Test Case Count	apisCaseNum	bigint	Read-only	/	Total number of test cases under the service
OpenAPI Specification	schema	object	Read-only	/	OpenAPI specification details
Tenant ID	tenantId	long	Read-only	/	Tenant ID
Creator ID	createdBy	bigint	Read-only	/	Creator ID
Creator	createdBy Name	string	Read-only	/	Creator name
Creation Time	createdDate	datetime	Read-only	/	Service creation time
Last Modified By ID	lastModified By	bigint	Read-only	/	Last modifier ID
Last Modified By	lastModified ByName	string	Read-only	/	Last modifier name
Last Modified Time	lastModified Date	datetime	Read-only	/	Last modification time

Status Flow Diagram

Key Field Descriptions

1. When creating a new service:

• Required fields: projectId, name
• Recommended initial value: status="In Design"
• Default values: auth=false, hasApis=false

2. Importing OpenAPI services:

• Set source="IMPORT"
• Set importSource="OpenAPI"
• Automatically populate the schema object

3. Service release process:

In Design → In Development → Development Completed → Released

4. Permission control:

After enabling auth, data permission authorization must be configured. It is recommended to enable this after test verification or upon release