Frequently Asked Questions

Testers.Network is a platform that connects Android developers with testers who have access to real physical devices. Our service provides access to a variety of Android devices with different specifications, screen sizes, and OS versions to ensure compatibility across the Android ecosystem.

The testing process is simple:

1. Register your Google Play application URL
2. Select the devices you want to test on
3. Configure your testing parameters (duration, frequency, etc.)
4. Choose between automated or manual testing
5. Receive detailed reports and analytics

We offer a range of pricing options to suit different needs:

• Free Devices: Several devices are available at no cost, allowing you to test your app without any financial commitment.
• Premium Devices: Advanced and newer devices are available at minimal daily rates.
• Testing Duration: The cost may vary based on how long you need the devices and how many tests you want to run.

You can see the detailed pricing when you select devices on the dashboard. We follow a pay-as-you-go model, so you only pay for what you actually use.

Automatic Testing:

• Our system automatically interacts with your app
• Tests run according to the schedule you set
• Standard user interactions are simulated
• Great for regression testing and regular monitoring
• Reports are generated automatically but may take longer to process

Manual Testing:

• Human testers interact with your application
• More exploratory and intuitive testing approach
• Can focus on specific features or user flows
• Provides qualitative feedback on user experience
• Reports are created manually and include more detailed observations

You can choose the approach that best suits your needs or combine both for comprehensive testing. Each method produces different types of reports with varying delivery timeframes.

Our testing platform provides comprehensive reports and analytics, which vary depending on the testing method:

Automated Testing Reports:

• Functionality issues detected automatically
• Performance metrics based on device sensors
• Screenshots at predefined checkpoints
• Technical logs and error reports
• These reports are standardized and delivered quickly

Manual Testing Reports:

• Detailed human observations about user experience
• Subjective assessment of app responsiveness and usability
• Specific feedback on UI/UX elements
• Custom screenshots highlighting specific issues
• These reports are more detailed but take longer to prepare

All reports include:

• Functionality Reports: Details on any crashes, errors, or unexpected behavior
• Performance Metrics: Loading times, responsiveness, and resource usage
• Compatibility Information: How your app performs across different devices and OS versions
• Visual Verification: Screenshots showing how your UI appears on various screen sizes
• Log Files: Detailed technical logs for debugging purposes

All reports are presented in an easy-to-understand format and can be downloaded for offline analysis.

We take security seriously and implement several measures to protect your application:

• Physical devices are wiped after each testing session is completed
• Your app and data are never shared with unauthorized third parties
• All connections between our systems are encrypted using industry-standard protocols
• We do not store your app's source code or sensitive assets

Please note that testing devices do have internet access to simulate real-world usage conditions. This is essential for testing features like online connectivity, user authentication, and cloud synchronization.

We only access publicly available versions of your app from Google Play, using the URL you provide during registration.

Yes, you can cancel a testing request through your dashboard:

1. Navigate to the "Testing History" section
2. Find the test you want to cancel
3. Click the "Cancel" button
4. For paid tests, you'll need to enter your cancellation PIN code

Important notes about cancellation:

• Tests can only be cancelled if they are in "Waiting for Start" or "Waiting for Payment" status
• For paid testing requests, you'll need the PIN code provided during the test creation
• Payments are non-refundable for cancelled tests that have already been paid for
• You won't be charged for cancelled tests that haven't been paid for yet

We offer several payment options depending on the amount:

USDT (TRC-20) Cryptocurrency:

• For any amount, we accept USDT on the TRC-20 network
• After selecting your devices and testing parameters, you'll see the total cost
• You'll receive a USDT wallet address
• Transfer the exact amount to the provided wallet address
• Your testing will begin automatically once payment is confirmed

PayPal:

• Available for amounts exceeding $100
• Contact us at info@selfwallet.io to arrange payment
• Include your testing request ID in your email

Corporate Business Account:

• Available for amounts exceeding $1000
• Contact us at info@selfwallet.io for invoice and payment details
• We'll provide formal documentation for your accounting department

Important notes:

• Always save your cancellation PIN code in case you need to cancel the request
• Make sure to send the exact amount requested when using cryptocurrency
• Only use the TRC-20 network for USDT transfers
• Payments are non-refundable after testing has begun

If you have any questions, issues, or feedback that isn't addressed in our FAQ, you can reach our support team at support@selfwallet.io.

Please note:

• We aim to respond to all inquiries within 48 hours
• For technical issues with the website or testing platform, please contact support@selfwallet.io
• For business inquiries or payment arrangements, please contact info@selfwallet.io
• We cannot provide support for Google Play issues or how Google Play functions
• For urgent matters, please include "URGENT" in your email subject line

While we strive to provide reliable and accurate testing services, please be aware of the following disclaimers:

• Testers.Network acts as a platform connecting app developers with testers, and we cannot guarantee that all possible bugs or issues will be identified during testing
• Test results are informational only and should be used as part of your broader quality assurance strategy
• We are not responsible for any decisions you make based on testing reports
• The performance of your app on testing devices may differ from performance on other devices with similar specifications
• We do not guarantee app approval by Google Play or any other app store based on our testing
• Our liability is limited to the amount paid for testing services
• Test devices have internet access and while we take security measures, we cannot guarantee absolute privacy

By using our service, you acknowledge and accept these limitations. For complete terms and conditions, please refer to our Terms of Service.

To add multiple email addresses from a spreadsheet to your Google Play Console testers list:

1. In your spreadsheet, the cell below the yellow cell automatically aggregates all email addresses
2. Select and copy this cell containing all the email addresses
3. Paste the copied content into the field for adding tester emails in Google Play Console

Important notes:

• Remove any quotation marks at the beginning and end of the list to avoid errors
• Remember to press Enter after pasting to activate the "Save Changes" button

There are two common reasons why testers might see "File not found" or "Page not found" messages:

1. Tester emails not added to Google Play Console:
   • Navigate to Play Console → Closed testing → Manage version → Number of testers → Create mailing list
   • Ensure all tester emails are properly added to your tester list
2. Country/Region restrictions:
   • Testers from countries not included in your testing availability cannot access the app
   • Verify your country settings at Play Console → Closed testing → Manage version → Countries/Regions

The approval timeline varies significantly between applications:

• Google officially states a 7-day review period, but actual times vary widely
• Some applications are approved within hours, while others may take several weeks or months
• Several developers report that contacting Google Support after the 7-day period can help expedite the process

We recommend building in extra time for the approval process when planning your app launch schedule.

No, releasing updates during closed testing will not reset the testing timer.

In fact, releasing updates during closed testing is recommended and demonstrates to Google that you're actively improving your application based on tester feedback.

Google doesn't always provide specific reasons for rejecting a production release after closed testing. Based on collective experience, here are strategies to increase your chances of success:

Best Practices for Successful Testing:

• Release regular updates during the closed testing period to demonstrate active development and response to feedback
• Provide comprehensive answers in the post-testing questionnaire that Google will send you
  • Example question: "How did you determine your app was ready for release?"
  • Poor answer: "I don't know" or "It seems fine"
  • Good answer: "I consistently updated my application based on tester feedback until testers no longer reported significant issues or questions about functionality. This iterative improvement process indicates the app is now stable and ready for public release."
• Ensure genuine tester activity during the testing period
  • While opinions vary on the required level of tester engagement, having at least a few testers who open your app regularly (even briefly) during the testing period may improve your chances