Mind the scope

Please make sure to always stay in the test environment. If the domain changes while navigating through the website, you are testing a different product. Unless stated otherwise, this other website is not in scope and corresponding bug reports 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.

Subdomains are typically used to distinguish among different services or sections of a website. We use features to subdivide software into more comprehensible parts, which is why we will explicitly provide them for 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 no other information is provided, subdomains are out of scope.


Different environments

Live sites

Live Sites are operational websites. Companies can lose customers and revenue through bugs on live websites. Therefore, bugs on live pages are normally more relevant than on the websites that are not live yet.

Since such sites are live, your actions have the same consequences as any customer's actions. Don't trigger orders and don't contact them, e.g. via support chat, phone, or email, unless stated differently in the test instructions.


Staging/Pre-release sites

Those sites are still in the development stage and are often only accessible via proxy or credentials.

Functional bugs are most relevant here. Content – such as texts, pictures, or links – may be missing or replaced by placeholders. As this is intended, content problems are often out of scope on staging environments.

Functionalities that require a manual setup to also work on staging environments might not be available because they are oftentimes not set up. This is not a valid bug because these functionalities work on the corresponding live environments and nothing needs to be fixed on them. Examples:

  • Email services. You may not receive newsletters, registration or confirmation emails.
  • Facebook Login: The staging environment URL contains a subdomain, so that the site's URL does not match and authentication fails.


Live apps

Live apps are already released and available on the App store (iOS) or the Google Play store (Android). Information for live sites also applies to Live apps (see above).


Beta apps

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

  • iOS beta apps: The provided link usually needs to be opened in the browser on your iOS device. Click on the button to install the app on your device directly.
  • Android beta apps: The provided link is usually a download link for an APK file. You can download it to any device, transfer it to your Android phone or tablet, open the file, and install the app. Alternatively, open the link on your Android device directly, download the file, and install the app.

Information for staging sites also applies to beta apps (see above).

If you run into any trouble installing an app, you can contact the team leader via the test chat. 


Related articles:

Did this answer your question?