User:Tangiralapraveenwiki/sandbox

= UI Workstation Performance test using Jmeter/Firebug/Watir =

Purpose of this GUI Testing is to help you understand how an application can be tested according to the known and understood standards for GUI. This checklist can give some guidance to the development and QA (Testing), both the teams. Development team can make sure that during the development they follow guidelines related to the compliance, aesthetics, navigation etc. but onus of testing GUI is on the testing team and a tester responsibility to validate the product against GUI standards followed. This GUI test checklist can ensure that all the GUI components are thoroughly tested. In the first part of this checklist, we had done some parts of Functionality Testing, Usability Testing and Performance Testing

Functionality Testing
We have tested and still testing all the links in web pages, database connection, forms used in the web pages for submitting or getting information from user, and Cookie testing. Check all the links:


 * Tested the outgoing links from all the pages from specific domain under test.
 * Tested all internal links.
 * Tested links jumping on the same pages and different pages.
 * Tested if there are any orphan pages.
 * Lastly in link checking, need to check further for broken links in all above-mentioned links/pages

Usability Testing (Test for navigation)

 * Navigation provided in all the web pages while surfing is OK can say, different controls like buttons, boxes or how user using the links on the pages to surf different pages had been tested.


 * Usability testing which includes, Website should be easy to use. Still has to provide the clear instructions while page navigation and for Login/Logout successfully or not and also checked if provided instructions are correct means whether they satisfy purpose or not.


 * Main menu should be provided on each page makes ease of navigation should be consistent.

Performance Testing
Web application should sustain to heavy load. Web performance testing should include: Web Load Testing and Web Stress Testing Testing the application performance with different load and connection speed further to test in web load testing


 * Have to test if many users are accessing or requesting the same page simultaneously. Can system sustain in peak load times?
 * This we can do with Jemter by increasing the number of virtual users and we can get throughput calculated with kilo bytes/second
 * Site should handle many simultaneous user requests, large input data from users, Simultaneous connection to DB, heavy load on specific pages etc.
 * This also can be done with Jmeter with specific test cases where we can prepare with large input data and JDBC test cases (i.e. connection to DB) on specific pages etc.

Firebug
Firebug is an essential browser-based web development tool for debugging, testing, and analyzing web pages. It has a powerful set of utilities to help you understand and dissect what’s going on. One of the many notable features is the Net (network”) tab where you can inspect HTML, CSS, XHR, JS components.

We have used for the User Interface (UI) screen testing part with the response times obtained using the inbuilt add-on tool of FireFox Browser the “Firebug” which gives us the Net Response time which includes the time spent while request/response processing of a web page in these areas viz. HTML,CSS,JS,Images,Flash. Along with this we can get the Console time (Query time) also to know the query time once place by request.

Sometimes for some drop down fields in a search criteria section of different model applications like Securities, Positions, Customers the value retrieved multiple times. Please refer to the sheet with Response times (using Firebug tool) and Response times (which are taken manually)