TM Forum Community

Hi Team,

I'd appreciate your guidance on a TMF CTK implementation question.

In our projects, we usually implement only the endpoints that are required by the business. However, when running the TMF CTK, we often have to create additional endpoints and implement static/mock logic for APIs that are never used in our actual application, just to satisfy the CTK test cases.

Is this the recommended approach for TMF implementations, or is there a better way to handle these scenarios? We'd really appreciate hearing how other teams deal with this.

Example: In TMF620 Product Catalog, our application only uses GET and PATCH for Product Offering. However, to pass the CTK, we also need to implement additional endpoints such as POST Product Offering, Product Specification, Product Offering Price, and other related APIs. Since these endpoints are not part of our business flow, we end up creating them with static/mock implementations solely for CTK compliance.

We've also encountered the same situation with other TMF APIs, such as Customer Management, Reseller, Feature Management, and Service Inventory, where additional endpoints are required by the CTK even though they are not used by our business.

Also, we are working toward TM Forum certification, so we'd like to understand the recommended approach and best practices for handling these scenarios.

If anyone has faced a similar situation or can share TM Forum best practices, we'd really appreciate your guidance.
Thank you!