What are the typical problems in web testing?

1:server problems(ie server down or under maintenance)

2:HardWare problem

3:DataBase problem

1. Functionality problems
2. UI related problems
3. Database related problems
4. OS compatibility problems
5. Browser compatibility problems
6. Security related problems
7. Load related problem.
and also many more

2 .What are the important test scenarios for testing a web site?

As a Test Engineer you have to identify Test Scenarios in the light of Test Plan. First of all, You have to assume that GUI
objects and elements of a website together is One Test Scenario. Then, U have to check all the links and buttons. Go for
Checking that all forms are working properly or not. Prepare Test Scenarios of the forms of a webpage.We can identify 4
different types of Test Scenarios of a form 1)Check the form with valid data in all the fields 2) Check the form with invalid
data which violate the validations of fields in the form 3) check the form by leaving some mandatory fields in the form 4)
Check the form with existing record details

As a tester you should perform or consider below mentioned test scenario for web testing-
1.Functionality testing
2.Performance Testing
-Load and Stress testing
3.Security Testing
4.Usability Testing
5.Compatibility Testing
6.Interface Testing

3 . In n tier Architecture What are the factors should be considered for testing?

In 3 tier architecture there are 3 layers in the architecture. They are 1) Application(Presentation) layer 2)Business Logic
Layer and 3)Data layer

In n tier architecture, Data layer is divided into 2 layers i.e Data access and Database.

In n tier architecture, Data access layer and Database layer may or may not reside on the same location.keeping that into
consideration we have to prepare Test strategy and Test Approach.

4. What bugs are mainly come in webtesting what severity and priority we are giving

Mainly there are following bugs which occurs during web-testing.

GUI related bugs: Low priority(Depend on website type either it is for advertisement or other),
Functionality related bugs: High priority
Validation on fields: Medium priority.
URL security breaking bug:High priority.

5 .WRITE TEST CASES FOR URL(ADDRESS) TESTING?

Test Objective -- To Verify the URL Address

Test Procedure/Steps -- 1. Open Internet Explorer. > 2. Enter valid URL in address box. > 3. press Enter.
Expected Result -- URL should be open properly.

Actual Result -- URL Open properly.

Comment -- If any
6. What types of web testing security problem?
Pasting internal url directly into browser address bar without login.
*Check reactions for invalid inputs for login id and password
*User should not view the other stats.
Web testing security problem:
1.Directly changing URL and u can get the information of admin side.
2.Type wrong URL,it should show,the URL is invalid or whatever.

7. What is Glyphs?
Glyph is the picture of the character.

8. What is the difference of approach for Testing Client/server and web appications?

In case of web based testing we have test web browser and pagesbut in case of client server testing we test icon of
application that is main difference

Web based Application follows the client Server Architecture.Since in web based, we have a client i.e. Browser itself and
the server is at some remote location.<br>There is no such difference between client server and web based but it can be
said that applications that are based on the client server architecture are different. Eg. Window based application - in them
we need to install the application at each of the client sor user interface server being common for all the clients. but in web
based application for user interface there is no need for any installation. The browser is the client itself

8. What happens in a web application when you enter all the data and click on submit button suddenly the connection
goes off?where the data will go pls answer immdiately ?
If the data reaches the web server by the time of disconnection,the system will persist the data in the database .If the
connection fails before reaching the server ,the data won't be persisted and data will be lost.

9. What are possible configurations that could affect the testing strategy of any web site?
Hardware platform (PC, Mac), Browser software and version, Browser Plug-Ins, Browser settings options, Video resolution
and Colour Depth, text size.

10 . What are the important scenarios for testing emails? how do you test emails? which tool is best for testing email?

Test the email is not a very easy scenario.

We can categorised the different part on which tester may perform the testing.

1) for incoming mail with attachment

2) for outgoing mail with attachment

3) mail failure

4) Other properties like ;Delete,Edit etc.........

1) for incoming mail with attachment :--

1. Chek the proper incoming address or id.

2. Chek Not only the One address(TO),but also for

the Ccc and Bcc Addresses.

3. Check the max and min limit for number of

addresses.

4. Check if address has some error like @ or . is

missing .

5. Check if address has more than 1 @ sign .

