Welcome to the new Parasoft forums! We hope you will enjoy the site and try out some of the new features, like sharing an idea you may have for one of our products or following a category.
The request has an attached output, but it is no longer being requeste
Options
LegacyForum
Posts: 1,664 ✭✭
in FAQ
How do you resolve this error message?
The most usual case when you get that message is when you record a functional test scenario with the "Auto Generate Response Stubs" option turned on in the recording wizard. That option causes stubs to be created for all asynchronous requests seen while recording. The stubs get attached to the tests where the asynchronous requests were detected during the recording. However, asynchronous requests do not always occur at the same time in Ajax scenarios. This can cause them to occur during different tests on playback than they did during the recording, or sometimes they may not happen at all during playback. When this happens, you can see the message that you described.The other situation where you will see this message is when you have attached an output tool to an individual request by right-clicking on the test and choosing "Add Output". The reasons you see the message are the same even if you added the output manually. The other reason you could see the message is that the URL for the request has changed slightly.
The easiest way to resolve this is to turn off the "Auto Generate Response Stubs" message while recording. You should only use that option when you know that you want to stub asynchronous requests. If you have no specific reason to stub those requests, don't use that option.
If you need some of the stubs but not all, or you don't want to re-record your scenario, or you are getting the message as a result of manually adding an output, you can do one of two things. Either remove the output completely, or (in the case where the request URL has changed), recreate the output on the new URL using "Add Output".
0