Automation Testing, Manual Testing, QTP/UFT 11 , QC/ALM 11 ,SAP TAO, Unix, Selenium, Oracle SQL, Shell Scripting and For Online Trinings to contact me : Cell:+91-8897972059 , Email Id : quicktestprotech@gmail.com

Monday, January 24, 2011

Web Application Testing-3

Validate your HTML/CSS:

 

If you are optimizing your site for Search engines then HTML/CSS validation is very important. Mainly validate the site for HTML syntax errors. Check if site is crawl able to different search engines.

 

Database testing:

 

Data consistency is very important in web application. Check for data integrity and errors while you edit, delete, modify the forms or do any DB related functionality. Check if all the database queries are executing correctly, data is retrieved correctly and also updated correctly. More on database testing could be load on DB, we will address this in web load or performance testing below.

 

Usability Testing:

 

Test for navigation:


Navigation means how the user surfs the web pages, different controls like buttons, boxes or how user using the links on the pages to surf different pages.
Usability testing includes:
Web site should be easy to use. Instructions should be provided clearly. Check if the provided instructions are correct means whether they satisfy purpose. Main menu should be provided on each page. It should be consistent.

 

Content checking:

 

Content should be logical and easy to understand. Check for spelling errors. Use of dark colors annoys users and should not be used in site theme. You can follow some standards that are used for web page and content building. These are common accepted standards like as I mentioned above about annoying colors, fonts, frames etc.
Content should be meaningful. All the anchor text links should be working properly. Images should be placed properly with proper sizes.
These are some basic standards that should be followed in web development. Your task is to validate all for UI testing

 

Other user information for user help:

 

Like search option, sitemap, help files etc. Sitemap should be present with all the links in web sites with proper tree view of navigation. Check for all links on the sitemap.
“Search in the site” option will help users to find content pages they are looking for easily and quickly. These are all optional items and if present should be validated.

Interface Testing:

 

The main interfaces are:
Web server and application server interface
Application server and Database server interface.
Check if all the interactions between these servers are executed properly. Errors are handled properly. If database or web server returns any error message for any query by application server then application server should catch and display these error messages appropriately to users. Check what happens if user interrupts any transaction in-between? Check what happens if connection to web server is reset in between?

 

Compatibility Testing:

 

Compatibility of your web site is very important testing aspect. See which compatibility test to be executed:
§         Browser compatibility
§         Operating system compatibility
§         Mobile browsing
Printing options


Browser compatibility:

 

In my web-testing career I have experienced this as most influencing part on web site testing.
Some applications are very dependent on browsers. Different browsers have different configurations and settings that your web page should be compatible with. Your web site coding should be cross browser platform compatible. If you are using java scripts or
AJAX calls for UI functionality, performing security checks or validations then give more stress on browser compatibility testing of your web application.
Test web application on different browsers like Internet explorer, Firefox, Netscape navigator, AOL, Safari, Opera browsers with different versions.

 

OS compatibility:

 

Some functionality in your web application is may not be compatible with all operating systems. All new technologies used in web development like graphics designs, interface calls like different API’s may not be available in all Operating Systems.
Test your web application on different operating systems like Windows, Unix, MAC, Linux, Solaris with different OS flavors.

 

Mobile browsing:

 

This is new technology age. So in future Mobile browsing will rock. Test your web pages on mobile browsers. Compatibility issues may be there on mobile.


Printing options:

 

If you are giving page-printing options then make sure fonts, page alignment, page graphics getting printed properly. Pages should be fit to paper size or as per the size mentioned in printing option.

 

Performance testing:

 

Web application should sustain to heavy load. Web performance testing should include:
Web Load Testing
Web Stress Testing
Test application performance on different internet connection speed.
In web load testing test if many users are accessing or requesting the same page. Can system sustain in peak load times? Site should handle many simultaneous user requests, large input data from users, Simultaneous connection to DB, heavy load on specific pages etc.

Stress testing:

Generally stress means stretching the system beyond its specification limits. Web stress testing is performed to break the site by giving stress and checked how system reacts to stress and how system recovers from crashes. Stress is generally given on input fields, login and sign up areas.
In web performance testing web site functionality on different operating systems, different hardware platforms is checked for software, hardware memory leakage errors,

Security Testing:

Following are some tests for web security testing:
  • Test by pasting internal URL directly into browser address bar without login. Internal pages should not open.
  • If you are logged in using username and password and browsing internal pages then try changing URL options directly. I.e. If you are checking some publisher site statistics with publisher site ID= 123. Try directly changing the URL site ID parameter to different site ID which is not related to log in user. Access should deny for this user to view others stats.
  • Try some invalid inputs in input fields like login username, password and input text boxes. Check the system reaction on all invalid inputs.
  • Web directories or files should not be accessible directly unless given download option.
  • Test the CAPTCHA for automates scripts logins.
  • Test if SSL is used for security measures. If used proper message should get displayed when user switch from non-secure http:// pages to secure https:// pages and vice versa.
  • All transactions, error messages, security breach attempts should get logged in log files somewhere on web server.
               
Web Testing is an essential topic now a days
 

Web Application Testing-2

  – for Server side Validations
         
§          HTML (Hyper Text Markup Language) – for displaying web pages
§          XML (Extensible Markup Language) –for Transporting the Data
§         Java Script – for Client Side Validations
§         VB Script
§           IIS, Apache, Tomcat, Pramathi – as Web servers
§           JBoss, WebLogic, WebSpeare, COM+ - as Application Servers
§          Java, C#.NET, VB.NET, VC++.NET for Components development
§          SQL Server, Oracle, MySQL  as Database Servers
§         HTTP, SOAP – as Protocols



Functionality Testing:


Test for - all the links in web pages, database connection, forms used in the web pages for submitting or getting information from user, Cookie testing.

Check all the links:

 

§         Test the outgoing links from all the pages from specific domain under test.
§         Test all internal links.
§         Test links jumping on the same pages.
§         Test links used to send the email to admin or other users from web pages.
§         Test to check if there are any orphan pages.
§         Lastly in link checking, check for broken links in all above-mentioned links.

 

Test forms in all pages:

 

Forms are the integral part of any web site. Forms are used to get information from users and to keep interaction with them. So what should be checked on these forms?
§         First check all the validations on each field.
§         Check for the default values of fields.
§         Wrong inputs to the fields in the forms.
§         Options to create forms if any, form delete, view or modify the forms.

 

Cookies testing:

 

Cookies are small files stored on user machine. These are basically used to maintain the session mainly login sessions. Test the application by enabling or disabling the cookies in your browser options. Test if the cookies are encrypted before writing to user machine. If you are testing the session cookies (i.e. cookies expire after the sessions ends) check for login sessions and user stats after session end. Check effect on application security by deleting the cookies

Web Application Testing-1

Web Applications Testing

I) Overview:


Now a days Web Applications are getting more popular in the IT Industry, having so many advantages like supporting more clients, no client side installation and accessing from any ware etc…

 

Types of Web Application

 We can categorize web applications in two ways

 

a)    Business Classification

 

1)     Web Sites (They provide information about Organizations or Industries or persons)

2)    Web Portals (They are Business gateways, ex: Online Shopping sites, Job portals etc.)

3)     Web Applications (They are Service providers (both Free and Paid), apart from information) Ex: Net Banking Applications, Insurance Applications etc…)

 

b)    Technical Classification

1)     Intranet Applications (They are private applications, uses local area network (LAN))

2)     Internet Applications (They are Public applications, uses Wide area network (WAN)

3)     Extranet Applications (They also Private applications over Internet (WAN))

 

Browser:


It is a Software Application, which retrieves, and Presents information in text, image and voice like different file formats.

The browser is the viewer of a Web Site and there are so many different browsers and browser options that a well-done Web Site is probably designed to look good on as many browsers as possible.

Popular Browsers:
  • Internet Explorer
  • Mozilla Firefox
  • Google Chrome
  • Safari
  • Opera
  • Etc…

Web Application Testing

Quality Center 10.0 Certification Questions

1. What attachment types are allowed in QC?
  • Files, URL, Snapshot, System Information, Clipboard
  • Files, URL, Snapshot, Clipboard
  • Files, Snapshot, System Information, Clipboard
  • Files, URL, Snapshot, System Information, Clipboard, Microsoft Office
  • Files, URL, Bitmap Capture, System Information, Clipboard


2. What requirement type can a folder be a child of?
  • Any Requirement Type
  • Folder only
  • Business Folder
  • Functional Requirement
  • Group

3. When trying to run a test set with manual & automated tests in it using the automated runner an error occurs with the manual tests, what is the most common cause?
  • The automated tests have to come first in the execution flow
  • The Test has no steps in it
  • You cannot use the automated runner to run both manual and automated tests
  • The Test does not exist
  • The Responsible Tester field has not been completed