6. Check if . has arrives less than 1 or more than

standard time (as per registered)

7. Check if address has arrives more than 1 time.

8. Check address only have @, ., _ and - special

symbols that are standard signs.

9. Check taht mail dose not have unnecessary

content with it self.

10. If there is/are any attachments then they open

properly.

11. The attachment size not exceeds the standard

size.

12. If there are more than 1 attachments then the

calculated size must be under the Standard size.

13. If email content have some images or some

different Flash pic must show properly.

14. Some time mail have some different extentions

file then it shows properly.

15. If the user read the mail ,then it should be

marked as readable.

other...........

2) for outgoing mail with attachment :--

1. Check the Address as we done prior.

2. Here we must check for the attachments.

3. For all the send pictures

4. Mail content should have the proper content.

3) mail failure:-- Check for the mail failure

4) Other properties like ;Delete,Edit etc.........

11 .How to Test the Cookies and Memory leakages? (i.e does the cookies expired or not and about memory leakage)?

Memory Leakages: By volume testing and stability/reliability testing

12 . What is your approach or how do you start Testing an Webapplication

1.Go through the test plan understand the test scenarios

2.Report all CSS issues then go for functional testing
3.Play around the web site
4.Make sure duplicated bugs not reported
5.Bug Regression

13 . During the passward field testing. What sould be the focus (give answer in one word)

1. password should be in encrypted form

2. the field can not be copied either by right clicking of the mouse or by ctrl+c option

1."Validation"
2."Mask"
3."Strength" (validated by characters and length as per standard)

