Explore topic-wise InterviewSolutions in .

The bug that MAINLY comes in web testing are COSMETIC bugs on web pages , field VALIDATION related bugs and also the bugs related to scalability ,throughput and RESPONSE time for web pages. During the WEBSITE application testing, bug related to the link broken also comes.

The bug that mainly comes in web testing are cosmetic bugs on web pages , field validation related bugs and also the bugs related to scalability ,throughput and response time for web pages. During the website application testing, bug related to the link broken also comes.

client/server APPLICATION is a 2-tier application where as WEB application is an n-tier application.

client/server application is a 2-tier application where as web application is an n-tier application.

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.

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.

Authentication is the process by which the SYSTEM identifies the user. The aim is to ensure that the user is actually a user who claims to be. There are different types of authentication, which can be used as password-based authentication, authentication based devices, etc. On the other hand, the authorization is the process after the authentication process. In this process the system to decide whether a PARTICULAR task can be PERFORMED by the user, does the necessary PERMISSIONS, etc.

Authentication is the process by which the system identifies the user. The aim is to ensure that the user is actually a user who claims to be. There are different types of authentication, which can be used as password-based authentication, authentication based devices, etc. On the other hand, the authorization is the process after the authentication process. In this process the system to decide whether a particular task can be performed by the user, does the necessary permissions, etc.

The test CASE format may vary DEPENDING on whether the site is a static website or dynamic website. The static website will have the front of the test CASES, navigation. On the other hand, if the site is a dynamic web site, then test cases are divided into front end test cases, again the FINAL test cases, the field validation test cases, case base test DATA, test cases, security, etc.

The test case format may vary depending on whether the site is a static website or dynamic website. The static website will have the front of the test cases, navigation. On the other hand, if the site is a dynamic web site, then test cases are divided into front end test cases, again the final test cases, the field validation test cases, case base test data, test cases, security, etc.

Some of the HTTP response OBJECTS are WRITING, CLEANING, counting, etc. HTTP response SUBCLASSES are HttpResponseRedirect, HttpResponsePermanentRedirect, HttpResponseBadRequest, HttpResponseNotFound, etc.

Some of the HTTP response objects are writing, cleaning, counting, etc. HTTP response subclasses are HttpResponseRedirect, HttpResponsePermanentRedirect, HttpResponseBadRequest, HttpResponseNotFound, etc.

USABILITY testing is in fact an important part of the test site. In usability testing, it checks if the website is EASY to USE. Is it possible that the USER can move easily within the website. Is there any ambiguity in the website, which can make the user experience.

Usability testing is in fact an important part of the test site. In usability testing, it checks if the website is easy to use. Is it possible that the user can move easily within the website. Is there any ambiguity in the website, which can make the user experience.

The most important factor to consider is the hardware PLATFORM, while some may USE the Mac platform, some may use Linux, while others can use the Microsoft. The next is the browsers and their versions in the box. ALONG with the browser versions, different plug-ins must also be considered. The resolution also monitor color depth and SIZE of the text are some of the other CONFIGURATIONS.

The most important factor to consider is the hardware platform, while some may use the Mac platform, some may use Linux, while others can use the Microsoft. The next is the browsers and their versions in the box. Along with the browser versions, different plug-ins must also be considered. The resolution also monitor color depth and size of the text are some of the other configurations.

The commonly USED browsers are MOZILLA Firefox, GOOGLE Chrome, Internet Explorer and Opera. Therefore, a Web application must be TESTED in these browsers as WELL.

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

Static web PAGES only give information to the USER and the user does not have any interaction with the website. On the other hand, DYNAMIC Web sites are those where the user communicates with the SYSTEM and they are required information. In providing the required information, you may be able to retrieve the information you are looking for.

Static web pages only give information to the user and the user does not have any interaction with the website. On the other hand, dynamic Web sites are those where the user communicates with the system and they are required information. In providing the required information, you may be able to retrieve the information you are looking for.

