[GitHub] [dolphinscheduler] SnowMoon-Dev commented on pull request #10817: [API-Test] [Improvement] update api test demo

[GitBox <gi...@apache.org>]

SnowMoon-Dev commented on PR #10817:
URL: https://github.com/apache/dolphinscheduler/pull/10817#issuecomment-1176975616

   > I think the development cost of this way for new contributors is much higher than that before. We should try to reduce the learning cost of development.
   
   First of all, thank you for the review suggestion you gave me, I admit that I increased the complexity of the development, I also felt this way when writing this demo, but I think it is necessary because it allows new contributions Those who know the interface definition method of each API, build test cases according to the interface definition method, instead of looking at the interface documentation or the corresponding controller code, I will add interface descriptions and corresponding links to each API interface definition later. Make the use of each interface clearer for contributors
   
   
   In addition, API testing does not completely depend on interface developers, and my current method conforms to the process of interface development. First define the interface to implement the interface method, and initialize the corresponding interface factory when writing test cases. The purpose of this interface factory It is also used for API+UI testing later. I know that although it may feel like rewriting the interface for interface developers, I think it is necessary


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@dolphinscheduler.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org