14. How to do browser testing( create a standard script and run it for the different browser

The GUI architecture and events messaging differs from browser to borwser

like IE use Win32::OLE messaging and firefox must be using some GTK based messaging. So it is generally difficult to create
one standard script that runs on all browsers.

But tools like Winrunner, QTP must be using complex procedures inside them to handle different browsers.

to me, if my application supports different browsers like IE, firefox, opera, netscape i will try to do manual testing.

15. Name a few website mistakes that could cause configuration and compatibility bugs

Non standard colors, frames, tables etc.

1.By clicking on links it may show Fatal error

2.Unable to submit the orders
3.Forward and back navigation error pops up
4.Accepting invalid codes

1.Accepting HTML codes

2.When scalability changing ALIGNMENT is not in middle
3.Alignment is not good

16 . How to test Browser compatibility testing?

Testing the application with multiple browsers (ie IE,Netscape navigator,Mozilla Firefox etc)is called browser
compatibility testing

clink on to the verified file and just login through out the mails or unique with ur thouts
 test the application with different browser as well with different OS.

For window system test it with Most avalavle version of IE specially IE6 and IE7.
With Linux you can check it with firefor.
For mac chack with safari.......ect

Test the application in different hardware and software configuations and also the with different browsers

17 .What are the important test scenarios for testing a web site?

1.Usability testing
2.User interface testing
3. Functional testing under this
Links
Forms
Database
4. Compatibility testing
5.Security
7.Server Log files
8.Performance

18. From the testability point of view what is the difference between client/server
testing and web testing

Client Server testing is a three tier architecture and when testing has to be done on this
we need to consider all types of testing like the stress testing , data - volume testing,
load testing and performance testing.

When u are doing a normal web testing then you will be testing navigation testing, frame
testing, broken links or missing URL's and static text testing.

19 Difference between Desktop, Client server and Web testing

1. Describe some of the possible web page futures .

2. Question: What are possible configurations that could affect the testing strategy of
any web site?
Answer: Hardware platform (PC, Mac), Browser software and version, Browser Plug-
Ins, Browser settings options, Video resolution and Colour Depth, text size,
3. What is website usability testing ?
Google for more Usability software testing interview questions.
4. Why spell checker is not enough during testing spelling on web page?
5. Question: Name a few website mistakes that could cause configuration and
compatibility bugs.
Answer: Non standard colours, frames, tables etc.
6. Question: What the latest web technologies do you know?
Answer: RSS,
7. Question: Name some Alternative Browsers.
Answer: Opera, Mozilla
8. Describe some Caching Issues.
9. What HTML standard do you know?
10. What web specific types of testing do you know?
11. What is static and what is dynamic web page?
12. Question: Can the Netscape scripting host without plug-ins run Microsoft JScript on
the client side?
Answer: No
13. Question: What is Glyphs?
Answer: Glyph is the picture of the character.
14. What techniques will cause double-byte problems to show up?
15. What is Alt Key Input?
16. How will you decide when and what to test during performance testing?
17. Question: What types of web testing security problems do you know?
Answer:(Denial of Service (DoS) attack, buffer overflow)
18. Question: What types HTTP Response Codes do you know?
Answer: ( 2xx - success, 3xx - Redirection, 4xx - Client Error, 5xx - Server Error )
19. What errors can occur when the page loads?
20. What are the metrics what can be used during performance testing?
21. What HTML file extension can be used?
22. What is CSS stands for?
23. What are the differences between testing WEB application and testing client-sever
application?
24. Write test cases for Search Engine?
25. Difference between HTTP and HTTPS? Explain how the data is secured in HTTPS?
26. What does DNS contains?
27. What is the difference between authentication and authorization?
28. What type of security testing you performed?
29. What are the differences between GUI and Usability Testing
30. How to find that a page cached by Google?
Definition: cashed page is a snapshot of a web page collected during crawling.
To retrieve Google’s cached version of a page type:
cache:www.extremesoftwaretesting.com/InterviewQuestions/WebTesting.html and
click search
31. How to find the cookie details of the page displayed in IE?
Type in the URL: javascript:alert(document.cookie.split(';').join('\n'));

============================================================

32. Question: Please tell all you know about testing web services.
Answer:
There are multiple non-functional requirements expected from the web services:
33.  Performance
34.  Scalability
35.  Extensibility
36.  Reliability
Types of testing that applied to web services:
37.  Unit testing
38.  Functional testing of web services
39.  Integration testing of web services
 40.  Performance testing
The purpose of functional testing of a web service is to ensure that the expected
business functionality is provided correctly by the web service.
Integration testing of web services
Web services are integrated with multiple components such as brokers or service
coordinators.
Web services Integration Testing. The intent of Web services Integration Testing is to
expose faults in the interactions between web service and other software components,
modules and functions. To verify that integrations do not break the system.
Performance testing of web services
As defined on Wikipedia
(http://en.wikipedia.org/wiki/Software_performance_testing), performance testing is
in general testing that determines how a system performs in terms of responsiveness
and stability under a particular work load.
Web service performance test planning includes:
41.  Identify the expected performance requirements
42.  Analyze web service real world working scenarios
43.  Identify message volume, size, and transmission rate
This includes load and stress testing the web service as well as measuring the
performance under various conditions. Apache JMeter http://jmeter.apache.org/ is a
good open source testing tool which can be used for performance testing of web
services.

Web Testing: Complete guide on testing

web applications
Points to be considered while testing web applications. Let’s have first web testing checklist.

1) Functionality Testing
2) Usability testing
3) Interface testing
4) Compatibility testing
5) Performance testing
6) Security testing

1) 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.

Let’s take example of the search engine project currently I am working on, In this project we
have advertiser and affiliate signup steps. Each sign up step is different but dependent on
other steps. So sign up flow should get executed correctly. There are different field
validations like email Ids, User financial info validations. All these validations should get
checked in manual or automated web testing.

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. (I will soon write separate article on cookie testing)

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 crawlable 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.

2) 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.

3) 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?

4) 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.

5) 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,

6) Security Testing:
Following are some test cases 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 logged in user. Access should denied for this user to view others stats.
 Try some invalid inputs in input fields like login username, password, 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

How can a Web site be tested?

Points to be considered while testing a Web site:

Web sites are essentially client/server applications –

with web servers and ‘browser’ clients.

Consideration should be given to the interactions between html pages, TCP/IP

communications, Internet connections, firewalls, applications that run in web pages
(such as applets, javascript, plug-in applications), and applications that run on the server side
(such as cgi scripts, database interfaces, logging applications, dynamic page generators, asp,
etc.).

Additionally, there are a wide variety of servers and browsers, various versions of each, small
but sometimes significant differences between them, variations in connection speeds, rapidly
changing technologies, and multiple standards and protocols. The end result is that testing for
web sites can become a major ongoing effort.

