Frequently Asked Questions

Q1: Which desktop browsers are supported by Testize's service?

The Following browsers are supported:

  • Windows: Internet Explorer 7, 8, 9, 10, Firefox, Chrome and Opera 12.
  • Mac OS X: Safari 6, Firefox, Chrome and Opera 12.
  • Linux: Firefox, Chrome and Opera 12.

  • Q2: Which mobile devices are supported?

    We currently support the following devices:

  • iOS devices: iPhone 5S (iOS7), iPhone 5, iPhone 4S, iPhone 3GS; iPad 2 and iPad New.
  • Android devices: Nexus 7 tablet (Android 4.2.2), Nexus 4 phone (Android 4.1), and Nexus One phone (Android 2.3.3)

  • Additional mobile device and platform support, such as Windows Phone 8, Surface, etc., are expected in a near future.

    Q3: Will TestizeScore change if I restart only one test result

    Restarting a single result for a specific browser/device will not trigger a TestizeScore recalculation. You will need to restart all of the screenshots to recalculate your TestizeScore.

    Q4: Why I don't see a TestizeScore or any metrics when using sites with Basic/Form-based Authentication?

    Unfortunately, the majority of site metrics apply to public sites only and don't support sites with authentication.

    Q5: Why don't I see Internet Explorer screenshots when testing a site with Basic Authentication?

    This is a known Internet Explorer issue. Please refer to this KB for more details.

    Q6: Is Form-based Authentication Supported?

    Both basic and form-based authentication is supported. Users are able to specify a dedicated web page that displays an authentication form and an additional web page to validate the success of authentication against predefined text on a page. Also, verification text can come in the form of a regular expression. While basic HTTP authentication is supported for all users, form-based authentication support is reserved for paying users due to the additional resources required to support this feature.

    Q7: How to test local sites?

    We support a secured HTTPS tunnel between our Testize network and your machine (Linux, MacOS, Windows), so you could test your local sites. Please download and install this small tool for you operating systems and follow site's instruction to configure web tunneling in few clicks. After the web tunneling is set, just use the tunneled site address (https://...) and use that URL address with our Testize service, the same way as you test other sites.

    Q8: How to filter Testize's hints in site analytics of my web site?

    Many websites nowadays use various 3rd party web analytical services, such as Google Analytics, Yahoo Web Analytics, Crazy Egg, Yandex.Metrica, etc.
    One of the side effects of using these services is that all non-human visits are recorded with 100% bounce rate, affecting results. Non-human visits are detected by time spend on site and your behavior on site, which cannot be reproduced by web testing tools effectively. To overcome this issue, you can use one of the following approaches:

  • "Active approach" - to prevent visits from Testize (or any other service) being recorder first place. In order to achieve that, special code has to be added to the website that wraps analytics code snippet with a condition that checks for request's originating IP and header values. When the request is identified coming from Testize, the analytics code should not be activated.
  • "Passive approach" - to filter visits from specific IP addresses. The following article describes how to set up such filters in Google Analytics ( Other major analytics and monitoring tools should have similar capabilities.
  • Q9: Why many of my test's screenshots results fail?

    Depending on the number of selected devices/browsers and the type of hosting service, your hoster may drop/reset connection to your site. This is a most common behavior for shared hosting provides, which usually have quite limited bandwidth capacity.
    When you start a new test, our cloud-based service resolves your site and analyze its content from the multiple locations around the world to test your site thoroughly and identify not only content issues but accessibility cross-mobile/browser issues as well. It means that number of requests to your site will be equal to the number of selected browsers. For example, you run the test against 25 browsers and there will be 25 concurrent requests to your site (1 per testing browser). The shared hosting provider may reset/drop multiple concurent connections to optimize its workload.
    When you see such behavior, consider either testing your site on smaller subset of devices and browsers, or changing the hosting provider.

    Test Your Site:

    • 25 browsers & mobile devices
    • Performance and loading time
    • Compliance to web standards