In this scenario, when a user sends a command to a public account, the interaction process is user data-& amp; gt; TX server-& amp; gt; on the URL filled in, how did you debug it? In this scenario, the user sends a command to the public account. The interaction process is based on the user data, the TX server, and the entered URL.
Q: How did you debug this process?
Reply content:
In this scenario, the user sends a command to the public account. The interaction process is based on the user data, the TX server, and the entered URL.
Q: How did you debug this process?
This is a PHP debugging script I found on github (I made a branch https://github.com/kuandrew/WeTest myself)
You can modify it a little later, which is more convenient to use.
The general principle is to simulate various POST requests on the server and parse them locally using JS.
The artifact is in hand.
If you want to check whether the sent request parameters are correct, you have an online interface debugging tool.
After the URL and Token are passed, the interaction is nothing more than a question and a question. I don't understand how to debug it ^
I am debugging this way...
I applied for a test account, and then resolved the interface address DDNS to my host.
This allows debugging.
Wx.qq.com is convenient for debugging.
Use ddns to resolve to the local machine, and send messages to clients (Mobile or Desktop ).
How does the public platform implement local testing? Searching before a question is a good habit. Since you think it is inconvenient, It is not inconvenient for you alone, so there must be a solution. : P
We recommend using SocketLog debugging: https://github.com/luofei614/SocketLog
Why not mention what platform I am based on? PHP/. NET/Java/Other?