Other considerations might include:

What are the expected loads on the server (e.g., number of hits per unit time?), and what kind
of performance is required under such loads (such as web server response time, database
query response times). What kinds of tools will be needed for performance testing (such as
web load testing tools, other tools already in house that can be adapted, web robot
downloading tools, etc.)?

Who is the target audience? What kind of browsers will they be using? What kind of
connection speeds will they by using? Are they intra- organization (thus with likely high
connection speeds and similar browsers) or Internet-wide (thus with a wide variety of
connection speeds and browser types)?
What kind of performance is expected on the client side (e.g., how fast should pages appear,
how fast should animations, applets, etc. load and run)?

Will down time for server and content maintenance/upgrades be allowed? how much?

What kinds of security (firewalls, encryptions, passwords, etc.) will be required and what is it
expected to do? How can it be tested?

How reliable are the site’s Internet connections required to be? And how does that affect
backup system or redundant connection requirements and testing?

What processes will be required to manage updates to the web site’s content, and

what are the requirements for maintaining, tracking, and controlling page content, graphics,
links, etc.?

Which HTML specification will be adhered to? How strictly? What variations will be
allowed for targeted browsers?

Will there be any standards or requirements for page appearance and/or graphics throughout a
site or parts of a site??

How will internal and external links be validated and updated? how often?
Can testing be done on the production system, or will a separate test system be required?
How are browser caching, variations in browser option settings, dial-up connection
variabilities, and real-world internet ‘traffic congestion’ problems to be accounted for in
testing?

How extensive or customized are the server logging and reporting requirements; are they
considered an integral part of the system and do they require testing?

How are cgi programs, applets, javascripts, ActiveX components, etc. to be maintained,
tracked, controlled, and tested?
Pages should be 3-5 screens max unless content is tightly focused on a single topic. If larger,
provide internal links within the page.

The page layouts and design elements should be consistent throughout a site, so that it’s clear
to the user that they’re still within a site.

Pages should be as browser-independent as possible, or pages should be provided or

generated based on the browser-type.

All pages should have links external to the page; there should be no dead-end pages.
The page owner, revision date, and a link to a contact person or organization should be
included on each page.
 Web Testing: Complete Guide To Your Web
Application Testing
In previous Software testing Class we have outlined the “Difference between Priority and
Severity?” In today’s class we will see more details on Web application testing. This
article will help you to learn basic of web testing. Before start testing web site it’s
very important to know about which all testing methods needs to cover.

Prior to see more details on web application testing, first let’s see the definition of the
Web Testing.

What is Web Testing?

“Web testing is the name given to Software Testing that focuses on testing the web
applications.” In Web-based application is completely tested before going production
environment. This could help to address the issues in web application before exposed to
public like the Functional issues, web application security, web services issues,
integrations issues, environment issues and its ability to handle traffic is checked. In this
stage of Web Testing making effort to find out the possible bugs in the system.

Web Application Testing Checklist:

Let see what all testing is to be carried out on in software web testing. The testing is
totally based on your web testing requirements but following is the standard checklist of
web testing:
 Web Testing
1. Functionality Testing:

In Functional testing we need check the each components are functioning as expected or
not, so it is also called as “Component Testing”. Functional testing is to testing the
functionality of the software application under test. Basically, it is to check the basic
functionality mentioned in the functional specification document. Also check whether
software application is meeting the user expectations. We can also say that checking the
behavior of the software application against test specification.

In this testing activities should include:

Link Testing:

Check for all broken links on your web pages & all links are working correctly. Along
with you can check the different links on you web pages:

 Internal links
 Outgoing links
 MailTo Links
 Anchor Links
 Web form testing:

In the web application testing the “Forms Testing” is the essential part of testing any
web site. The main purpose of Form is to get the information from user & store into the
database. And keep on interact with them. Below are the test cases which should be
considered while doing form testing:

 First thing to test in the form is the Validations on each form fields. Here two
types of Validation need to be consider – “Client side” & “Server side” validations.
 Check default values are being populated
 Check for all Mandatory fields. Check if a user not entered a required field
showing a mandatory error message.
 Add information using form & update information using form.
 Tab orders.
 Check for the default values of fields.
 Forms are optimally formatted for better readability
 In Negative testing enter invalid inputs to the forms fields.

