Testing Environments

Please make sure to always stay on the given test environment. If the domain changes while navigating through the website, you are testing a different product. Unless stated differently, this other website is not in scope and corresponding bugs will be rejected. For example, the footer link Give us your feedback on the website http://www.europcar.com leads to http://www.europcar-feedback.com/. Despite the similar name and design, it is a different website and not supposed to be tested, if not given further instructions.

Subdomains are typically used to distinguish different services or sections of a website. We at test IO use features to subdivide software into more comprehensible parts, which is why we will provide them for such services on subdomains, if we want them to be tested. For example, the header link marketplace on the website http://www.asos.com leads to https://marketplace.asos.com – a website with different header, footer, and navigation bar that obviously offers a different service. When no feature or other information are provided, subdomains are out of scope.

Live Page:

Is a live and operational website- Companies can lose revenue/customers through bugs on live websites. Therefore bugs on live pages are normally much more relevant as issues on the website which are not live yet.

Staging/Pre-Release Pages:

Are still in the development stage and are often only accessible by proxy or password.

Functional bugs are most relevant here. Some links and content, such as pictures etc. may not work properly yet and are therefore often not in Scope.

Live Apps:

Are already released and available in the app store.

Beta Apps:

Are not released yet and need to be downloaded via the link provided. Installing a beta app can be more complex than installing a live app.

If you should run into trouble installing the app you can contact the tests team-leader.