.NET Framework v 4.5.2 is required.
The .NET framework is available here for free here: https://www.microsoft.com/en-gb/download/details.aspx?id=42642
Hardware requirements depend directly on the volume of traffic, in terms of number per second or size of payload. In our experience a dual core desktop can support thousands of requests per second so long as the network bandwidth is sufficient.
The Stub itself is available here: http://188.8.131.52/performance-stub/
- Unzip the contents of your download to a folder of your choice, there is no install package as it’s completely portable. You can run from a pen drive if you prefer to.
- Launch the application PerformanceStub.exe and you will arrive at the main screen below (Main Window). Each row in the table represents a stub which is setup on a unique IP address and port combination on the local machine. An IP Address of 0.0.0.0 means all available IP addresses.
- In the screenshot above we can see that the example HTTP stub has failed to start but the HTTPS stub is running. In this case it’s because we have IIS installed and it’s greedily taken port 80 so our stub can’t run. The HTTPS stub runs on port 443 which (by default) IIS hasn’t taken.
- If at any point your stub fails to start you can open the debugging window by clicking “Start and View Log” button on the Main Window. See this page for more details on troubleshooting: Performance Stub Troubleshooting
- We can test it’s running by visiting the url in Internet Explorer using the following URLs :
https://localhost/example - you may get a certificate error here, see this section on certificates if you wish to host an HTTPS endpoint : Performance Stub Walkthrough : HTTPS and Certificates
- You now have a working stub…. What’s that you say you didn’t want to return “this is an example repsonse”? fear not, visit this page for details on how to configure the stub for your application : Performance Stub Walkthrough : Request Response Matching