Cookies testing:

Cookies are the small text file that gets saved the user’s system. These files are saved in
the desired location and used by the browsers to use the cookies. Basically used to
maintain the session mainly login sessions the Cookies are used. Instructive information
is recorded in the cookie (like Sessions) and that can be retrieved for the web pages.
User can able to enable or disable the Cookies in browser options. The basic test to
check if cookie is stored in the user’s machine in the encrypted format. (I am writing
separate article on Cookie Testing, post it soon)

So let’s see what should be tested in Cookies testing:

 Test the application by disabling the Cookies

 Test the application after corrupting the cookies.
 Check the behavior of application after removing the all the cookies for the
website you are testing.
 Check website writing cookies are working or not on different browser.
 Check if cookies for authenticated login are working or not.
 Check if behavior of application after deleting the cookies (sessions) by clearing
cache or after cookies expired
 Check if login to application after deleting the cookies (sessions)

Test HTML and CSS:

To optimize web site in the search engine then testing of HTML and CSS make important
role. In this testing check that different search engines can crawl your site without any
error. You should check for all Syntax Errors, Color Schemas in the readable, check for
Standard Compliance and the standards are followed like W3C, ISO, ECMA, IETF, WS-I,
OASIS

Test business workflow:

This would include:

 End to end testing of business scenarios/workflow which ensure that the

completeness of website testing.
 Testing of Positive as well as negative scenarios.
 2. Usability testing:

Now a day’s the Usability testing is playing an important role of any web application. This
testing is to be carried out by testers like you to ensure that cover all possible test cases
which targeted audience of the web application are doing regularly.

This would include –

Navigation testing of the web site:

 All possible options like Menus, Links or buttons on web pages should be visible &
accessible from all the web pages.
 Web pages navigation should be Easy to use
 Help instruction content should be clear & should satisfy the purpose.
 All options on header, footer & left/right navigation should be consistent
throughout the pages.

Content testing of the web site:

 No spelling or grammatical errors mistake in content throughout the page.

 Alt text should be present on Images
 No broken images
 Your task is to validate all for UI testing
 Follow some standard on content building on web page
 All content should be legible & easy to understand.
 Dark color infuriates the users, so avoid using dark colors in the theme.
 Proper size images should be placed on web page
 All the anchor text links should be working properly.

3. Compatibility testing.

In software application testing the Compatibility testing is the non-functional part of

testing. It is ensuring that how application’s working in the supported environments.
Customers are uses web application on different Operating systems, Browser
compatibility, computing capacity of Hardware Platform, Databases and Bandwidth
handling capacity of networking hardware. The Compatibility testing is to make sure that
“Is web application show correctly across different devices?”

This would include-

Browser Compatibility Test:

Web applications are rendering differently on different browsers. The objective of

browser compatibility testing is to ensure that no any errors on the different web
browsers while rendering the sites. In Browser Compatibility Testing you need to ensure
that your web application is being displayed properly on different browsers. Also check
AJAX, JavaScript and authentication are functioning correctly.

OS compatibility:

In new technology newer graphics designs are used & different APIs are used which may
not work on different Operating systems. Also on rendering of different objects like text
fields, buttons may display different on different Operating System. So testing of web
application should be carried out on different OS like Windows, MAC, Solaris, Unix, Linux
with different OS flavors.
 Mobile browsing:

In latest Mobi technology you also test out Mobile Browser Compatibility too. It may be
possible of Compatibility issues on Mobile browsers. So in the new Mobi technology age
you testing of web pages on mobile browsers should be carried out.

4. Database Testing:

Data reliability is key part in the Database testing. So for web application should be
thoroughly tested.

Testing activities would include-

 Check if queries are executed without any errors.

 Creating, updating or deleting data in database should maintain the data
integrity.
 More time should not take to execute the queries, if required tune the queries for
better performance.
 Check load on database while executing heavier queries & check the result.
 Collect data from database & represent on the web pages correctly.

5. Crowd Testing:

Crowd testing is when a large group of perfect strangers try your product then give you
phenomenally helpful feedback on usability, bugs and features.

