There are a variety of ways to test SessionCam using your own processes or third party software.
We’ve outlined our recommended approach to testing below:
How to test recording
You can view the calls that SessionCam makes using developer tools such as Firebug or Fiddler web Proxy.
As such you can test that SessionCam is recording correctly by looking for the following calls:
- JS call
- Flash file call: This call will only trigger for browsers that do not support CORS (Cross-origin resource sharing). To see if your browser supports CORS you can check here. If your browser supports CORS you won’t see this request.
- Config call: This decides the config options for SessionCam — whether to record or not, which fields to mask out and other config options. If the config specifies that recording should start then we'll carry on, if not there will be no more activity.
- Get PageID call: Sends the page HTML and is usually only called once per page.
- Save Events Call: These are generally sent every second while there are events being monitored. If this happens and the site is operating as normal then everything is OK.
How to test replay
Once you are happy that recording is working correctly, you can check that sessions are coming into the SessionCam console.
You can do this by browsing your website and then checking in the console. You can:
- Find your session by using the IP address filter
- View the replay of your session and check that it’s functioning as expected (e.g pages are numbered correctly and images appear as they should).
Note that if you do not see assets, you may need to allow our IP addresses.
If you encounter a problem during testing, contact our support team who can investigate and resolve the problem for you.