Scribd
Upload
97 views5 pages

Automation Testing Interview Questions

While web applications are built on client-server architecture, there are key differences that impact testing approaches: 1. In client-server, clients and servers exist within a single protected environment, but the web is open to anyone globally, posing greater security risks. 2. Client-server clients are controlled and known, but web users are anonymous, allowing for more opportunities for tampering. 3. Client-server testing focuses more on platform/OS dependence and business logic, while web testing emphasizes security, scalability across browsers, and performance with thousands of users.

Uploaded by

Ashutosh Mishra
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
97 views5 pages

Automation Testing Interview Questions

While web applications are built on client-server architecture, there are key differences that impact testing approaches: 1. In client-server, clients and servers exist within a single protected environment, but the web is open to anyone globally, posing greater security risks. 2. Client-server clients are controlled and known, but web users are anonymous, allowing for more opportunities for tampering. 3. Client-server testing focuses more on platform/OS dependence and business logic, while web testing emphasizes security, scalability across browsers, and performance with thousands of users.

Uploaded by

Ashutosh Mishra
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

Automation testing interview questions

this question asking in CSC compony totally they asking each and every point in winrunner,manual ..so i have to send this some questions this is first round and final round questions..... initially they asking my total all projects 1) what is compile module 2) how to retrive ur test data 3) what is diff between test script and compile module script 4) how to execute ur script with out GUI map 5) how to connect database in winrunner 6) what is whitebox testing technics 7) how to write testcases 10-16 numerical nos 8) what parameterization 9) what is test director 10) If i run script the objects r changing continuosly what will do? 11) what is project plan,Test plan 12) what is addins in winrunner? 13) what is selectors ? 14 )Automation architecture in ur compony? 15) what is treturn treexit? 16) how to connect datadriven wizard, which files r using? 17) in ur testing requirements r continuosly changing what will do? 18) why r u came to testing side? 19) Iam un educated how to say what is testing? 20) how to connect WR script to testdirector ? 21) what is SDLC Modes? 22) what is version control? 23) write test case watch? 24) Black box technics how to use in ur test case with example? 25) bug lifecycle? 26) what is consomotic ray testing? 27) what is bench mark? 28) what is test bed? 29) when will use updatemode: 30) what is data junction? 31) how to connect data to ODBC? 32) what is TRIGGERS? 33) what is Stored Procedures: 34) write query lessthan 10 sal? 35)what is outer join? 36) what is cursors?, how many types ? 37) u can send bug to dev ? but dev said that is not a bug what will do? 38) what is low pririty, high severity? 39) what is clent server, web sever? 40) have u using performace testing manually? 41) how to use tsl expection in ur script? they asking total scenario. 42)what is the use of IF_EXIT statement 43) what is diff between set_ window,_ set_window IF anybody wants Answers defenitely i can forward .... we will share our knowledge. ok

totally they asking each and every point in winrunner,manual ..so i have to send this some questions this is first round and final round questions..... initially they asking my total all projects 1) what is compile module 2) how to retrive ur test data 3) what is diff between test script and compile module script 4) how to execute ur script with out GUI map 5) how to connect database in winrunner 6) what is whitebox testing technics 7) how to write testcases 10-16 numerical nos 8) what parameterization 9) what is test director 10) If i run script the objects r changing continuosly what will do? 11) what is project plan,Test plan 12) what is addins in winrunner? 13) what is selectors ? 14 )Automation architecture in ur compony? 15) what is treturn treexit? 16) how to connect datadriven wizard, which files r using? 17) in ur testing requirements r continuosly changing what will do? 18) why r u came to testing side? 19) Iam un educated how to say what is testing? 20) how to connect WR script to testdirector ? 21) what is SDLC Modes? 22) what is version control? 23) write test case watch? 24) Black box technics how to use in ur test case with example? 25) bug lifecycle? 26) what is consomotic ray testing? 27) what is bench mark? 28) what is test bed? 29) when will use updatemode: 30) what is data junction? 31) how to connect data to ODBC? 32) what is TRIGGERS? 33) what is Stored Procedures: 34) write query lessthan 10 sal? 35)what is outer join? 36) what is cursors?, how many types ? 37) u can send bug to dev ? but dev said that is not a bug what will do? 38) what is low pririty, high severity? 39) what is clent server, web sever? 40) have u using performace testing manually? 41) how to use tsl expection in ur script? they asking total scenario. 42)what is the use of IF_EXIT statement 43) what is diff between set_ window,_ set_window