To test the software application Crowd testing can be used. It not limited to web
applications, but for all kinds of applications including mobile application testing.
Crowdtesting is dependent on the quality of the crowd. Also it depends on a crowd that
is composed out of a large group of diver’s people. It used do system tests for
performance and usability testing. Simply this is complementary to ‘normal’ testing. The
mainly complicated job of crowd testing is determining a good enough crowd.

6. Interface Testing:

In the Interface testing mainly three areas should be covered: Web Server, Application
Server and Database Server. Ensure that all the communications between these all
servers should be carried out correctly. Verify that if connection between any servers is
reset or lost then what is happing. Check if any request interrupts in-between then how
application is responding. On returns of any error from web server or database server to
application server then error should be Errors are handled properly & display such errors
to the user.

 Web Server: Check if all web requests are accepting and not any requests are
denied or leakages.
 Application Server: Check if request is sending correctly to the any server &
displayed correctly. Check if errors are catch properly & displayed to admin user.
 Database Server: Check if database server is returns correct result on query
request.

Check if all three servers are connected to each & test request is processing correctly.
And any error in between then error should be displayed to user.
 7. Performance Testing:

Performance testing is to check the web application is working under the heavy load.
Performance testing is categorized into two parts:
Web Stress Testing, Web Load Testing

This would include-

 Check if response times of Website application under different speeds of

connections
 Check if site handles many simultaneous user requests at same time.
 Check if how your web application sustain under the peak loads
 Check if large input data from users.
 Check the behavior of web application if simultaneous connection to Database.
 Check if how the web site pulls through if crash occurs due to peak load.
 Check if optimization methods such as reduce load times by enabling cache on
browser client and server side, gzip compression etc
 Check if any hardware memory leakage errors

8. Security testing:

The security testing is carried out to ensure that is any information leakage in terms of
encrypting the data. In e-commerce website the Security testing is play an important
role. In this testing check if secure information is to check whether how to store
sensitive information such as credit cards etc.

Testing Activities will include-

 Check if unauthorized access to secure pages, if user changes from “https” to

“http” (secure to non-secure) in secure pages then proper message should be
display and vice versa.
 Check if accessing internal pages directly entering URLs in browser. If login is
required then user should redirected to login page or appropriate message should
be displayed.
 Most of the information related to transactions, error messages, login attempts
should be logged in log file.
 Check if restricted files are able to access for download.
 Check if internal Web directories or files are not accessible unless & until not
configured for download.
 Check if CAPTCHA is added & working properly for logins to prevents automates
logins attempts.
 Check if try to access others information by changing parameter in query string.
For example if you are editing the information & in URL you are seeing UserID =
123, try to change this parameter values & check if application is not providing
the other users information. It should display Access denied for this user to view
others users information.
 Check if sessions are got expired after pre-defined amount of time if user not
using session.
 Check if user not able to pass login page for invalid username/password
combination.
 Check if user is navigated to encrypted SSL pages for secure website.
 Web Testing Interview Questions with Answers

It is important that you are abreast with the latest trends and tools used in the software
testing industry, when you are appearing for the interview. You will have to ensure that you
keep your knowledge up-to-date, when you want to appear from an interview, as the
chances are high that your knowledge may become obsolete. It is important to note that the
software testing field is a volatile field and many changes continue to take place on a daily
basis. Before turning towardsquestions and answers, it is important that you know some
important manual testing questions and answers as well.

 What are the common problems faced in web testing?

The most common problem faced during web testing is the server problem. The server can
either be down or it can be under maintenance. The next problem, which is often faced in
web testing is database problem, where the connection to the database can be broken. In
some cases, there can be hardware compatibility problems, when one is testing a web
application.

 How are the static websites different than the dynamic websites?
Static websites only give out information to the user and the user does not have any sort of
interaction with the website. On the other hand, dynamic websites are the ones, where the
user communicates with the system and is asked for information. On providing the required
information, he may be able to retrieve the information he is looking for.

 Which are the common browsers, where a web application should be tested?
The browsers that are commonly used are Mozilla Firefox, Google Chrome, Internet Explorer
and Opera. Therefore, a web application must be tested on these browsers as well.

 While testing a website, which are the different configurations which will have to be
