IT Connect

Information technology tools and resources at the UW

As part of the report publishing process, reports go through performance testing.  You (the report developer) are responsible for supplying 3 different scenarios that represent a user’s typical report viewing activity.  These scenarios are provided in the form of “test URL strings”, which are specialized URLs that mimic a report viewing session.

An example test URL string is presented below. Use this example as a template for creating your own test URL strings.

The test URL string is made up of 4 components; the first 3 are required.  Concatenate these segments together to create a full test URL string.

Root String for Test Server

This first segment of the test URL string is the same for every report:

Sample Folder Path and Report Name for Report to be Tested

This segment varies for every report:


Rendering Component

This segment is the same for every report:


Sample Parameter Values from Query

This segment is required only if the report contains parameters from which the user can select.  It always begins with an ampersand followed by the report parameter name and values representative of users’ typical selections. You should provide selections that will initiate a rigorous test of a report’s performance.  Should you need help constructing the parameter selection, write to Your request is then logged and the Enterprise Data & Analytics (EDA) staff can retrieve sample parameter values from the Parameters column in the ExecutionLogStorage table in the ReportServer database on the EDWTEST1\Pres server.

&college=C&dept=102&major=0-ANTH-00-0-0&major=0-ANTH-00-1-1&major=0-ANTH-00-2-0&major=0-ANTH-00-2-1&major=0-ANTH-00-3-0&major=0-ANTH-00-4-1&major=0-ANTH E-00-0-0&major=0-ANTH E-00-1-1

Full Query String for Testing

Now put it all together and it looks something like this: E-00-0-0&major=0-ANTH E-00-1-1