New answers tagged

0

Try using XSLT reports this report will give you page loading time and in your script set wait.until logic below is the sample for script and the code for XSLT report. check index.html report you will page loading time. And set Web driver wait time to high like 5 minutes see the example. Hope this will help. //Wait for maximum 5 minutes if needed ...


1

Question 1: Is it useful to do separate load testing on a mobile App? So, can we say load testing of a mobile App is actually load testing of the web API...? Answer 1: Depending on the nature of testing it is always advised to run at least a subset of tests on real devices. The resources available on mobile devices are hugely different in comparison to ...


0

To answer your first question, Is it useful to do separate load testing on a mobile App? It is very useful to do a separate load testing for a mobile application because, the raise of several mobile network technologies, such as 2G, 3G, 4G, etc. has led to variations in response times with increasing load on the server. The application owner needs to ...


0

Selenium is the wrong tool for measuring page load times. Selenium can't actually block until the page finishes loading, so it has to poll the browser. Your load time precision is constrained by the poll interval. The most accurate tools for measuring page load times are browser extensions like YSlow, Firebug, and the Chrome DevTools.


2

Instead of voting for closing I am going to use your question as an example to how not to ask questions. How are we supposed to know what do you need ? we don't know what the product is, what are the company's future plans for the product or testing, what is the budget and how much time do you have or can spend automating stuff, what's your priorities, how ...


1

It simplifies to knowing what you want to measure and knowing how to determine when you have measured it. Entry criteria include: Knowing what sort of performance you are looking at. Eg maximum load, use of system resources at various loads, affect on response times as load increases, long term stability (eg memory loss), and several others. Stability of ...


1

Ask clarification questions, and lead the other side to give you an answer. It's always a good advice, but especially true for interview questions. Let's use your question as an example- How do you define performance testing ? what is our goal- do we want to verify the product can achieve X or do we want to investigate and find out what X is ? What are ...


0

Normally performance testing of mobile application is not required as mobile applications have only one user and if you're happy with application load time, responsiveness, rendering times, etc. - you should be good to go. If your application is being updated frequently and it is relatively big and complex you might want to automate the steps and set some ...


0

I feel your question is a bit contradictory/too broad of a scope. You will first need to decide what exactly you want to test.. Manual testing is usually only good for functional testing (seeing if it works the way it should). If you want to do performance testing there are multiple tooling options to consider: do you want to test the app itself (GUI) on ...


0

You can try to turn on the screen rotation and rotate the screen and instantly click on some functionalities and check if they behave they way it is expected or not.In my workplace we had issue that when the screen is rotated the functionalities wouldn't work or would take time to respond. To test it on different network, you can configure the router to ...


1

Performance testing doesn't only mean many users hitting the same thing at the same time. There are various aspects of performance testing which you can opt to do manually. As you said you have to test a mobile application, you can test, Whether it works in the same seamless manner on a phone with low hardware, OS and memory configurations as it does on ...


1

The Throughput: is the number of requests per unit of time (seconds, minutes, hours) that are sent to your server during the test. The Response time: is the elapsed time from the moment when a given request is sent to the server until the moment when the last bit of information has returned to the client. The throughput is the real load processed by your ...


0

When you are doing a load test on an application, there is a lot that you have to take into consideration, CPU utilization over time with consistent load. RAM utilization over time with consistent load. Disk I/O utilization over time with consistent load. Network I/O utilization over time with consistent load. Not just the server's CPU and RAM but its ...



Top 50 recent answers are included