Purchase Reports is a type of custom report used for reporting a successful transaction in the Real Payment test. 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. Please keep in mind that Purchase Reports should be used only for successful transactions; if the transaction fails, a Failed Purchase Report should be submitted.
⚠️ Please ensure that you only attempt to complete the order if you have previously reserved a task.
To submit the Failed Purchase Report, proceed as follows:
Ensure that you have an active Test Session.
Ensure that you have previously reserved a task.
Press the Submit Report button in the bottom action bar of the Test Cycle.
Select the feature for which you are reporting a bug, then under the Report type select Purchase Reports and click on the Go to external report page button.
You will land on the Test IO Issuing platform, where you will need to fill in the Transaction details.
Transaction details
When filling in a purchase report, you will have slightly different fields to fill in compared to our regular bug report form. Also, you will need to choose between selecting an existing transaction or registering a new transaction:
If you have used a card issued by Test IO, then please select Transaction from the Select a transaction dropdown menu.
If your transaction is not on the list or if you're using a different card/payment method, please select the button Register new.
Select existing
If you used the card issued by Test IO, then to fill in the Purchase Report, you will need to fill in the following fields:
Transaction: Open the "Select a transaction..." dropdown menu, and select one of the transactions from the list.
Order confirmation number: 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.
Device used: Select the device that you have used during the process. Keep in mind that the devices shown in this section are taken from your Tester Profile Devices page, so ensure that your devices are up-to-date before submitting the report.
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 or a screencast of the order process as evidence that you completed the requested task. Order confirmation pages, emails, and card statements are all relevant attachments that could be included. We recommend that your attachment always follow our Attachment rules.
Register new
Here, you will need to fill in the following details:
Payment method: Select the payment method you used to complete the transaction.
Card last 4 digits: In case a Card was used for payment, please add the last 4 digits of the card that you have used.
Payment processor: Add 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: Please select the currency from the dropdown, and in the input field, add the value.
Purchase date: Select the date that you completed the order.
Order confirmation number: 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.
Device used: Select the device that you have used during the process. Keep in mind that the devices shown in this section are taken from your Tester Profile Devices page, so ensure that your devices are up-to-date before submitting the report.
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 or a screencast of the order process as evidence that you completed the requested task. Order confirmation pages, emails, and card statements are all relevant attachments that could be included. We recommend that your attachment always follow our Attachment rules.
Best Practices for Testing and Attachments
Read the test instructions and feature descriptions carefully. If something is unclear or not straightforward, reach out immediately to TL or CSM and ask for clarification. Do not proceed on your own.
We recommend reading our Attachments rules and requirements.
Blur all sensitive information, such as unmasked card information, your real address, and other PII (Personally Identifiable Information) in your attachments. If some parts in the video (screencast) need to be blurred, you can use some free tools to blur them.
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. When you are done with testing—especially before the test cycle ends—please review your reports and ensure there are no "pending" reports.
If there are any, you may remove them by opening the detail page of the "pending" report and clicking the "Delete" button in the bottom action bar.
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!