Purchase Reports

Quickly learn how to submit a Purchase Report

Zorica Micanovic avatar
Written by Zorica Micanovic
Updated over a week ago


As a tester, you play a crucial role in ensuring the quality and functionality of the software being developed. In this tutorial, we will explore an exciting new feature called "Purchase Reports". These custom reports are specifically designed for real payment testing and will help identify and resolve issues related to purchases in the application.

Understanding Purchase Reports

Purchase Reports are a type of bug that has only one severity level, which makes it easier for testers to classify them. Test instructions will always specify the requested action for each Purchase Report, making it easier for you to understand what needs to be tested and reported. The Payout information will be displayed in the right sidebar of the test instructions.

Submitting Purchase Reports

To submit a Purchase Report, follow these steps:

  1. Activate the Test Session for the relevant cycle.

  2. Click on the Submit Report button within the application.

  3. Select the appropriate feature under test.

  4. Choose from the dropdown menu the "Purchase Report" type and select "Go to external report page".

  5. You will then be directed to an external report page specifically designed for Purchase Reports.

  6. Fill in the necessary details in the report form, including all relevant information about the placed order.

  7. Once the form is complete, click on the Create Report button to submit the Purchase Report.

In the video below, you can see how to start submitting the Purchase Report.

Note: Make sure that your Purchase Report Attachments always ad here to our general rules about Bug Report Attachments.

Filling in a Purchase Reports

When filling in a purchase report, you will have slightly different fields to fill in compared to our regular bug report form. We will go through each of these fields in this section:

  • Transaction: if you're using a card issued by Test IO, please select one of the transactions from the list. If your transaction is not on the list or if you're using a different card, please select the button "Register a transaction".

    • Payment method: select the payment method you used to complete the transaction.

    • Payment processor: add here the name of the payment processor, related to the payment method selected previously. For example, if you used a Mastercard Debit card to complete the transaction, the payment method is "Debit card" and the processor is "Mastercard". Adding the name of the bank that issued the card is also relevant for some customers.

    • Amount: select the currency and the amount used when purchasing. The default values are USD and EUR. If you had to use a different currency, please select the USD option.

    • Purchase date: select the date that you completed the order

  • Order confirmation number: as the name suggests, please add any order ID or confirmation number you got when completing the purchase.

  • Purchased item: describe the item purchased, whether it is a regular item or a subscription product.

  • Notes: Please add as much relevant information as was requested in the test instructions. Usually, customers will request the type of checkout (guest or logged-in user), the credentials used, the email, and other information that identifies your order.

  • Attachments: Here, you must upload one or more screenshots of the order as evidence you completed the requested task. Order confirmation pages, emails, and card statements are all relevant attachments that could be included.

Note: You must blur ALL your sensitive information from the screenshot, such as unmasked card information, your real address, and other PII (Personally Identifiable Information), but make sure the relevant order information is not hidden in your screencast when removing the PII from it.

Managing Purchase Reports

After submitting a Purchase Report, you will have the option to make edits if necessary. In case a mistake was made, or the report is no longer relevant, testers can also delete the Purchase Report.

It’s important to note that depending on the test instructions, there may be instances where you can submit multiple Purchase Reports during the test cycle. Always follow the provided guidelines to ensure accurate reporting.

Note: After opening the external page, a "pending" report will be opened in the Test IO interface. If you close the external report page without submitting the report, the pending report will still be in the Test IO interface. You must then edit or delete the report to avoid TL rejections.

Team Leader Processes for Purchase Reports

The Team Leader is responsible for reviewing and forwarding Purchase Reports, just like other bug types. If a Purchase Report does not meet the criteria or is not relevant, Team Leaders have the option to reject it using the same reasons as they would for other bugs. They can also interact with Purchase Reports by requesting additional information from testers, leaving comments, and even liking the reports to acknowledge their contribution.

However, there are some restrictions on Purchase Reports, such as no reproduction and no list of similar bugs.

If you disagree with the decision of the Team Leader and you don’t have a Dispute block, you can submit a Dispute. It will be reviewed by our respective Dispute Team.

Purchase Reports offer an excellent opportunity for testers to contribute significantly to the improvement of real payment testing. By understanding the process of creating, submitting, and managing these custom reports, testers can effectively identify, and report issues related to purchases, ensuring a seamless and reliable user experience for customers. So, embrace this new feature, and let’s work together to enhance the quality of our application’s payment functionality!

Did this answer your question?