Web Application Security Testing


Web Application Security Testing Web application and Client-Server, are they same? This question is very common in software testing interviews, if you are part of some e-groups related to testing, you might have heard it many times from different people. There are numerous differences in Client-Server and Web application architecture. As a tester if you are testing Web applications, it is important to understand what Client-Server architecture is and how Web is different from traditional Client-Server architecture.Web is a specialized version of client server network, but it has got noticeable differences. In client server network, computing resources are conserved by delegating complex and time consuming task to powerful, expensive computers called server. These server machines are much more powerful in terms of large storage and computing power. They do all the computing and delivers result back to the machines called client over a communication path. Thus client-server architecture comprises of server, client and communication path connecting them. If you see at the lower level, client server architecture is not that simple. In order to connect two computers, you need network level protocol, you need proper software at client side and server side to send and receive data over network. You need to take care of data loss during transmission, bandwidth issues, dropped connectivity etc. Most of these issues are already addressed by protocols like TCP/IP, UDP, ARP etc. and developers face very little problem in implementing them. These protocols are backbone of the client server architecture.WWW was developed on top of existing client server architecture. It came into existence as a replacement for FTP and email as a mechanism of sharing files and data. New development in servers to handle more requests, new client software to connect and browse resources on server; new development like HTTP, HTML etc fueled the growth of Web. Main component of the Web architecture is the Web Server, which can serve request from any client. Initially, web started serving static content and soon it was explored for the possibility of doing much more than just static content.Even though Web is built on top of client server, there are noticeable differences. For example Web is a special case of client server architecture in which fat clients are used to communicate with the server using variety of protocols and standards like HTTP, HTML, XML, SOAP etc. In client server architecture, both client and server exist within the walls of a single company, thus operates in a protected environment. Clients in that case become the trusted user. Web is different, since client can connect server from anywhere thus not a single connection can be treated as trusted. Because client server is typically within a companys firewall, issues related to security are not as important as in Web applications. In client server architecture, clients are controlled as in who can access, how clients will communicate

and use servers resources etc. In Web, mostly anyone with a browser can connect to the Web. In client server architecture, every client is known; every request received by server will have information on who originated this request. In Web, users are anonymous thus pose a greater security risk. Web gives more opportunity to malicious users to tamper data at the client side as well as at the network level. Chances of data being tampered in the traditional client server architecture are much lesser as compare to Web. Number of clients that can be connected to the server is predictable and can be controlled in the traditional client server, but it can not be controlled in the Web. Clients are much more controlled in client-server. Which OS they will use, which platform they will run on, what browser will be used every thing can be controlled. In comparison to that, nothing can be controlled in Web. Because of the fact that both are different, testing applications in client server, or web will also be different. The main areas where the testing gets affected can be summarized as: Business Logic: Mostly in the cases of Client-Server client side business logic needs to be tested which is mostly not needed in for the web-based applications. Platform / OS Dependence: The web based applications are O/S independent; they just need to be tested on different browsers. The Client-Server applications depend upon the Platform/ OS used, which accentuate their testing on different Platforms and OS. Scalability: Web based Application have to be tested for performance against thousands of simultaneous users. This number will be considerably less for Client Server application Security: This forms an integral part of web based applications but it might be relaxed just a bit for Client Server applications. The reason for this relaxation is based on the fact that the in case of Client-server interaction is taking place mostly between the trusted/known sources which is not the case for web based applications. In a nutshell it can be stated that although web-based applications are a special case of client-server applications, yet their testing differ in many areas. All the areas identified above need to be addressed adequately in your testing, specially security since every client connected in the web environment is a potential threat to the system.Hope with this article you can appreciate the difference between clientserver architecture and web application architecture. Also, how testing applications based on these architecture is different from one another. Importance of security testing in the web application testing is also established in this article.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy