Purchases in tests

If a test instructs you not to complete any purchases/orders, this means, also no such attempt should be made. This also includes cases in which the final order form is sent with missing mandatory fields or in which an external payment provider is triggered afterwards (even if this provider allows cancelling the transaction).


Endless loading

If you find a bug where an app or website keeps loading “endlessly” without any error message or crash, we require extended documentation to prove the validity of the problem:

  • Show your internet speed at the beginning and end of your screencast, e.g. via https://fast.com/
  • Show that you didn't use a proxy or VPN at the end of your screencast.


Prior-Acceptance “Guarantee”

Please note that the fact that an issue has been accepted in the past (either by the team leader or by the client) does not guarantee that the same issue will be accepted in all future tests. Of course, our aim is to evaluate all errors in a comparable way, but it cannot be completely ruled out that something has been overlooked in the past or that new information has been added in the meantime.


Social Media Signup and Login

Social media signup and login methods are, for example, Facebook, Twitter, Instagram, Google, Google+. If you cannot login or sign up on a website or in an app with them, the following severities apply:

On Staging

“Login/signup” is required:
Social Network doesn’t work = Low, since it’s often not integrated
Email doesn’t work = Critical

“Login/signup” is not required:
Social Network doesn’t work = Low, since it’s often not integrated
Email doesn’t work = High

Live System

“Login/signup” is required:
Social Network doesn’t work = High
Email doesn’t work = Critical

“Login/signup” is not required:
Social Network doesn’t work = High
Email doesn’t work = High

If the app or site crashes without an error message after an unsuccessful login or sign up, it is handled like a normal crash (critical bug).

Did this answer your question?