The most common problem encountered during TESTING NETWORK is the server problem. The server may be down or may be subject to maintenance. The next problem, which is often found in testing SITE is a DATABASE problem, where the connection with the broken base. In some cases there may be hardware compatibility issues when you are testing a Web application.

The most common problem encountered during testing network is the server problem. The server may be down or may be subject to maintenance. The next problem, which is often found in testing site is a database problem, where the connection with the broken base. In some cases there may be hardware compatibility issues when you are testing a Web application.

No, there is no CHANGES on WEB PAGES. no CHANCE of VALIDATION.

No, there is no changes on web pages. no chance of validation.

CLIENT Server testing is 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 you 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.

Client Server testing is 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 you 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.

• Without Using GUI MAP Editor, We can Recognize the Application in WinRunner by RAPID TEST Script Wizard, but it is also recognize only Client server application, not Web BASED application.
• This can be ACHIEVED by using Descriptive programming but not with rapid script wizard.

NON STANDARD COLORS, frames, tables ETC.

Non standard colors, frames, tables etc.

• invoke_application COMMAND used to launch APPLICATION in WR.
• Invoke command we will USE to invoke a application in winrunner. invoke_aplication(PATH)

Testing the application with MULTIPLE BROWSERS (ie IE,Netscape navigator, Mozilla Firefox ETC)is CALLED browser COMPATIBILITY testing.

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

The first thing you need is to go through the specification and without USING the specification you are just PLAYING with the application. So specification is the main interface to the for any software to be tested.
First Do The GUI TESTING after finishing that we can go for Functionality Testing.

The first thing you need is to go through the specification and without using the specification you are just playing with the application. So specification is the main interface to the for any software to be tested.
First Do The GUI testing after finishing that we can go for Functionality Testing.

Through Volume testing it is possible. i.e., An application tries to retrieve large AMOUNT of data that require large temporary buffer area. If the data exceed the buffer area the situation of MEMORY LEAKAGE will occur and query will fail without returning any result as sorting didn’t got finished as buffer exceeds the limit.
We need to know the memory SIZE before the test EXECUTION and after test execution by using memory related API functions or MFC functions.

Through Volume testing it is possible. i.e., An application tries to retrieve large amount of data that require large temporary buffer area. If the data exceed the buffer area the situation of memory leakage will occur and query will fail without returning any result as sorting didn’t got finished as buffer exceeds the limit.
We need to know the memory size before the test execution and after test execution by using memory related API functions or MFC functions.

CLIENT SERVER Testing:
In client server testing test engineer are conduct the following testing’s:-

1. Behaviour testing(GUI TESTING)
2. INPUT domain testing
3. Error Handling testing
4. Backend testing.

Web Testing:
In Web testing test engineer are conduct the following testings:-

1. Behaviour Testing
2. Static web testing
3. Input domain testing
4. Backend testing.

Client Server Testing:
In client server testing test engineer are conduct the following testing’s:-

Web Testing:
In Web testing test engineer are conduct the following testings:-

Hardware PLATFORM (PC, Mac), Browser SOFTWARE and version, Browser Plug-Ins, Browser settings options, Video resolution and Color Depth, text size.

Hardware platform (PC, Mac), Browser software and version, Browser Plug-Ins, Browser settings options, Video resolution and Color Depth, text size.

• In CASE of web based testing we have test web browser and pages but 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.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 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.

GLYPH is the PICTURE of the CHARACTER.

Glyph is the picture of the character.

• As a Tester you should test GUI of the website, test whether the PAGE layout and design elements are consistent throughout the site, Whether all the links provided in the website are WORKING PROPERLY, What are the expected loads on the server performance of the website (CHECK for webserver response time and database query time)under heavy loads.
• As a Test Engineer you should also test the FUNCTIONALITY of each and every object existing in the web page while testing a web application.