considered? These configurations may demand for change in strategy of the webpage.
The most important factor that needs consideration is the hardware platform, while some
may use the Mac platform, some may use Linux, while others may use Microsoft platform.
The next comes the browsers and their versions into the picture. Along with the browser
versions, the different Plug-Ins also have to be taken into consideration. The resolution of
the monitor also with color depth and text size are some of the other configurations.

 Is usability testing possible while testing a website?

Usability testing is indeed an important part of web testing. In usability testing, it is checked,
whether the website is user-friendly. Is it possible for the user to move around easily within
the webpage. Is there any sort of ambiguity on the webpage, which can hinder the user
experience.

 What is a proxy server?

A proxy server is a server, which behaves like an intermediary between the client and the
main server. Therefore, the requests onto the main server are first sent to the proxy server
from the client system, which are then forwarded to the main server. The response from the
main server is sent to the client through the proxy server itself. The request and/or the
response may be modified by the proxy server depending on the filtering rules of the server.

 Which are the HTTP Response Objects?

Some of the HTTP Response Objects are write, flush, tell, etc. The subclasses of HTTP
Response are HttpResponseRedirect, HttpResponsePermanentRedirect,
 HttpResponseBadRequest, HttpResponseNotFound, etc.

 Which are the different test case formats, that are a part of web testing?
The test case formats will vary depending on whether the website is a static website or a
dynamic website. The static website will have the front end test cases, navigation test cases.
On the other hand, if the website is a dynamic website, then the test cases will be broadly
divided under front end test cases, back end test cases, field validations test cases, database
test cases, security test cases, etc.

 Explain the difference between authentication and authorization during web testing?
Authentication is the process with which the system identifies the user. The goal is to ensure
that the user is indeed a user, who he claims to be. There are different types of
authentications, which can be used like password based authentication, device based
authentication, etc. On the other hand, authorization is the process after the authentication
process. In this process the system will decide whether a particular task can be performed by
the user, does he have the necessary permissions, etc.

 Which different test scenarios will you consider, when you are testing a website?
The first scenario to be tested is the GUI. The page layout and the design elements used on
the website have to be uniform throughout the website. The next part to be tested are the
different links provided inside the website. Along with the links, it will also have to be tested,
whether internal navigation is smooth and also check if it is complex. The next important
aspect to be checked, is the response time of the website. This will also have to checked,
when there is heavy load on the system.

Web Based Testing Interview Questions

• Which different scenarios will be used for testing emails?

• How will you test cookies? Whether the cookies have expired, are there cookies on the
system, etc.?
• How will you test the URL of a website?
• Can font and alignment testing be carried out manually on a webpage? How?
• How should performance testing be performed on a website?
• What is caching? What are the common problems seen in caching?
• Explain the different between HTTP and HTTPS?
• Which are the different Web Service Standards? Are the Web Service Standards supported
by W3C?
• How is the response time at the server end calculated?
• How is the architecture of the website identified?

==================================================

Interview Questions on Web Testing What is Web application

What is HTML?

HTML stands for Hyper Text Markup Language, it is for displaying web pages and other information. Basically it is data presenter in the web.

What is HTTP?

Hyper Text Transfer Protocol, the data transfer protocol used on the World Wide Web.

What is HTTPS?

HTTPS stands for Hypertext Transfer Protocol Secure is a widely-used communications protocol for secure communication over a computer network.

What is internet application?

Generally it is a public web application, uses Wide area network. It can be accessed from anywhere.

What is intranet application?

It is a private application, can be accessed within the Organization only. It uses Local /Private Network and Internet Protocol technology to share
information.

What is purpose of Java Script in the Web?

It is for performing client side validations.

What is Server side validation?

Validating, processing client requests and providing response from the Server.

What is the difference among Intranet, Internet and Extranet web applications?

Intranet: It is a private network(Within the Organization) uses LAN/MAN Technologies Internet: It is a Public network uses WAN
Technology Extranet: It also private network over Internet

What is the difference between desktop application testing and web testing?

Desktop testing is standalone testing. Desktop need not worry about number of user etc. Web testing is

related to client server. Web testing needs to have many testing’s like usability, GUI, and Load

Testing.

Which different test scenarios will you consider when you are testing a website?

