1. The breakpoint

1.1 Automatic Breakpoints

（1）Rules→ Automatic Breakpoints→ Before Requests/After Responses

Before Requests： Request breakpoint , Request from Fiddler Interrupt before sending . It is often used to modify request parameters .

After Responses： Response breakpoint , The response was interrupted after returning from the server . Often used to modify response data .

This works for all requests , That is to say , When enabled , All requests or responses will be interrupted , It needs to be released manually .

（2） Refresh the page , By Fiddler interrupt , Modification request / The response data （ This is Before Requests, So it is to modify the request parameters ）, Select the next action as needed .

Break on Response： Release request , Interrupt response .

Run to Completion： Release request , Return response .

Choose Response： Select file as response data . Click on Run to Completion after , Return the file directly （ amount to mock The role of ）.

1.2 Breakpoint command

You can use commands to interrupt specific requests , Other requests are not affected .

• bpu string： Request breakpoint ,string Is a matching string . Such as ：bpu 127.0.0.1, All requests for the domain name will be interrupted .
• bpu： Do not enable request breakpoints , amount to Disable.
• bpafter string： Response breakpoint ,string Is a matching string . Such as ：bpafter login, For all url Contained in the login Interrupt response to string request .
• bpafter： Do not enable response breakpoints .
• g/go： Release interrupted request / Respond to , But the next new request will still be blocked .
• bps status： Interrupt the request for the specified response code . Such as bps 200 Indicates that all response codes of interrupt are 200 Request .
• bpm method： Interrupts the request for the specified method . This “ Method ” refer to HTTP Method , Such as GET、POST etc. .
• bpv method： relieve HTTP Method breakpoint .

2.mock data

2.1 Response breakpoint

It has been described in detail earlier , Skip here .

2.2 AutoResponser

（1） Add rules

Enable rule： Enable rules

Unmatched requests passthrough： All requests that do not match are released .

 

Matching rules ：

Prefix	Matching instructions	give an example
No prefix	Equivalent to fuzzy search , request url If the matching string is included in the, the matching will be successful
EXACT:	Equivalent to precise search , request url Match the matching string as like as two peas to match the success.
REGEX:	Regular matching , Followed by regular expression

  Executive action ：

• It could be a website address , At this time, it plays the role of redirection
• It can also be fiddler Built in files 、 Custom response 、 Or local files
• Or set up / Add some information, etc

（2） Initiate request , You can see that the returned response is the content of the local file . 

 3.Composer

establish 、 Send a request , It can be used for simple interface testing .

3.1 Customize Request request

Fill in the request method manually 、url、 Request header 、 Request parameters, etc , Click on execute Send a request .

3.2 replay

Drag a session to Composer in , Click on execute Repeat the request .

3.3 Tamper with request data

（1） Drag a request from the conversation list on the left to Composer in ,fiddler The request mode will be automatically decomposed 、 request url、 Request header 、 Request body

（2） Modify request data ： Request parameters 、 Request first class

（3） Click on execute Send request out