Help & FAQs

Testers.Network is a platform that connects Android developers with testers who have access to real physical devices.

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
• 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

You can see the detailed pricing when you select devices on the dashboard.

Automatic Testing:

• Our system automatically interacts with your app
• Tests run according to the schedule you set
• Standard user interactions are simulated

Manual Testing:

• Human testers interact with your application
• More exploratory and intuitive testing approach

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

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 be cancelled if they are in 'Waiting for Start', 'Waiting for Payment', or 'In Progress' 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 provide access to testers by E-mail without using Google groups:

1. After logging in, go to the Testing History section.
2. In the Devices column, click on the icon in the 'Devices' section and click 'Display Devices'
3. You will see a list of devices on which testing is taking place and their E-mail address.

Important notes:

• Delete all spaces at the beginning and end of the list, separate the e-mail addresses with commas
• 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

We always welcome feedback to improve our platform or to report any issues you encounter.

Please send your suggestions, feature requests, or bug reports to support@selfwallet.io.

Our team actively reviews all feedback and uses it to prioritize future improvements to the platform.

To ensure a sustainable testing environment, we occasionally need to limit testing access for certain applications:

• Some applications may be denied full testing access on our platform
• Others may only have access to paid devices or devices with manual testing capability

We apologize if our service doesn't meet your current needs. We're continuously working to improve our platform's capabilities.

If you paid for testing that was subsequently canceled, please contact our support team for a refund.

Every few months, we purge old testing data to optimize our database or when implementing changes that are incompatible with previous testing history.

This is part of our regular maintenance process to ensure the platform runs efficiently.

We recommend downloading or recording important testing results if you need to maintain records beyond our retention period.

Our testing platform has several limitations you should be aware of:

Automated Testing Limitations:

• File Size: Applications larger than ~40-50MB may not be suitable for automated testing
• Permissions: Certain permissions cannot be granted automatically, including camera, microphone, contacts, and GPS access
• Root Access: Devices do not have root access
• Launch Time: Your application must launch within 30 seconds on the test device for successful testing
• Network Access: Some IP addresses and network protocols may be blocked by our firewall
• Test Completion: After completing all tests for the day, your app will be force-closed to free memory but will not be uninstalled until the testing period ends
• Paid Applications: Testing of paid applications or paid functionality within the app is not available in automated testing. This is only possible via manual testing.

For testing that requires permissions, larger app sizes, paid features, or other special needs, we recommend our paid manual testing services.

If your app requires promo codes (for paid functionality or access) — please include them in the wishes/comments section when creating a manual testing request.

Note that we don't offer app update testing during an active testing session. You would need to cancel the current testing and create a new request (refunds are not provided for unused testing time).

Only one testing process per application can be active at any given time.

Our paid manual testing service offers several advantages over automated testing:

• Human Testers: Your application is tested by a real person who can grant all necessary permissions
• No Size Limits: There's no limit on application file size
• Guaranteed Feedback: You'll receive at least one review and rating for your application (note that we cannot guarantee positive reviews)
• Custom Instructions: You can provide specific testing instructions or scenarios
• Priority Support: Priority assistance for any issues that arise during testing

Manual testing is ideal for applications that require user interaction, access to sensitive permissions, or have complex functionality that automated testing cannot effectively evaluate.

There are several potential reasons for a 'Failed' status in your device testing logs:

• Device Compatibility: You may have selected a device that's incompatible with your app's API level requirements
• Tester Access: You might not have added our tester group to your app's testing access list
• App Size: Your application may be too large for automated testing
• Malicious Behavior: If our system detects potentially harmful behavior in your application

We investigate all 'Failed' statuses and attempt to resolve issues when possible. In some cases, we may need to block your application from testing on our devices if we detect malicious behavior.

When configuring your testing settings, you specify a start date and time in UTC format. Here's how our scheduling works:

• Testing will begin each day at your specified time
• Tests will be distributed over a 20-hour window
• The specified number of tests will be executed as devices become available

This means that while testing will start on the date you specify, individual tests may not begin precisely at your start time due to device availability and scheduling optimization.

NOF Token is a cryptocurrency developed by Selfwallet LTD. Here's what you need to know:

• You can obtain NOF Tokens by exchanging TRX through a smart contract
• For more details, visit https://nof.selfwallet.io
• We sometimes accept payment in NOF Tokens during manual transactions with users
• Payments in NOF are typically about 30% cheaper, though you may lose approximately 20% in exchange rates
• We use NOF Tokens to compensate our testers

In the future, we plan to transition to accepting payments exclusively in NOF Tokens for our testing services.

We periodically post information about tester recruitment on the main page of testers.network. Here's how the process works:

• You install our testing app on your smartphone
• The app notifies you when and which applications need testing
• It tracks your testing activities
• You confirm task completion at the end of the testing period
• If the client has no outstanding concerns about the testing, you receive payment

There are specific requirements for how testing should be conducted. We provide detailed instructions to all testers who join our network.

Keep an eye on our website for announcements about tester opportunities.