When SQL Server is set as test repository you can query test log directly and generate custom reports using external analytical tools. The test repository table structure is shown below.
is the main table that stores all session information. Session's time-based performance metrics is stored in Fiddler session timer format described here. The following six timers used:
ClientBeginRequest- Time at which this HTTP request began. May be much later than ClientConnected due to client connection reuse.
ClientDoneRequest- Exact time that the client browser finished sending the HTTP request to StresStimulus or Fiddler.
ServerGotRequest- Exact time that StresStimulus or Fiddler finished (re)sending the HTTP request to the server.
ServerBeginResponse- Exact time that StresStimulus or Fiddler got the first bytes of the server's HTTP response.
ServerDoneResponse- Exact time that StresStimulus or Fiddler got the last bytes of the server's HTTP response.
ClientDoneResponse- Exact time that StresStimulus or Fiddler finished transmitting the HTTP response to the client browser.
API for querying session content
The Query Log allows to display session content in the session grid. However, the capacity of the session grid to display a very large number of records is limited. For such situations an option exists to query session content directly from the test repository.
Session data is stored in the
ResultData table in the SQL Server database. However requests and response information is stored UTF8 binary encoded form.
to decode session content to clear text use build-in function
Utf8ToNVarChar() as shown below:
SELECT dbo.Utf8ToNVarChar(RequestBytes) AS RequestChars, dbo.Utf8ToNVarChar(ResponseBytes) AS ResponseChars FROM ResultData
- No labels