• The bug that mainly comes in WEB testing are cosmetic bugs on web PAGES , field validation related bugs and also the bugs related to scalability ,throughput and response TIME for web pages.
• During the website application testing, bug related to the LINK broken also comes.

• Denial of Service (DoS) attack, buffer overflow.
• 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.

• Basically 3-tier ARCHITECTURE is for windows based application. Whereas N-tier architecture is for web-based applications. So, We should do the testing related to web-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.

1. SERVER PROBLEMS(ie server down or under maintenance).
2. HARDWARE problem.
3. DataBase problem.

Web SERVER MONITORS, database server monitors, NETWORK monitors are used to test the PERFORMANCE of the web application.

Web server monitors, database server monitors, network monitors are used to test the performance of the web application.

START ->Run ->TYPE Regedit then GOTO ->HKLocalMachine->Software->Mercury Interactive-> QTP->LOGGER->Media->Log.

Start ->Run ->type Regedit then goto ->HKLocalMachine->Software->Mercury Interactive-> QTP->Logger->Media->Log.

In N tier ARCHITECTURE, load testing, BROWSER testing, compatible testing and FUNCTIONAL testing are mandatory factor.

In N tier architecture, load testing, browser testing, compatible testing and functional testing are mandatory factor.

In the WEB TESTING the main problems with SERVER security the security testing PLAYS important ROLE.

In the web testing the main problems with SERVER security the security testing plays important role.

Microsoft INTERNET Explorer displays the LOCK icon in the lower-right of the browser WINDOW Many SSL Certificate vendors (Verisign, GeoTrust, etc.) ALSO provide a "site seal" to the OWNERS of these web sites.

Microsoft Internet Explorer displays the lock icon in the lower-right of the browser window Many SSL Certificate vendors (Verisign, GeoTrust, etc.) also provide a "site seal" to the owners of these web sites.

Web application:

• A web application is a database disc.
• Any application which resides on a server, but meant for use by humans, which uses web pages as the presentation LAYER. All USER interactivity (the GUI) is done through web pages, but all data is stored and (MOSTLY) manipulated on the server.

Web SERVICE:

• A web service is a online service, as in Verizon online service.
• server-based application (as above) which may be accessed over the web via HTTP, but is meant PRIMARILY for interaction with other programs. Thus, it will have a clearly-defined API which consists of providing responses to HTTP GET and POST requests made by a remote application.

Web application:

Web service:

This is a SIMPLE test method that tests the HelloWorld() WEB method of a Web service:

This is a simple test method that tests the HelloWorld() Web method of a Web service:

This is the process for testing a Web service that runs on your local computer but not in IIS:

1. CREATE the Web service on the local file SYSTEM.
2. Generate unit tests against the Web service in the standard way for generating unit tests.
3. Add the AspNetDevelopmentServerAttribute attribute to the unit test. The arguments for this attribute class point to the site of the Web service and NAME the server.
4. Within the unit test, add a CALL to the TryUrlRedirection method to point the Web service OBJECT to the correct server. Verify that it returns true, and use and Assert statement to fail the test if the redirection fails.
5. Call the Web service or exercise it in any other way that you feel is necessary to test it thoroughly.

This is the process for testing a Web service that runs on your local computer but not in IIS:

You can test Web services by calling Web methods from unit tests. The following LIST describes two ways to test Web services with unit tests:

• The Web service runs on an active Web server. There are no special REQUIREMENTS for TESTING a Web service that runs on a LOCAL or a remote Web server, such as IIS. To do this, add a Web reference and then CALL the Web methods of the Web service from your unit tests just as they would call the methods of a program that is not a Web service.
• The Web service is not hosted in an active Web server. you can test a Web service that runs on your local computer and not in a Web server, such as IIS. To do this, you use an attribute provided by the Team System testing tools to start ASP.NET Development Server. This creates a temporary server at localhost that hosts the Web service that you are testing.

You can test Web services by calling Web methods from unit tests. The following list describes two ways to test Web services with unit tests: