The video player was well designed to be used in high Testing bandwidth scenarios, functioning without any packet loss where bandwidth was upwards of 2MBPS. This restricted the user base for the player as it was not able to reach out to the audience who had low bandwidth internet connections.
Our team, spent time understanding the problem at hand. We then suggested that we would conduct bandwidth simulation and packet loss testing. To test how the video played in low bandwidths, we used scripts that were executed on the system’s firewall to simulate low bandwidth. We were able to test the player with bandwidths as low as 33 kbps. Similarly, to test bad internet connection, with data packet loss during transmission we again used scripts that we’re able to simulate scenarios wherein we were able to drop any percentage of packets ranging from 0 – 100. We used the ipfw (IP Firewall: service for MAC and modified the client-provided scripts to test packet loss and low bandwidth scenarios. For Windows, we used Fiddler and Charles tools, to simulate these scenarios. We created these scripts and shared them with the client. Using these scripts we were able to combine the low bandwidth and packet loss scenarios and make suggestions to improve the player’s performance
Our suggestions included: Make the video available in various bitrates and based upon the quality of the user’s internet connection the player would automatically choose the correct bitrate i.e. if a user has a slow connection the video would be played at around 464 Kbps and on a fast connection it would be played at 2128 Kbps. A typical video has bitrates such as 464 Kbps, 664 Kbps, 828 Kbps, 1128 Kbps, 1528 Kbps, 1628 Kbps, and 2128 Kbps; accommodating such a large range drastically improved the end-user experience.