Bandwidth testing for superior user experience – here’s how?

The bandwidth Testing process simulates a low internet bandwidth connection and checks how your application behaves under desired network speed.

Considering a scenario where a specific application’s home page always loads in milliseconds in office premises this may not be the case when an end-user with low network speed accesses the application. To enhance user experience and get to know the application load times at specific network bandwidth speeds, we can simulate it and identify specific component/service call which is taking more time and can be improved further.

Prerequisites:

Bandwidth testing using Chrome browser. You should set your ‘Network’ panel in the chrome browser as per the below requirements.

Setup:

  1. Go to Customize and control Google Chrome at the top right corner and click More tools, then select Developer tools
    • Or press keyboard shortcut Ctrl + Shift + I
    • Or press F12
  2. Then click the ‘No throttling’ dropdown and choose Add… option under the Custom section.
  3. Click Add custom profile
  4. You will need to enter profile name in order to click on Add button. For example, ‘TestApp 1 MBPS’.
  5. Fill in the Download, Upload, Latency columns as below and click Add.

Example for 100Kbps:

Download (kb/s)Upload (kb/s)Latency (ms)
10050300

Example for 1Mbps:

Download (kb/s) Upload (kb/s)Latency (ms)
102451250

Example for 2.5Mbps:

Download (kb/s)Upload (kb/s)Latency (ms)
2600150030

Configuring Chrome is a one-time affair. Once Chrome has been configured for bandwidth testing, use the same settings by selecting the profile name [TestApp 1 MBPS] from the No Throttling drop-down.

Metrics to be collected for bandwidth testing:

  • Data transferred (KB)
  • Time taken for data transfer (seconds)

Using Record network activity option in the Chrome browser, you can get the above attributes.

Note: Toggle button “Record network log”/”Stop recording network log” and button “Clear” are available in the network panel.

It is best practice to close all the non-testing applications/tools in the system and other tabs from Chrome where the testing is performed.

Steps for recording network activity:

  1. Open Developer Tools and select the Network tab.
  2. Clear network log before testing.
  3. Make sure Disable cache checkbox is checked.
  4. Select the created network throttling profile (say ‘TestApp 1 MBPS’).
  5. Start recording for the steps to be measured as per the scenario file.
  6. Wait for the completion of step and page is fully loaded to check the results
  7. Data transferred size for each recorded step will be displayed down in the status bar as highlighted. The size will be in byte/kilobyte/megabyte. Make note of it.
  8. Time taken for data transfer will be displayed in the timeline graph. The horizontal axis represents the time scale in a millisecond. Take the
  9. Maximum time. Take approximate value from the graph and make note of it.

Here is the sample screenshot taken for login process of snapdeal application page in which specific js component (base.jquery111.min.js) loading took 4.40s and also while searching for any product searchResult.min.js took 4.08s which can be improved further for better user experience.

This Bandwidth Testing Process helps in every possible way to improve user experience by identifying specific component or API calls which are taking more time to load and it helps developers to fix those specific components.

Your application’s performance is a major differentiator that decides whether it turns out to be a success or fails to meet expectations. Ensure your applications are peaked for optimal performance and success.

Trigent’s experienced and versatile Quality Assurance and Testing team is a major contributor in the successful launch, upgrade and maintenance of quality software used by millions around the globe. Our experienced responsible testing practices put process before convenience to delight stakeholders with an impressive industry rivaled Defect Escape Ratio or DER of 0.2.

Responsible Testing – Human centricity in Testing

Why responsibility in testing?

Consumers demand quality and expect more from products. The DevOps culture emphasizes the need for speed and scale of releases. As CI/CD crisscrosses with quality, it is vital to engage a human element in testing to foresee potential risks and think on behalf of the customer and the end-user.

Trigent looks at testing from a multiplicity of perspectives. Our test team gets involved at all stages of the DevOps cycle, not just when the product is ready. For us, responsible testing begins early in the cycle.

Introduce the Quality factor in DevOps

A responsible testing approach goes beyond the call of pre-defined duties and facilitates end-to-end stakeholder assurance and business value creation. Processes and strategies like risk assessment, non-functional tests, and customer experiences are baked into testing. Trigent’s philosophy of Responsible Testing characterizes all that we focus on while testing for functionality, security, and performance of an application.

Risk coverage: Assessing the failure and impact early on is one of the most critical aspects of testing. We work along with our clients’ product development teams to understand what’s important to stakeholders, evaluate and anticipate risks involved early on giving our testing a sharp focus.

Collaborative Test Design: We consider the viewpoints of multiple stakeholders to get a collaborative test design in place. Asking the right questions to the right people to get their perspectives helps us in testing better.

Customer experience: Responsible Testing philosophy strongly underlines customer experience as a critical element of testing. We test for all promises that are made for each of the customer touchpoints.

Test early, test often: We take the shift-left approach early on in the DevOps cycle. More releases and shorter release times mean testing early and testing often that translates into constantly rolling out new and enhanced requirements.

Early focus on non-functional testing: We plan for the non-functional testing needs at the beginning of the application life cycle. Our teams work closely with the DevOps team’s tests for security, performance, and accessibility – as early as possible.

Leverage automation: In our Responsible Testing philosophy, we look at it as a means to get the process to work faster and better. Or to leverage tools that can give better insights into testing, and areas to focus on testing. The mantra is judicious automation.

Release readiness: We evaluate all possibilities of going to the market – checking if we are operationally ready, planning for the support team’s readiness to take on the product. We also evaluate the readiness of the product, its behavior when it is actually released, and prepare for the subsequent changes expected.

Continuous feedback: Customer reviews, feedback speaks volumes of their experience with the application. We see it as an excellent opportunity to address customer concerns in real-time and offer a better product. Adopting the shift-right approach we focus on continuously monitoring product performance and leveraging the results in improving our test focus.

Think as a client. Test as a consumer.

Responsibility in testing is an organizational trait that is nurtured into Trigent’s work culture. We foster a culture where our testers imbibe qualities such as critical thinking on behalf of the client and the customer, the ability to adapt, and the willingness to learn.

Trigent values these qualitative aspects and soft skills in a responsible tester that contribute to the overall quality of testing and the product.
Responsibility: We take responsibility for the quality of testing of the product and also the possible business outcomes.

Communication: In today’s workplace, collaborating with multiple stakeholders, teams within and outside the organization is the reality. We emphasize not just on the functional skill sets but the ability to understand people, empathize with different perspectives, and express requirements effectively across levels and functions.

Collaboration: We value the benefits of a good collaboration with BA/PO/Dev and QA and Testing – a trait critical to understand the product features, usage models, and work seamlessly with cross-functional teams.

Critical thinking: As drivers of change in technology, it is critical to developing a mindset of asking the right questions and anticipating future risks for the business. In the process, we focus on gathering relevant information from the right stakeholders to form deep insights about the business and consumer. Our Responsible Testing approach keeps the customer experience at the heart of testing.

Adaptability & learning: In the constantly changing testing landscape, being able to quickly adapt to new technologies and the willingness to learn helps us offer better products and services.

Trigent’s Responsible Testing approach is a combination of technology and human intervention that elevates the user experience and the business value. To experience our Responsible Testing approach, talk to our experts for QA & Testing solutions.

Learn more about responsible testing in our webinar and about Trigent’s software testing services.