Troubleshooting
Overview
This troubleshooting guide addresses common issues you may encounter while using RobusTest. These solutions cover the most frequently reported problems and their resolutions.
Getting Additional Help:
If you don’t find your specific issue here, please log a support ticket for personalized assistance from our technical support team.
Common Issues and Solutions
Unable to Reach Node Server
Issue: Clicking on Manual or Automation buttons shows “Unable to reach node server” message.
Cause: Your computer is accessing RobusTest through a proxy server that blocks WebSocket protocol.
Solutions:
Configure Proxy Settings: Contact your network administrator to allow WebSocket connections
Bypass Proxy: If possible, temporarily bypass the proxy for RobusTest access
Alternative Ports: Try accessing RobusTest through alternative ports that may not be blocked
VPN Solution: Use a VPN connection that doesn’t block WebSocket traffic
Verification: Test WebSocket connectivity using browser developer tools or online WebSocket test tools.
No Live View for Hub Tests
Issue: Automation tests run on RobusTest Hub but don’t appear in Live View.
Cause: Build URL mismatch - the build URL you’re using belongs to another user.
Solutions:
Verify Build URL: Ensure you’re using the correct build URL generated for your account
Check User Access: Confirm you have access to the project containing the build
Regenerate URL: Create a new build URL from your project dashboard
User Permissions: Verify your user permissions allow access to the specific project
Verification: Check that the build appears in your project’s build list.
Live View Test Steps Not Visible
Issue: Unable to see test steps in Live View for your device.
Cause: Firewall is blocking test step execution information.
Diagnosis:
# Test connectivity to RobusTest server
telnet <RobusTest_Installation_Address> <port_number>
Solutions:
Firewall Configuration: Contact your network administrator to open required ports
Port Testing: Test specific ports used by RobusTest Live View
Alternative Access: Use a different network connection to bypass firewall restrictions
VPN Access: Connect through a VPN that doesn’t have these restrictions
Required Ports: Ensure the following ports are open: - HTTP: 80/443 - WebSocket: 8080/8443 - Live View: Custom ports (contact support for specifics)
Unable to Access RobusTest
Issue: Cannot access RobusTest platform at all.
Diagnosis Steps:
Network Connectivity: Verify your computer is connected to the network
Server Reachability: Test server connectivity:
# Test basic connectivity
ping <RobusTest_server_IP_address>
# Test HTTP connectivity
curl -I <RobusTest_server_URL>
# Test specific port
telnet <RobusTest_server_IP> <port>
Solutions:
Network Issues: - Check your internet connection - Verify DNS resolution - Try accessing from a different network
Server Issues: - Server may be down for maintenance - Contact your RobusTest administrator - Check server status page (if available)
Firewall/Proxy Issues: - Configure proxy settings - Whitelist RobusTest domains - Open required ports
Browser Issues: - Clear browser cache and cookies - Try a different browser - Disable browser extensions
Performance Issues
⚡ Performance Problem
Issue: RobusTest is slow or unresponsive.
Common Causes and Solutions:
Network Latency: - Check your internet speed - Use a wired connection instead of Wi-Fi - Move closer to your router
Browser Performance: - Close unnecessary browser tabs - Clear browser cache - Update to the latest browser version
Device Resource Issues: - Close other applications - Restart your computer - Check available RAM and CPU usage
Server Load: - Try accessing during off-peak hours - Contact support if persistent
Device Connection Issues
📱 Device Connectivity Problem
Issue: Devices not appearing or showing as disconnected.
Solutions:
Device Status: Check device status on the Health Page
USB Connection: Ensure USB debugging is enabled (for local devices)
Network Issues: Verify network connectivity between device and server
Device Restart: Restart the device and try reconnecting
Node Status: Check if the node hosting the device is online
Test Execution Failures
🧪 Test Execution Problem
Issue: Tests fail to execute or complete.
Common Solutions:
App Installation: Ensure the app is properly installed on the device
Permissions: Verify app has required permissions
Device Compatibility: Check device compatibility with your app
Test Script Issues: Review test scripts for errors
Resource Availability: Ensure device has sufficient resources
Best Practices for Troubleshooting
💡 Pro Troubleshooting Tips
Effective Troubleshooting Strategy:
Document Issues: Keep track of error messages and steps that led to the problem
Check Logs: Review browser console logs and RobusTest logs
Isolate Problems: Try to reproduce the issue in a controlled environment
Update Software: Keep your browser and operating system updated
Contact Support: Don’t hesitate to contact support with detailed information
Getting Help
🆘 Support Request Checklist
When contacting support, please provide:
📝 Detailed description of the issue
🔄 Steps to reproduce the problem
📷 Screenshots or error messages
💻 Browser and operating system information
🌐 Network configuration details (if relevant)
See also
Related Topics:
User Profile - Accessing support and help resources
Health Page - Monitoring device and node status
Unable to access RobusTest Server - Detailed server access troubleshooting unreachable or that the server is down. Please check on this with your IT team If the ping command is successful and you are able to reach the server, then we check if the RobusTest server is running successfully.
Visit the RobusTest processes page and ensure that all processes are running as expected The URL for RobusTest processes page looks as below
http://<robustest server url>:9001
Make sure all the processes are in running state. In case the URL above is not reachable, it means the RobusTest server is not running. Start the RobusTest application by running the following command on the system. You will need to login to the RobusTest server using putty or similar tool.
# cd /opt/code/RobusTest # screen -S FrontEnd # sudo su (enter the password when prompted) # ./StartServer.sh
To find out the IP addresses of the deployment servers other such details, please contact your RobusTest administrator.