The first scenario to be tested is the GUI. The page layout and the design elements used on the website have to be uniform throughout the website. The
next part to be tested is the different links provided inside the website. Along with the links, it will also have to be tested, whether internal navigation is
smooth and also check if it is complex. The next important aspect to be checked is the response time of the website. This will also have to checked, when
there is heavy load on the system.

Explain the difference between authentication and authorization during web testing?

Authentication is the process with which the system identifies the user. The goal is to ensure that the user is indeed a user,
who he claims to be. There are different types of authentications, which can be used like password based authentication, device based
authentication, etc. On the other hand, authorization is the process after the authentication process. In this process the
system will decide whether a particular task can be performed by the user, does he have the necessary permissions, etc?

Which are the different test case formats that are a part of web testing?

The test case formats will vary depending on whether the website is a static website or a dynamic website. The static website will have the front end test
cases, navigation test cases. On the other hand, if the website is a dynamic website, then the test cases will be broadly divided under front end test cases,
back end test cases, field validations test cases, database test cases, security test cases, etc.

Which are the HTTP Response Objects?

Some of the HTTP Response Objects are write, flush, tell, etc. The subclasses of HTTP Response are HttpResponseRedirect,
HttpResponsePermanentRedirect, HttpResponseBadRequest, HttpResponseNotFound, etc.
What is a proxy server?

A proxy server is a server, which behaves like an intermediary between the client and the main server. Therefore, the requests onto the main server are
first sent to the proxy server from the client system, which are then forwarded to the main server. The response from the main server is sent to the client
through the proxy server itself. The request and/or the response may be modified by the proxy server depending on the filtering rules of the
server.

Is usability testing possible while testing a website?

Usability testing is indeed an important part of web testing. In usability testing, it is checked, whether the website is user-friendly. Is it possible
for the user to move around easily within the webpage? Is there any sort of ambiguity on the webpage, which can hinder the user
experience?

While testing a website, which are the different configurations which will have to be considered these configurations may
demand for change in strategy of the webpage.

The most important factor that needs consideration is the hardware platform, while some may use the Mac platform, some may use Linux, while others
may use Microsoft platform. The next comes the browsers and their versions into the picture. Along with the browser versions, the
different Plug-Ins also have to be taken into consideration. The resolution of the monitor also with color depth and text size are some of the other
configurations.

Which are the common browsers, where a web application should be tested?

The browsers that are commonly used are Mozilla Firefox, Google Chrome, Internet Explorer and Opera. Therefore, a web application must be tested on
these browsers as well.

How are the static websites different than the dynamic websites?

Static websites only give out information to the user and the user does not have any sort of interaction with the website. On the other hand, dynamic
websites are the ones, where the user communicates with the system and is asked for information. On providing the required information, he may be
able to retrieve the information he is looking for.

What are the common problems faced in web testing?

The most common problem faced during web testing is the server problem. The server can either be down or it can be under maintenance. The next
problem, which is often faced in web testing is database

problem, where the connection to the database can be broken. In some cases, there can be hardware compatibility problems,
when one is testing a web application.

What is the purpose of VbScript in the Web?

It can be used for client side validations as well as Server side validations.

What is Web Services?

Web services are application components, communicate using open protocols and these can be used by other applications. XML is the basis for Web
services SOAP (Simple Object Access Protocol), UDDI (Universal Description, Discovery and Integration) and WSDL (Web Services Description Language)
are the Web services platform elements.

What the latest web technologies do you know?

Latest web technologies are: The main three web tracks: 1. Microsoft ASP.Net Track + SQL Server database engine (IDE: Expression Web, Visual Studio). 2.
Oracle Java Track + Oracle database engine (IDE: NetBeans, Eclipse). 3. PHP Track + MySQL database engine (IDE: Zend Studio, DreamWeaver). There are
many new concepts and enhanced methodologies like Ajax, JQuery, JSON, and so on.

What types HTTP Response Codes do you know?

Types of HTTP Response Codes are: 2xx

success, 3xx
–

Redirection, 4xx

Client Error, 5xx

Server Error

What types of web testing security problems do you know?

Types of web testing security problems are: Denial of Service (DoS) attack, buffer overflow etc…

==================================================================================================