From the course: Advanced JMeter

What about login screens? - Apache JMeter Tutorial

From the course: Advanced JMeter

Start my 1-month free trial

What about login screens?

“

- [Instructor] At this stage, I can point JMeter at a static website and send virtual load to that site. This is great news if the site I wanted to test is indeed static. I can navigate, click around, go to other pages, and have detailed information of the performance of all of those steps come back to Jmeter. However, web applications aren't static. They usually have login screens that require authentication, like a username and password. It's not going to do me any good to test the responsiveness of the initial login page of a web application if my company wants to know the performance of the pages that appear after that, known as the landing page. To do that, I need to give JMeter some more information, like a valid username and password. This can then be used to log into the web application to access that landing page. There are many, many different types of authentication for login screens on web applications, including the use of cookies or tokens, open standards like security markup language, there could even be third party offerings, like Oauth or OpenID. In this course, I'm going to be using a basic database powered login form. I have a valid username and password, so that's what I'll be using. To better understand the login functionality of the web application, it's best that I have a conversation with the development team first. I could also use the JMeter Test Script Recorder to visually see the login process within JMeter, and then discuss that with the team. This should allow me to have a conversation about the specifics of the login method, and to better understand it. It's all about understanding how the application handles authentication, so that I know how best to test it.

Contents