Friday, February 2, 2018

Performance Testing Activity for Login into application

We have many application monitoring and profiling tools but it is very difficult to distinguish between client side and server activities in the application.
Let us start the scenario from clicking of the login button in the application to identify client side and server side activity.
  • Clicks on the login button on Browser -> client side metric
  •    Initial validation (Client code validates username and password) -> client side metric
  •  Client submits request to server -> client side metric
  •  Server checks the username and password -> server side metric
  •  Server checks database with stored username -> server side metric
  •  Also server creates session for that particular user -> server side metric
  •  Server responds with home page html, which is index.html -> server side metric
  • Browser loads index.html page -> client side metric
  • Browser loads all Java script files present in index.html page -> client side metric
  • Browser loads all CSS files present in index.html page -> client side metric
  •  Browser loads all images present in index.html page -> client side metric
  •  Browser evaluates all JavaScript and CSS present in the JavaScript -> client side metric
  •     Next Browser renders index.html -> client side metric
  •    Finally end user will see the page in the browser which is completely loaded.

1 comment :