4. For the Releases module to show linked defects on the Quality graphs, how must a defect be linked?
  • Linked to requirements
  • Directly to the Release or Cycle
  • Linked to requirements that are linked to Releases or Cycles
  • Linked to any entity
  • To Tests that are linked to Requirements that are linked to Releases or Cycles

5. How many memo fields can you add to a module?
  • 1
  • 99
  • 9
  • 5
  • unlimited

6. How does QC connect to the database - what protocol is used?
  • The Database client protocol
  • JDBC
  • http
  • Microsoft JET
  • ODBC

7. What is the maximum default attachment size for mail?
  • 2 MB
  • 3 MB
  • 5 MB
  • 6 MB
  • 1 MB

8. What Databases does QC support?
  • MSDE, Microsoft SQL Server, Oracle
  • Microsoft SQL Server, Oracle
  • MSDE, Microsoft SQL Server, Oracle, Sybase
  • Access, MSDE, Microsoft SQL Server, Oracle
  • Access, MSDE, Microsoft SQL Server, Oracle, Sybase

9. What is used to check that QC has been installed properly?
  • QC Install Checker
  • Quality Center Checker
  • QC Install Inspector
  • QC Install Check
  • Quality Center Check Tool

10. What web servers does QC support?
  • Apache, JBoss, Websphere Xitami
  • Microsoft IIS Only
  • Microsoft IIS, JBoss Only
  • JBoss Only
  • Microsoft IIS, Apache, JBoss, Websphere

11. What platforms does the QC application support?
  • Windows Only
  • Windows & Linux Only
  • Windows, Linux, Solaris
  • Windows, Linux, Solaris, OS2
  • Unix Only

12. What is the QC application file called?
  • QC
  • QualityCenter
  • qcbin
  • sabin
  • None of the above

13. What is the Site Admin application file called?
  • SA
  • SiteAdmin
  • qcbin
  • sabin
  • None of the above

14. How do you change the name of the defects module within one particular project?
 You can't
  • By adding a particular record in the DATACONST Table for that project
  • Add the REPLACE_TITLE Site Parameter
  • Change the BUGS Table for that project
  • Change the REPLACE_TITLE Site Parameter

15. How can you change the name of any of the modules for all projects?
  • You can't
  • By adding the REPLACE_TITLE record in the DATACONST Table for that project
  • Add the REPLACE_TITLE Site Parameter
  • Change the BUGS Table for that project
  • Change the REPLACE_TITLE Site Parameter

16. What is the default timeout on the server for user inactivity?
  • 20 minutes
  • 2 hours
  • 10 minutes
  • There is no limit
  • 10 hours

17. What is the default mail interval setting?
  • 10 minutes
  • 1 minute
  • 1 hour
  • immediately
  • 10 hours

18. To use a System Test in QC, what needs to be installed first?
  • The QC Connectivity Add-in on the machine where the test is to be run
  • The QC for QTP Add-in
  • You do not need to install anything
  • The System Test Remote Agent Add-in and the QC Connectivity Add-in on the machine where the test is to be run
  • The QTP Add-in

19. How many custom fields can you create per module in QC?
  • 10
  • 999
  • 99
  • 50
  • There is no limit

20. Where can you import users from within site admin?
  • LDAP, Windows Domain Servers
  • LDAP
  • Windows Domains
  • You cant inport users
  • Windows Directory Services

21. What value do you set the user timeout to in the Server Parameters, so users will never timeout when inactive?
  • 0
  • 999
  • -1
  • NULL
  • 1

22. What are the 4 views called in the requirements module?
  • Tree, Details, Grid, Coverage Analysis
  • Tree, Details, Tab, Coverage Analysis
  • Folder, Details, Grid, Coverage Analysis
  • Tree, Details, Grid, Graph
  • Tree, Information, Grid, Coverage Analysis

23. How many default user groups are there in QC & what are they?
  • TDAdmin, Developer, QA Tester
  • TDAdmin, Viewer
  • Admin, Developer, Project Manager, QA Tester, Viewer
  • TDAdmin, Developer, QA Tester, Viewer
  • TDAdmin, Developer, Project Manager, QA Tester, Viewer

24. What Module Access permission can you assign to Groups?
  • Requirements Only or all of the modules (full access)
  • You choose which modules out of any of them you would like to assign to a group
  • Defects Only, or all modules (full access)
  • You cant do this
  • Requirements Only, Defects Only or all of the modules (full access)

25. Which Entity is a defect directly linked to by default if a defect was raised during a manual test run?
  • Test
  • Requirement if the Test is linked to a requirement
  • Test Run
  • Test Step
  • Test Set

Loading...