What is the difference between client-server testing and web based testing and w

hat are things that we need to test in such applications? Ans: Projects are broa
dly divided into two types of:
• •
2 tier applications 3 tier applications
CLIENT / SERVER TESTING This type of testing usually done for 2 tier application
s (usually developed for LAN) Here we will be having front-end and backend. The
application launched on front-end will be having forms and reports which will be
monitoring and manipulating data E.g: applications developed in VB, VC++, Core
Java, C, C++, D2K, PowerBuilder etc., The backend for these applications would b
e MS Access, SQL Server, Oracle, Sybase, Mysql, Quadbase The tests performed on
these types of applications would be - User interface testing - Manual support t
esting - Functionality testing - Compatibility testing & configuration testing -
Intersystem testing WEB TESTING This is done for 3 tier applications (developed
for Internet / intranet / xtranet) Here we will be having Browser, web server a
nd DB server. The applications accessible in browser would be developed in HTML,
DHTML, XML, JavaScript etc. (We can monitor through these applications) Applica
tions for the web server would be developed in Java, ASP, JSP, VBScript, JavaScr
ipt, Perl, Cold Fusion, PHP etc. (All the manipulations are done on the web serv
er with the help of these programs developed) The DBserver would be having oracl
e, sql server, sybase, mysql etc. (All data is stored in the database available
on the DB server) The tests performed on these types of applications would be -
User interface testing - Functionality testing - Security testing - Browser comp
atibility testing - Load / stress testing - Interoperability testing/intersystem
testing - Storage and data volume testing A web-application is a three-tier app
lication. This has a browser (monitors data) [monitoring is done using html, dht
ml, xml, javascript]-> webserver (manipulates data) [manipulations are done usin
g
programming languages or scripts like adv java, asp, jsp, vbscript, javascript,
perl, coldfusion, php] -> database server (stores data) [data storage and retrie
val is done using databases like oracle, sql server, sybase, mysql]. The types o
f tests, which can be applied on this type of applications, are: 1. User interfa
ce testing for validation & user friendliness 2. Functionality testing to valida
te behaviors, i/p, error handling, o/p, manipulations, services levels, order of
functionality, links, content of web page & backend coverage’s 3. Security test
ing 4. Browser compatibility 5. Load / stress testing 6. Interoperability testin
g 7. Storage & data volume testing A client-server application is a two tier app
lication. This has forms & reporting at front-end (monitoring & manipulations ar
e done) [using vb, vc++, core java, c, c++, d2k, power builder etc.,] -> databas
e server at the backend [data storage & retrieval) [using ms access, sql server,
oracle, sybase, mysql, quadbase etc.,] The tests performed on these application
s would be 1. User interface testing 2. Manual support testing 3. Functionality
testing 4. Compatibility testing 5. Intersystem testing Some more points to clea
r the difference between client server, web and desktop applications: Desktop ap
plication: 1. Application runs in single memory (Front end and Back end in one p
lace) 2. Single user only Client/Server application: 1. Application runs in two
or more machines 2. Application is a menu-driven 3. Connected mode (connection e
xists always until logout) 4. Limited number of users 5. Less number of network
issues when compared to web app. Web application: 1. Application runs in two or
more machines 2. URL-driven 3. Disconnected mode (state less) 4. Unlimited numbe
r of users 5. Many issues like hardware compatibility, browser compatibility, ve
rsion compatibility, security issues, performance issues etc. As per difference
in both the applications come where, how to access the resources. In client serv
er once connection is made it will be in state on
connected, whereas in case of web testing http protocol is stateless, then there
comes logic of cookies, which is not in client server. For client server applic
ation users are well known, whereas for web application any user can login and a
ccess the content, he/she will use it as per his intentions. So, there are alway
s issues of security and compatibility for web application.
What is Cookie? Cookie is small information stored in text file on user’s hard d
rive by web server. This information is later used by web browser to retrieve in
formation from that machine. Generally cookie contains personalized user data or
information that is used to communicate between different web pages. Why Cookie
s are used? Cookies are nothing but the user’s identity and used to track where
the user navigated throughout the web site pages. The communication between web
browser and web server is stateless. For example if you are accessing domain htt
p://www.example.com/1.html then web browser will simply query to example.com web
server for the page 1.html. Next time if you type page as http://www.example.co
m/2.html then new request is send to example.com web server for sending 2.html p
age and web server don’t know anything about to whom the previous page 1.html se
rved. What if you want the previous history of this user communication with the
web server? You need to maintain the user state and interaction between web brow
ser and web server somewhere. This is where cookie comes into picture. Cookies s
erve the purpose of maintaining the user interactions with web server. How cooki
es work? The HTTP protocol used to exchange information files on the web is used
to maintain the cookies. There are two types of HTTP protocol. Stateless HTTP a
nd Stateful HTTP protocol. Stateless HTTP protocol does not keep any record of p
reviously accessed web page history. While Stateful HTTP protocol do keep some h
istory of previous web browser and web server interactions and this protocol is
used by cookies to maintain the user interactions. Whenever user visits the site
or page that is using cookie, small code inside that HTML page (Generally a cal
l to some language script to write the cookie like cookies in JAVAScript, PHP, P
erl) writes a text file on users machine called cookie. Here is one example of t
he code that is used to write cookie and can be placed inside any HTML page: Set
-Cookie: NAME=VALUE; expires=DATE; path=PATH; domain=DOMAIN_NAME; When user visi
ts the same page or domain later time this cookie is read from disk and used to
identify the second visit of the same user on that domain. Expiration time is se
t while writing the cookie. This time is decided by the application that is
going to use the cookie. Generally two types of cookies are written on user mach
ine. 1) Session cookies: This cookie is active till the browser that invoked the
cookie is open. When we close the browser this session cookie gets deleted. Som
e time session of say 20 minutes can be set to expire the cookie. 2) Persistent
cookies: The cookies that are written permanently on user machine and lasts for
months or years. Where cookies are stored? When any web page application writes
cookie it get saved in a text file on user hard disk drive. The path where the c
ookies get stored depends on the browser. Different browsers store cookie in dif
ferent paths. E.g. Internet explorer store cookies on path “C:\Documents and Set
tings\Default User\Cookies” Here the “Default User” can be replaced by the curre
nt user you logged in as. Like “Administrator”, or user name like “Vijay” etc. T
he cookie path can be easily found by navigating through the browser options. In
Mozilla Firefox browser you can even see the cookies in browser options itself.
Open the Mozila browser, click on Tools->Options->Privacy and then “Show cookie
s” button. How cookies are stored? Lets take example of cookie written by rediff
.com on Mozilla Firefox browser: On Mozilla Firefox browser when you open the pa
ge rediff.com or login to your rediffmail account, a cookie will get written on
your Hard disk. To view this cookie simply click on “Show cookies” button mentio
ned on above path. Click on Rediff.com site under this cookie list. You can see
different cookies written by rediff domain with different names. Site: Rediff.co
m Cookie name: RMID Name: RMID (Name of the cookie) Content: 1d11c8ec44bf49e0… (
Encrypted content) Domain: .rediff.com Path: / (Any path after the domain name)
Send For: Any type of connection Expires: Thursday, December 31, 2020 11:59:59 P
M Applications where cookies can be used: 1) To implement shopping cart: Cookies
are used for maintaining online ordering system. Cookies remember what user wan
ts to buy. What if user adds some products in their shopping cart and if due to
some reason user don’t want to buy those products this time and closes the brows
er window? When next time same user visits the purchase page he can see all the
products he added in shopping cart in his last visit. 2) Personalized sites: Whe
n user visits certain pages they are asked which pages they don’t want to visit
or display. User options are get stored in cookie and till the user is online, t
hose pages are not shown to him. 3) User tracking:
To track number of unique visitors online at particular time. 4) Marketing: Some
companies use cookies to display advertisements on user machines. Cookies contr
ol these advertisements. When and which advertisement should be shown? What is t
he interest of the user? Which keywords he searches on the site? All these thing
s can be maintained using cookies. 5) User sessions: Cookies can track user sess
ions to particular domain using user ID and password. Drawbacks of cookies: 1) E
ven writing Cookie is a great way to maintain user interaction, if user has set
browser options to warn before writing any cookie or disabled the cookies comple
tely then site containing cookie will be completely disabled and can not perform
any operation resulting in loss of site traffic. 2) Too many Cookies: If you ar
e writing too many cookies on every page navigation and if user has turned on op
tion to warn before writing cookie, this could turn away user from your site. 3)
Security issues: Some times users personal information is stored in cookies and
if someone hack the cookie then hacker can get access to your personal informat
ion. Even corrupted cookies can be read by different domains and lead to securit
y issues. 4) Sensitive information: Some sites may write and store your sensitiv
e information in cookies, which should not be allowed due to privacy concerns. T
his should be enough to know what cookies are. If you want more cookie info see
Cookie Central page. Some Major Test cases for web application cookie testing: T
he first obvious test case is to test if your application is writing cookies pro
perly on disk. You can use the Cookie Tester application also if you don’t have
any web application to test but you want to understand the cookie concept for te
sting. Test cases: 1) As a Cookie privacy policy make sure from your design docu
ments that no personal or sensitive data is stored in the cookie. 2) If you have
no option than saving sensitive data in cookie make sure data stored in cookie
is stored in encrypted format. 3) Make sure that there is no overuse of cookies
on your site under test. Overuse of cookies will annoy users if browser is promp
ting for cookies more often and this could result in loss of site traffic and ev
entually loss of business. 4) Disable the cookies from your browser settings: If
you are using cookies on your site, your sites major functionality will not wor
k by disabling the cookies. Then try to access the web site under test. Navigate
through the site. See if appropriate messages are displayed to user like “For s
mooth functioning of this
site make sure that cookies are enabled on your browser”. There should not be an
y page crash due to disabling the cookies. (Please make sure that you close all
browsers, delete all previously written cookies before performing this test) 5)
Accepts/Reject some cookies: The best way to check web site functionality is, no
t to accept all cookies. If you are writing 10 cookies in your web application t
hen randomly accept some cookies say accept 5 and reject 5 cookies. For executin
g this test case you can set browser options to prompt whenever cookie is being
written to disk. On this prompt window you can either accept or reject cookie. T
ry to access major functionality of web site. See if pages are getting crashed o
r data is getting corrupted. 6) Delete cookie: Allow site to write the cookies a
nd then close all browsers and manually delete all cookies for web site under te
st. Access the web pages and check the behavior of the pages. 7) Corrupt the coo
kies: Corrupting cookie is easy. You know where cookies are stored. Manually edi
t the cookie in notepad and change the parameters to some vague values. Like alt
er the cookie content, Name of the cookie or expiry date of the cookie and see t
he site functionality. In some cases corrupted cookies allow to read the data in
side it for any other domain. This should not happen in case of your web site co
okies. Note that the cookies written by one domain say rediff.com can’t be acces
sed by other domain say yahoo.com unless and until the cookies are corrupted and
someone trying to hack the cookie data. 8 ) Checking the deletion of cookies fr
om your web application page: Some times cookie written by domain say rediff.com
may be deleted by same domain but by different page under that domain. This is
the general case if you are testing some ‘action tracking’ web portal. Action tr
acking or purchase tracking pixel is placed on the action web page and when any
action or purchase occurs by user the cookie written on disk get deleted to avoi
d multiple action logging from same cookie. Check if reaching to your action or
purchase page deletes the cookie properly and no more invalid actions or purchas
e get logged from same user. 9) Cookie Testing on Multiple browsers: This is the
important case to check if your web application page is writing the cookies pro
perly on different browsers as intended and site works properly using these cook
ies. You can test your web application on Major used browsers like Internet expl
orer (Various versions), Mozilla Firefox, Netscape, Opera etc. 10) If your web a
pplication is using cookies to maintain the logging state of any user then log i
n to your web application using some username and password. In many cases you ca
n see the logged in user ID parameter directly in browser address bar. Change th
is parameter to different value say if previous user ID is 100 then make it 101
and press enter. The proper access message should be displayed to user and user
should not be able to see other users account. What is BVT? Build Verification t
est is a set of tests run on every new build to verify that build is testable be
fore it is released to test team for further testing. These test cases are core
functionality test cases that ensure application is stable and can be tested tho
roughly. Typically BVT process is automated. If BVT fails that build is again ge
t
assigned to developer for fix. BVT is also called smoke testing or build accepta
nce testing (BAT) New Build is checked mainly for two things:
• •
Build validation Build acceptance It is a subset of tests that verify main funct
ionalities. The BVT’s are typically run on daily builds and if the BVT fails the
build is rejected and a new build is released after the fixes are done. The adv
antage of BVT is it saves the efforts of a test team to setup and test a build w
hen major functionality is broken. Design BVTs carefully enough to cover basic f
unctionality. Typically BVT should not run more than 30 minutes. BVT is a type o
f regression testing, done on each and every new build.
Some BVT basics:
• • • • • •
BVT primarily checks for the project integrity and checks whether all the module
s are integrated properly or not. Module integration testing is very important w
hen different teams develop project modules. I heard many cases of application f
ailure due to improper module integration. Even in worst cases complete project
gets scraped due to failure in module integration. What is the main task in buil
d release? Obviously file ‘check in’ i.e. to include all the new and modified pr
oject files associated with respective builds. BVT was primarily introduced to c
heck initial build health i.e. to check whether - all the new and modified files
are included in release, all file formats are correct, every file version and l
anguage, flags associated with each file. These basic checks are worth before bu
ild release to test team for testing. You will save time and money by discoverin
g the build flaws at the very beginning using BVT. Which test cases should be in
cluded in BVT? This is very tricky decision to take before automating the BVT ta
sk. Keep in mind that success of BVT depends on which test cases you include in
BVT. Here are some simple tips to include test cases in your BVT automation suit
e:
• • • •
Include only critical test cases in BVT. All test cases included in BVT should b
e stable. All the test cases should have known expected result. Make sure all in
cluded critical functionality test cases are sufficient for application test cov
erage.
Also do not includes modules in BVT, which are not yet stable. For some underdev
elopment features you can’t predict expected behavior as these modules are unsta
ble and you might know some known failures before testing for these incomplete m
odules. There is no point using such modules or test cases in BVT. You can make
this critical functionality test cases inclusion task simple by
communicating with all those involved in project development and testing life cy
cle. Such process should negotiate BVT test cases, which ultimately ensure BVT s
uccess. Set some BVT quality standards and these standards can be met only by an
alyzing major project features and scenarios. Example: Test cases to be included
in BVT for Text editor application (Some sample tests only): 1) Test case for c
reating text file. 2) Test cases for writing something into text editor 3) Test
case for copy, cut, paste functionality of text editor 4) Test case for opening,
saving, deleting text file. These are some sample test cases, which can be mark
ed as ‘critical’ and for every minor or major changes in application these basic
critical test cases should be executed. This task can be easily accomplished by
BVT. BVT automation suits needs to be maintained and modified time-to-time. E.g
. include test cases in BVT when there are new stable project modules available.
What happens when BVT suite run: Say Build verification automation test suite e
xecuted after any new build. 1) The result of BVT execution is sent to all the e
mail ID’s associated with that project. 2) The BVT owner (person executing and m
aintaining the BVT suite) inspects the result of BVT. 3) If BVT fails then BVT o
wner diagnose the cause of failure. 4) If the failure cause is defect in build,
all the relevant information with failure logs is sent to respective developers.
5) Developer on his initial diagnostic replies to team about the failure cause.
Whether this is really a bug? And if it’s a bug then what will be his bug-fixin
g scenario. 6) On bug fix once again BVT test suite is executed and if build pas
ses BVT, the build is passed to test team for further detail functionality, perf
ormance and other testes. This process gets repeated for every new build. Why BV
T or build fails? BVT breaks sometimes. This doesn’t mean that there is always b
ug in the build. There are some other reasons to build fail like test case codin
g error, automation suite error, infrastructure error, hardware failures etc. Yo
u need to troubleshoot the cause for the BVT break and need to take proper actio
n after diagnosis. Tips for BVT success: 1) Spend considerable time writing BVT
test cases scripts. 2) Log as much detailed info as possible to diagnose the BVT
pass or fail result. This will help developer team to debug and quickly know th
e failure cause. 3) Select stable test cases to include in BVT. For new features
if new critical test case passes consistently on different configuration then p
romote this test case in your BVT suite. This will reduce the probability of fre
quent build failure due to new unstable modules and test cases.
4) Automate BVT process as much as possible. Right from build release process to
BVT result - automate everything. 5) Have some penalties for breaking the build
Some chocolates or team coffee party from developer who breaks the build will d
o. Conclusion: BVT is nothing but a set of regression test cases that are execut
ed each time for new build. This is also called as smoke test. Build is not assi
gned to test team unless and until the BVT passes. BVT can be run by developer o
r tester and BVT result is communicated throughout the team and immediate action
is taken to fix the bug if BVT fails. BVT process is typically automated by wri
ting scripts for test cases. Only critical test cases are included in BVT. These
test cases should ensure application test coverage. BVT is very effective for d
aily as well as long term builds. This saves significant time, cost, resources a
nd after all no frustration of test team for incomplete build.
<!-var theForm = document.forms[ aspnetForm ]; if (!theForm) { theForm = documen
t.aspnetForm; } function __doPostBack(eventTarget, eventArgument) { if (!theForm
.onsubmit || (theForm.onsubmit() != false)) { theForm.__EVENTTARGET.value = even
tTarget; theForm.__EVENTARGUMENT.value = eventArgument; theForm.submit(); } } //
-->
Welcome to MSDN Blogs Sign in | Join | Help Searc h
Sara Ford s WebLog
My adventures in sharing Microsoft source code
• • • •
Home Email RSS 2.0 Atom 1.0
Recent Posts
• • • • •
Did you know… You can sort objects and members in the Object Browser? #221 Did y
ou know… There are two primary means of searching for objects in the Object Brow
ser? - #220 Did you know… You can show Extension Methods in the Object Browser #
219 Did you know… How to stop displaying all inherited members in the Object Bro
wser member pane - #218 Did you know… What consists of “other” in Show Other Mem
bers in Object Browser Settings? - #217
Tags
• • • • • • • • • • • • • • •
Accessibility CodePlex Editor Hurricane Katrina and Waveland Hurricane Katrina a
nd Waveland, MS Karate Miscellaneous MS Personal Power Toys as Shared Source @ M
icrosoft Software Testing Visual Studio 2005 Tip of the Week Visual Studio 2008
Astuces Visual Studio 2008 Tip of the Day Visual Studio 2008 ワンポイント
• • •
VS Window Docking VSCore Community PowerToys Whidbey VS Settings
News
• • • • •
Visual Studio Tip of the Week Archive Katrina and Waveland, MS Archives Biograph
y Disclaimer
• • • • •
Talk To Me
Biography Disclaimer Recommend a Visual Studio Tip of the Week Contact Me
•
Recent Entries
• • • • •
Did you know… You can sort objects and members in the Object Browser? - #221 Did
you know… There are two primary means of searching for objects in the Object Br
owser? - #220 Did you know… You can show Extension Methods in the Object Browser
- #219 Did you know… How to stop displaying all inherited members in the Object
Browser member pane - #218 Did you know… What consists of “other” in Show Other
Members in Object Browser Settings? - #217
•
Top Picks
• • • • • • •
Visual Studio 2005 Tip of the Week Archives How i got started in Computer Scienc
e Guidelines: a hidden feature for the Visual Stuido Editor Developing a test sp
ecification Automation Testing versus Manual Testing Guidelines Fundamentals of
Accessibility Testing for Accessibility (MSDN)
•
Channel 9 Videos
• •
Accessibility and Visual Studio Are there some misperceptions of working at Micr
osoft that you d like to correct?
• • • • • • • •
What does it mean to test? How many bugs a day do you find? Who decides who wins
between a developer and a tester? Introduction to DevDiv’s Test Case Management
System Investigating a test case failure in the lab Analyzing a Test Case Failu
re Finding and Logging a Bug
MSFT Women Bloggers
• • • • •
Gretchen Betsy Sue Charla Eileen
Archives
• • • • • • • • • • • • • • • • • • • • • • • • • • • • •
May 2008 (19) April 2008 (29) March 2008 (24) February 2008 (26) January 2008 (3
4) December 2007 (24) November 2007 (27) October 2007 (26) September 2007 (25) A
ugust 2007 (26) July 2007 (7) June 2007 (1) May 2007 (8) April 2007 (3) March 20
07 (6) February 2007 (2) January 2007 (5) December 2006 (5) October 2006 (8) Sep
tember 2006 (1) August 2006 (5) July 2006 (9) June 2006 (13) May 2006 (11) April
2006 (5) March 2006 (7) February 2006 (7) January 2006 (11) December 2005 (3)
• • • • • • • • • • • • • • • • • • • • • • •
November 2005 (12) October 2005 (26) September 2005 (29) August 2005 (19) July 2
005 (10) June 2005 (26) May 2005 (24) April 2005 (27) March 2005 (15) February 2
005 (6) January 2005 (13) December 2004 (8) November 2004 (7) October 2004 (4) S
eptember 2004 (6) August 2004 (8) July 2004 (1) June 2004 (11) May 2004 (14) Apr
il 2004 (14) March 2004 (8) February 2004 (3) January 2004 (11)
Automation Testing versus Manual Testing Guidelines
I met with my team’s automation experts a few weeks back to get their input on w
hen to automate and when to manually test. The general rule of thumb has always
been to use common sense. If you’re only going to run the test one or two times
or the test is really expensive to automation, it is most likely a manual test.
But then again, what good is saying “use common sense” when you need to come up
with deterministic set of guidelines on how and when to automate? Pros of Automa
tion If you have to run a set of tests repeatedly, automation is a huge win fo
r you It gives you the ability to run automation against code that frequently
changes to catch regressions in a timely manner It gives you the ability to ru
n automation in mainstream scenarios to catch regressions in a timely manner (se
e What is a Nighlty) Aids in testing a large test matrix (different languages
on different OS platforms). Automated tests can be run at the same time on diffe
rent machines, whereas the manual tests would have to be run sequentially. Cons
of Automation It costs more to automate. Writing the test cases and writing or
configuring the automate framework you’re using costs more initially than runni
ng the test manually. Can’t automate visual references, for example, if you ca
n’t tell the font color via code or the automation tool, it is a manual test. Pr
os of Manual
If the test case only runs twice a coding milestone, it most likely should be a
manual test. Less cost than automating it. It allows the tester to perform mor
e ad-hoc (random testing). In my experiences, more bugs are found via ad-hoc tha
n via automation. And, the more time a tester spends playing with the feature, t
he greater the odds of finding real user bugs. Cons of Manual Running tests ma
nually can be very time consuming Each time there is a new build, the tester m
ust rerun all required tests which after a while would become very mundane and t
iresome. Other deciding factors What you automate depends on the tools you use
. If the tools have any limitations, those tests are manual. Is the return on
investment worth automating? Is what you get out of automation worth the cost of
setting up and supporting the test cases, the automation framework, and the sys
tem that runs the test cases? Criteria for automating There are two sets of ques
tions to determine whether automation is right for your test case: Is this test
scenario automatable? 1. Yes, and it will cost a little 2. Yes, but it will cost
a lot 3. No, it is no possible to automate How important is this test scenario?
1. I must absolutely test this scenario whenever possible 2. I need to test thi
s scenario regularly 3. I only need to test this scenario once in a while If you
answered #1 to both questions – definitely automate that test If you answered #
1 or #2 to both questions – you should automate that test If you answered #2 to
both questions – you need to consider if it is really worth the investment to au
tomate What happens if you can’t automate? Let’s say that you have a test that y
ou absolutely need to run whenever possible, but it isn’t possible to automate.
Your options are Reevaluate – do I really need to run this test this often?
What’s the cost of doing this test manually? Look for new testing tools Cons
ider test hooks Posted: Monday, February 07, 2005 6:38 PM by saraford Filed unde
r: Software Testing

Comments
Bruce McLeod said: Hi Sarah,
Interesting post. I have recently blogged about my opinion on the same subject h
ere: http://www.teknologika.com/blog/General/Testing/TenetsOfTestingPartTwo.html
. Regards, Bruce McLeod bruce at teknologika dot com # February 8, 2005 3:37 AM
Brian said: Thanks. In my position I have been mulling this over for a while. I
think i will have use for your framework. I was just assigned another product of
ours and I need to decide what I can and should automate. # February 8, 2005 9:
27 AM
Rob Caron s Blog said: # February 8, 2005 12:34 PM
Stephane R said: Automation makes you capitalize on invariants, hence test famil
ies. But what about adapting to the slightest changes in UIs? Do you simply thro
w a broken test case to the trashcan, or do you fix it? A big con of automation
is that it doesn t find you any new bugs. If you want to find those, you need to
either find those yourself by hand, or rely on somebody else s work. Are you st
ill using VisualTest for runs? How will that evolve will UIs going more towards
IDless controls in UIs? # February 8, 2005 1:20 PM
sara ford said: Stephane, "Do you simply throw a broken test case to the trashca
n, or do you fix it?" That s a good point about Automation that i missed in the
above guidelines. There is a cost with Automation to maintain the test case. Alm
ost always, you fix the test case, unless the app has changed in such a way that
the test is no longer valid. For example, say you test for a feature, but the f
eature is modified or cut,
then you would most likely destroy the test case. One good rule of thumb is don
t automate if you know the UI will be in flux. The slightest changes in UI can c
ause automation to fail. When you know the UI has been finalized, excluding any
fixes to bugs, that s the time to automate. "A big con of automation is that it
doesn t find you any new bugs." I disagree with this statement. The point of aut
omation is to find regressions. Regressions are bugs that appear because of some
change in the code. For example, say a developer fixes a bug, but because of th
e bug fix, another bug appears, the second bug is called a regression. "Are you
still using VisualTest for runs?" I ve never used VisualTest. We have our own au
tomation framework. Thanks, -sara # February 9, 2005 10:32 AM
Ran Gishri said: Great post. I would like to add yet another dimension to the de
cision - the human factor. Having worked with testing teams in three continents
I believe that building a good automated test suite, one that truly delivers the
anticipated ROI, cannot be achieved by your average Joe. Programming great test
cases that really work is much like, well, programming... Therefore, when you c
onsider whether to automate a test suite, I recommend you seriously consider the
level of expertise of your test team. Leaving automation to a non-expert would
probably lead to a lot of frustrations and no ROI. This all applies to functiona
l or regression test. When it comes to load test, obviously automation is absolu
tely mandatory. Gone are the days when you summoned 40 employees into a big lab
and asked them to hit the Enter key at the same time... # February 10, 2005 12:5
3 AM
Nilesh said: Suppose you have 4 cycles of tetsing and last cycle is regerssion w
herein you would think of automating the tests. First three cycles involve manua
l testing which include right from writing the test cases to execution. After su
cuessful completion of first three cycles, automation plays its role then during
this regerssion all the manual testers would no longer be required as u have hi
red automation specialists. Would it be justified to fire them??? # February 28,
2005 1:27 AM
Ken Baker said: Nilesh, I think the approach of manual testing all test cases fo
r multiple passes and then running those same test cases with automation for the
final "phase" is not a real world scenario. Ideally most projects would have ma
nual testing and automation going on at the same time, or even have automation b
eing coded before there is anything to test. In an ideal and agile world, your a
utomation for a feature under test should be completed before the feature is cod
e complete. This is an aspect of test driven development. Also keep in mind that
automation is not limited to GUI testing or driving the application through GUI
manipulation. That is, most people think of GUI and they say UI. UIs encompass
more than only GUIs. All testing requires UI in that calling a function/method o
f a DLL or webservice is interacting with a UI (a non-graphical UI). So, if you
have a detailed design spec or you practice Scrum or other agile/xp methodologie
s, the QA people will know what is being devloped before it is done, and they ca
n code some automation prior to the functionality even being "codecomplete". It
is up to the team/group to decide if the automation is run prior to code complet
e and thus should pass once the feature goes in or if the automation is run only
after you know the feature goes in. All the while, as Sara has already detailed
and as is the crux of her blog entry here, there are classifications of testing
that make no sense to be automated. Thus, each project has some balance to find
between what is to be automated, when to automated it, how it will be automated
, who will automate it, and how is manual testing complementing what is not bein
g automated. For too long many teams/groups have pictured QA in terms of how can
automated testing compliment manual testing and improve quality. In reality, au
tomation needs to have a larger and earlier focus and manual testing is the comp
liment to fill the holes where it makes no sense time-wise, feature-wise, or ski
ll-wise to automate a test. ADditionally, manual testing may certainly be needed
for tests to be run that are planned to be implemented via automation at a late
r time, but there will alsways be testing that won t be and shouldn t be automat
ed. # March 1, 2005 4:17 PM
Nilesh said: Ken, I got the gist of ur reply...But isn t manual testing necessar
y atleast for one pass? Or should we automate all the passes?? Thanks Nilesh
# March 2, 2005 1:05 AM
Nilesh said: Ken, I got the gist of ur reply...But isn t manual testing necessar
y atleast for one pass? Or should we automate all the passes?? Thanks Nilesh # M
arch 2, 2005 1:05 AM
Ken Baker said: Well, it seems to me the question should be "What part of the te
sting do we automate?" rather than "What iteration of the test pass should be au
tomated?" Let s say we have an existing project that has been released. Now we p
lan a new release with 6 new features and 4 bug fixes. Before we start work on t
his new release we have no automated testing in place. How do we proceed? My foc
us, if I wanted to introduce good automated testing, would be to focus on automa
ting testing on the new features and possibly have as much of this automation do
ne and ready to run before each feature is "code-complete". Let s assume that is
possible. You would still use manual testing to verify the bug fixes and test f
or regressions around these bug fixes as well as around the new features, though
the depth of the automated testing could also be used to test for regressions a
round the new features as well (though I would not recommend this). The reason y
ou wouldn t automate the testing of the bug fixes is actually the same reason yo
u probably wouldn t automate testing for regressions around the addition of new
features. Manual testing is good here because it is a form of oneoff smoke testi
ng or adhoc testing, basically, to verify the bugs are fixed and caused no regre
ssions and that the new features did not create bugs near but outside of them. N
ow let s say it is not possible to have all your new automated testing complete
before there is testable code, maybe some is or maybe none is. Of course you sho
uld sit around and not test completed code as you wait for automated tests to be
completed. This is one reason why all automated testing should also have formal
test cases. If you are ever waiting on automated tests, then these tests can an
d should be run manually. This applies when and if your automation becomes out d
ated as well, though there should be a strong emphasis on not letting automated
testing get out dated. So, in these cases we use manual testing where we want to
be using automated testing. Always keep in mind that one of the worst things, i
n my opinion, that a QA person or team can do is let code-complete
features sit untested too long. So, if your automation is not ready...manual tes
ting is needed. The other point buried in what I was saying up there is that the
re are types of testing you will never automate. The first category of testing t
hat you should not automate is testing that does not require being repeated on a
build-by-build, daily, or weekly basis. (All of this is excluding load, perform
ance and scalability testing, of course). Automated testing is about demonstrati
on of repeated reliability and catching regressions in code that is being update
d or impacted by other code updates. # March 2, 2005 10:24 AM
Ken Baker said: I wish I could edit my reply: There is a line above that should
be "Of course you should *not* sit around and not test completed code as you wai
t for automated tests to be completed." # March 2, 2005 10:27 AM
Test Notes said: # March 4, 2005 9:35 AM
Test Notes said: # March 4, 2005 9:36 AM
Munuren said: Nilesh, # March 7, 2005 10:43 PM
Amol Chavan said: What are test hooks ? Amol. # March 8, 2005 11:00 PM
software testing notes said: Hi my name is sakthi and my e-mail address will be
sakthisankar@msn.com I need
some notes regarding the testing can any on send me regarding the automated tool
s. # April 11, 2005 11:46 AM
Md.Fazel Hussain said: Hi Saraford, You have really mastered the art of explaini
ngTesting .I would be happy if I could get some tips like this at my mail. # Apr
il 19, 2005 6:53 AM
Mayur said: Hi , So far you have only concentrated on execution part of testing.
..I want to know if the planning part can be automated as well ? # April 22, 200
5 5:47 AM
Venkat said: Hi... Thanks for great Post..Some are asking when we have to automa
te? Is it in the Initial Testing Phase or in subsequent Testing.. Let me tell yo
u my experience.. Many times we go to automation for regression testing and perf
ormance testing.Based on type of testing we ll opt type of tool. For example we
can opt WinRunner for Regression and LoadRunner for Performance. As Saraford sai
d, one should be cautious how automation is going to help our testing in the nex
t versions. # May 12, 2005 10:37 PM
Test it till it hurts said: I came across this great article by Sara Ford about
when to automate. I ve read lots of articles concering this topic and they all
seem to boil down to the few questions that sara outlined. I believe that one cr
iteria that s over looked sometimes is if th # May 31, 2005 8:45 PM
Jonathan de Halleux said: Cons of manual testing: The tester gets more and more
bored by his work. Before soon, he either 1) gets depressed, 2) starts looking f
or another team/company. Both ways, productivity dives and soon enough you loose
working force in which you invested education/training money. :) # May 31, 2005
10:26 PM
Meenakshi Thiyagarajan said: Hai sara, Its clear and brief. well its quite inter
esting. I am new to this field. Gave me a brief description of the manual and au
tomated testing. # June 19, 2005 1:37 AM
Sanjay K said: really good stuff # July 11, 2005 1:04 PM
Raja Balachand said: hi very good posting. i need a clear classification of prac
ticle approach for TESTING. what happens in Real time senario after geathering r
equirements and till delivary stage? i need how to proceed with SRS, Test plans
Test cases, Which Test Cases To Be automated? can any one help me ramineni999@gm
ail.com # September 12, 2005 1:02 PM
shrinivas said: Nice article , but the author should be more clear in explaining
and if this one of more depth , it would have been more useful for us. If it is
possible please give when should we plan automating the test cases ( during SRS
or while creating Test Plans ) # September 30, 2005 4:56 AM
Sathya said: This indeed great article, Can you suggest me in a typical Product/
application life cycle (< 1 year) how much of effort required for writing test
cases versus test execution? # October 20, 2005 7:26 AM
Sathya said: This indeed great article, Can you suggest me in a typical Product/
application life cycle (< 1 year) how much of effort required for writing test
cases versus test execution? # October 20, 2005 7:27 AM
shiraz.rajwani@kotak.com said: Hi, There seems to be good knowledge sharing post
s in your blogs. If you take my opinon about Automation vs Manual then i would s
ay that its not only monetary factors or size of application that makes us to de
cide what to go for. What i think that apart from these factors a Project Manage
r need to consider; 1. How much quality the development team delivers to the tes
ters (Less bugs or more bugs)? 2. What is the project deadline ? 3. How critical
is the project ? Say if you are making an application for NASA than you need to
do manual and automation also and i would suggest that the application should a
lso be tested even if it goes live. 4. How familiar is the user with the technol
ogy ? (Novice / Beginner / Advanced) 5. What will be the users reaction if he fi
nds a bug ? Say if the application goes live and if the user discovers a bug the
n how will he handle it. Will he protect himself from the bug and pray not to se
e that bug again (Eg. Win XP OS) or will he stop the application and pick up the
phone and will yell to the support team (Like we do today with call center guys
) which will definately make an impact on users impression for vendors quality A
nd this list can go on . I think based on these factors and cost of resources (m
oney , labour , time)involved you can decide whether to go either for manual or
automation or both . # October 25, 2005 3:21 AM
smitha said: Very good one for a fresher to understand. Can I have detail notes
regarding Manual Vs Automation testing as i have to take a session in my company
for freshers. Pls help me out?
# October 28, 2005 5:51 AM
David Gilbert said: Sara -- good post, and a good set of rules of thumb to work
with. But I also agree with your early comment on using common sense. It is a ve
ry contextual consideration. For my two cents worth, look at my editorial at htt
p://www.siriussqa.com/newsletter1.html. Sincerely, David Gilbert # November 26,
2005 8:18 AM
sa.rafee said: hello sarafords, I want know how to test in manaul give explain a
nd please send some test case which you have applied for any object like combo b
ox;list box;edit text feild. # December 11, 2005 2:08 AM
s.varaprasad said: hi iam very impressed about manual and automation .Can you ex
plain detailed explanation regarding the live environment in companies. # Februa
ry 22, 2006 6:11 AM
saritha said: more notes about manual versus automated testing # February 27, 20
06 12:17 AM
Pankaj Mendiratta said: Hi Sara, First, I would like to thanks you for such a gr
eat and best differentiation between Manual and Automated Testing. Sara, could y
ou give me some good ppt on this topic and on when to use which tool in automati
on and some good tutorials on winrunner.. Many Thanks God Bless You Sara
pankajm@servizio.in # March 20, 2006 3:26 PM
Abhilasha said: I am new to testing field.Currently working as a developer from
last 2 years and want to shift to testing soon can any one provide me notes regr
ading testing from basics. my mail id id abhips686266@rediffmail.com # April 6,
2006 4:45 AM
Sachin said: I am new to testing field.Currently working in mech field and want
to shift to testing soon can any one provide me notes regrading testing from bas
ics. my mail id is sjdhote@gmail.com # April 24, 2006 5:22 AM
srikant said: Hi Sara, I am very much impressed with this topic.Its really a tim
e to appreciate u r topic.According to my point of view i think tools cannot be
intellegent than human brains.Rather manual testing takes time to complete the t
esting but its reliable,whereas automation tools leaves behind some important bu
gs which are difficult to find by tools.Tools are needed during the time of test
ing the load and performance.Is this section gives a point of view.If so pls fee
l free to send any comments. My mail id is:srikant_2977@yahoo.co.in srikant_ctc@
rediffmail.com # May 1, 2006 2:03 AM
harry said: Sir/Madam, This time i am workin in softare company they put me on M
anual Testing.Here is not Automated Testing.Are there scope of Manual testing.Pl
ease Suggest me.My Email ID is harish_usa@rediff.com # May 5, 2006 8:15 AM
sameer said: Hi Sara, This is a good artical and I am impresed. Sara, currently
I am doing Manual
testing on Web Applications. Please guide me should I shift to Automation testin
g and which is the right tool for that. And will you please tell me should I go
for the CSTE exam though I am doing manual testing. my mail Id is : - sam_sps@ya
hoo.co.in or sameer.bhate@rediffmail.com Thank you With Warm Regards Sameer # Ma
y 11, 2006 7:51 AM
parveen kumar said: Respected mam or sir, Quest:-How Can we apply manual testing
on web based parojat or like java based project.
Thanks mam # June 1, 2006 8:56 AM
sarithareddymeda said:
hi sara, i am very new to the testing enviornment specially manual , what are th
e intiatiives need to be taken to make myself perfect on manual testing, and can
you please list out the websites which quote examples of manual testing. thank
u # June 5, 2006 3:25 AM
saikishore said: Hello sara iam saikishore iam trying for a break in software te
sting nearly i have attended 25 interviews but couldnot get any initial break an
d iam mailing some of the interview questions on testing if you have answers for
them please reply me and waiting for your response thanking you
MPHASIS INTERVIEW QUESTIONS 1. Explain Bug Life cycle 2. What is integration tes
ting and regression testing 3. What is verification and validation 4. How does w
inrunner recognizes the project which is in custom build 5. What is expert view
and tree view 6. How does QTP identifies the project 7. What is the difference b
etween Winrunner and QTP 8. What is Test Director and which version of test dire
ctor your are using in your project 9. What is a test plans 10. what are the con
tents present in a test plan 11. What is the risk of testing a project SEMANTIC
SPACE INTERVIEW QUESTIONS 1. What is configuration Management 2. What is change
management 3. What are Severity and priority levels 4. What is Data integrity an
d Data validity 5. What are the browsers available and explain their versions 6.
Is it possible that Quality variates project to project 7. What are GUI Map fil
es and explain their Contents 8. What is Data base check point and why we go for
that 9. What is the difference between the Client server application and a Web
application 10. Does Winrunner Supports Web applications 11. What is process Man
agement 12. What is an Error, Defect, Bug 13. What is Quality 14. Which version
of Winrunner you are using 15. What is Build Verification and why we go for it 1
6. What is Defect density 17. What is Integration testing 18. What is Static tes
ting and types of Static testing
19. 20. 21. 22.
What is Validation testing what is Data driven testing and why we go for data dr
iven testing what is the definition of Testing What is Sanitation Testing
TESTING INTERVIEW QUESTIONS (SECOND ROUND) 1. What are joins and subjoins in the
data bases 2. what is data driven testing 3. what is verification and validatio
n 4. What is Quality Assurance (QA) and Quality Control (QC) 5. Is Verification
is related to QA and Validation is related to QC ? 6. which type of model you fo
llow basically in your project 7. what is a use case 8. How to test a Bike 9. ho
w to test a Lift (Elevator). 10. which configuration Management tool do you use
11. which Bug tracking tool do you use 12. explain Bug life cycle 13. what is Re
gression testing 14. what is ALPHA testing ans BETA testing 15. What types of te
stings comes under Non functional testing 16. what is TEST DIRECTOR 17. what is
CMM and CMM i 18. whar are Expressions in Winrunner 19. What is a Compile module
20. Is it Necessary to open the tool first or the application first 21. after g
etting a bug what will you do 22. if you add a new object or a new module for th
e existing application then how will you test the application 23. which Defect t
racking tool do you use 24. what is change management 25. What is smoke Testing
26. what is sanity testing 27. A application is given to you but the requirement
s and functionalities are missing what will you do to start the testing 28. whic
h testing documents will be received by the client SYNCOTA INTERVIEW QUESTIONS 1
.what is a test plan 2.Actually when will be the testing people will be involved
in the project 3.Define low priority and high severity 4.Whom do you report the
Bugs
5.what are the contents present in a test plan 6.which model will you follow 7.W
hich Bug tracking tool do you use and what are the contents present in it 8.If a
bug is reported what will be the Next work done 9. How to write test cases usin
g Use case diagrams 10.For a given condition (X>=0<100) how many test cases you
can write ACCENTURE INTERVIEW QUESTIONS 1.what is BVA and ECP 2.Do we have recov
ery manger in Winrunner 3 how does the winrunner recognizes the project 4 how is
winrunner is used in the project BLUESTAR INFOTECH INTERVIEW QUESTIONS 1. 2. 3.
4. 5. 6. What is the difference between Sleep and wait in winrunner what is int
egration testing and types of testing present what is system testing what is dat
a driven testing what is functionality testing if requirements are given to you
then how do you write the test cases for it
Account number = Ok cancel For above given form the valid account number starts
from 1 to 1000 so is it necessary to input the 1,2,3 ….998,999,1000 test cases t
o check the conditions of valid account numbers I,e is it compulsory to write 10
00 test cases for the above form
STAG SOFTWARE INTERVIEW QUESTIONS 1.what are the types of recording modes in win
runner 2.what are the three modes of running a test in winrunner 3.what is synch
ronization point 4.what are the contents present in a test case 5.do we need tes
ting for the project 6.what is code review and code walk through 7. At which pha
se the testing starts (begin) in the project 8. How do we test Client server app
lications and a Web applications
9. what is verification and validation 10. what is adhoc testing 11. what is tra
ceability matrix 12. what is base line document 13. what is Test Life Cycle 14.
what is regression testing and retesting 15. what is a BUG LIFE CYCLE 16. what i
s a Bug 17. what are defects 18. what is functionality testing and system testin
g. 19. a project has to be released in one day but the testing people got that p
roject from the developers half of the day before so what they have to do to com
plete the testing process. 20 what are severity level and priority levels AZTEC
SOFTWARE INTERVIEW QUESTIONS 1. What is BVA and ECP 2. Which version of WINRUNNE
R and QTP you are using in the project 3. What is the use of Recovery manager in
QTP 4. What is retesting and regression testing 5. Write the SQL queries for th
e following EMP table to select the employee id and his details from emp table 6
. For example: employee dept and employee id and employee name and employee sala
ry 7. what is a sub and what is a driver 8. What are your roles and responsibili
ties in your project 9. Does BVA is equivalent to ECP 10. If you find a bug what
will you do TESTING INTERVIEW QUESTIONS Choose the correct answer 1.Testing wor
k starts once a)once requirements are complete b)once test cases are complete c)
once coding is complete d)Beginning of the requirement 2.For White box testing ;
A)The tester is completely unconcerned about the internal behaviour of the progr
am B) the tester is concerned with finding the circumstances in which the progra
m does not behave according to code standards C) Test data is derived from marke
t requirements 3.stress testing is a measure of one of the following a) applilca
tion response time b) concurrent load on application can handle c) transaction p
er minute that can be handled d) virtual load at which the system will fail 4.Su
san reviews a QA test plan prepared by her counterpart and gives her comments. I
t’s a part of a)Quality control b)Quality Assurance c)Both d)none 5.user accepta
nce testing means ; a)testing performed on a single stand alone module b)testing
after changes have been made to ensure that no unwanted changes were introduced
c)testing to ensure that system meets the needs of the organization and the end
user
6.Software Quality Metrics will help you to A) Keep account on the software qual
ity of an application B) Analyze and improve the deficiencies of the application
C) Both of the above D) None of the above 7) Regression Testing: a) Tests how w
ell the program runs with Adverse data b) Tests program input branches c) Select
ive retesting to verify modifications have not cause adverse effects d) Testing
data during requirements phase 8)Application that has GUI must be tested for usa
bility a) For any kind of UI applications b) More necessary for Web- based appli
cations c) Only if the user is going to use the UI
d) Only if the user pays for it 9) the program according requirements expects th
e uppercase letters from A to Z .analyse the following inputs and choose one tha
t can cause the failure with greater probability. a) @, [ b) 1,0 c) B, W d) [,]
10)A system test that forces the software to fail in a variety of ways and verif
ies that software is able to continue execution without interruption. This defin
ition is nearest to; a) Recovery testing b) Stress Testing c) Both of the above
e) None of the above 11)Automated testing is necessary when a) testing has to be
done very quickly b) number of resources are very less c) most of the test case
s are similar in nature d) all of the above 12) which of the following tests is
performed early in a software testing process a)Monkey testing b)Unit testing c)
System testing d)None of the above 13)The testing technique that requires devisi
ng test cases to demonstrate that each program function is operational is called
a) Black box testing b) Glass-box testing c) Grey-Box testing d) White-Box Test
ing 14) What UML diagram is useful for black box testing a) Class diagram b) Obj
ect diagram c) Use case diagram d) Sequence diagram 15) What kind of tools would
you suggest to use the automation of regression tests
a) Capture and play back b) Static analysis c) Simulators e) Debugging tools Bas
ics of Winrunner 1. In analog mode of recording the maximum value of X in (X, Y)
a) the height of the screen, in Pixels, minus one. b) The height of the screen,
in Pixels c) The width of the screen d) The width of the screen, in Pixels 2.Du
ring play back, you accidentally hit “pause’ a) Execution stops and you need to
start from the beginning of the TSL again b) Executions stops and you can start
off execution again from where you had stopped, all variables Have to be redefin
ed c) Execution stops and you can start off execution again from where you had s
topped, all variables will still remain initialized e) You need to restart win r
unner to execute again 3) To start recording on a Web based application using wi
n runner and IE ; What of these is the best practice a) You have to shut down al
l Open IE sessions, open the application and then open win runner b) You have to
shut down all Open IE sessions, open win runner and then open the application c
) Open application and then open win runner d) Open win runner and then open the
application 4)the types of variable declarations found in a TSL function are a)
Static and Public b)auto, static and public c)auto ,static and extern d)need not
be declared e)C&D 5)You have executed a tl_step function in TSL for a context s
ensitve case . if thecondition fails] a)winrunner report shows the whole Run as
failed b)winrunner report shows only that step has failed c)winrunner report ign
ores the failure
d)None of the above 6) Which of this is true a)You always require a GUI file to
play a context –sensitive script b)you always require a GUI file to play an anal
og script c)Not necessary to have GUI file at all d)a&b e)none of the above 7) w
hich of the following describes the window www.india.com in regularized form a)”
!.India b)”!.*India c)”!India e) all of the above f) none of the above
TESTING INTERVIEW QUESTIONS 1. Explain Classical water fall model 2. Integration
testing is conducted by developers or testers 3. an application is given how do
you test for example the money deposited in account no.2 should be transferred
to Account no.1 Account no: 1 Account no: 2 Ok Cancel 4. what is V model 5. What
is BUG life cycle 6. What is alpha testing and beta alpha testing 7. What is ve
rification testing and validation testing 8. What are ISO and CMM standards leve
ls 9. Which should be given more preference I.e. severity or priority ? 10. How
to use the test director in your project 11. What is use of recovery manager in
QTP 12. What are the add ins in QTP 13. What are expressions in QTP 14. if the d
evelopers are not convinced with your bug in this case what will you do 15. if t
he developers are developing the application then what is the job assigned to th
e testers 16. What is system testing 17. What is smoke testing
18. What is sanity testing 19. What is sanitation testing
# June 13, 2006 4:46 AM
venkatesalu said: Hi, I am venky. I would like to know some sites regarding Manu
al testing tat will guide me. I wish to know sites that allowsme to practice Man
ual testing with samples and other stuff. # June 13, 2006 7:12 AM
Amit said: Hi, I am new to testing, could you please tell me how is a manual tes
ting done in a real life situation,starting from initiation to execution.Also ho
w is a test case run/tested manually. Thanks. # June 13, 2006 12:58 PM
QTPro Questions and Answers said: Came through the google search, Found this art
icle, and it s nice. Probably a better insight for people who are still confused
about whether to go for automation or not for particular testing tasks or modul
es. # July 6, 2006 7:00 AM
Sarah said: I do manual testing on Web based applicatons and I want to change th
e format of the test scripts that the company has used in the past. TDo you know
of a resource I could use to see different types of formats? We also just start
ed Agile developing. thanks much # July 17, 2006 2:27 PM
Dhatchayini said: can u tellme which is going to rule in future? Manual testing
r Automation Testing # July 18, 2006 5:39 AM
Feroz Khan said: I have two question to ask and as always your help will be grea
tly appreciated. How do you answer this question if you were me as I am totally
new to testing feild Q1- Can you explain your experience with writing test scrip
ts from scratch using automation tools such as Silktest, Winrunner, Test Directo
r, SilkPerformer, homegrown, etc). Q2- Can you explain your experience with, and
philosophy about, creating an architecture/harness for automated tests. What wa
s the hardest thing about implementing it? # July 18, 2006 5:21 PM
Ram Potula said: Excellent job, very useful information. Thank you. # July 24, 2
006 3:47 PM
shivappa said: Dear Sir/madam,
Sub: Application for suitable post (Master of computer applications) Having come
to understand that there is an opportunity for a Post-graduation in
MCA, in your esteemed organization, I offer myself as a candidate for the same.
I request you to consider my application favorably. I have enclosed my Resume th
at will be helpful to you to know my educational details. I shall produce the ce
rtificates of all qualifications mentioned therein when I am called for an inter
view. I promise to discharge my duties, when appointed, to the best of my abilit
ies.
Thanking you.
Yours faithfully, Shivappa.Seemikeri Cell No:9880058464 Enclr:Resume # July 25,
2006 6:56 AM
sateesh varma said: Hi! Madam I’m sateesh new to testing field. I want more info
rmation about manual testing plz send manual testing notes thanks madam # August
3, 2006 2:50 AM
tahir said: Hi, please let me some manual testing tips. if anybody has Manual te
sting notes or questioning answering in details plz send me on my mail id tahir@
sebiz.net or send me URL Thanx n regards, Tahir AHmad # August 7, 2006 11:56 A
M
sree said: Hi Sara, your information is very clear and intresting. I am new to t
his field and I would like to know more details about Manual and Automated testi
ng. If you or any one have notes about both Manual and Automated testing, please
provide me. That should be very helpful to me and would be great. My emai id :
srireddys@gmail.com. Thanks & regards, Sree # August 15, 2006 11:08 AM
sree said: No Problem # August 15, 2006 11:09 AM
Shivani said: Hi, Ms. Sara Thanks for this guidance, i am new to this feild,i re
ally appreciate your notes.Please provide some more information if possible on S
oftware Testing. Regards Shivani # August 16, 2006 4:30 AM
Sheetal said: Hi Sara & All, Its really great to know how u all are asking & sha
ring ur questions on the Board. From now onward I also want to become the part o
f the family. Regards, Sheetal # August 20, 2006 12:53 AM
Raj kumar said: Hi, Ms. Sara ,
I’m raj kumar have a 1 years in testing field. I want more information about man
ual as well as Automation testing plz send manual and Automation testing notes.
and also sand me latetest Question for QTP and Load Runner and Guide me . My Mai
l IDrajkumar.saw@gmail.com Thanks and regards, Raj kumar # August 20, 2006 11:46
PM
Ankur said: Hi, Need notes on software testing. Further if i cud get some script
s that automate testing. I am new to this so if u cud help me. # August 23, 2006
2:20 AM
Manav said: Hi, Ms. Sara, A great article. Well incase if u have notes on Softwa
re Testing and Samples of Automation Script. I would like to receive one. They w
ill really help me to further understand and enhance my knowledge. Also using th
em i can enhance my skills. Please guide and help me... Thanking You, Manav emai
lid: ankurjain_ojsb@rediffmail.com # August 23, 2006 2:26 AM
KY Sundar rao said: Dear sarah Madam, I am Sundar. I would like to know some sit
es regarding to practice Manual testing with samples and other stuff. If you or
any one have notes about both Manual and Automated testing, please provide me. T
hat should be very helpful to me and would be great. Thank you very much.
Kind regards, Sundar. # August 24, 2006 12:53 PM
Srinivasan said: hi sara its clear now of automated and manual testing, can u te
ll what role Unix shell,perl scripts in testing and what are the prospects of th
e above regards srinivasan # August 29, 2006 3:55 AM
vasanthbabu said: Hi, Ms. Sara , hello sarafords, Its really very interesting to
go on reading ur views and suggestion for the Others Querys and i am very much
impressed with the software testing and i had joined the software testing course
recently and i dont know abt anything but i have an interest to get good knowle
dge in testing field and i develop myself but there is no guidence for me until
i seen ur website and i dont worry now since u r now with me So please help me m
am and I want know how to test in manaul give explain and please send some test
case which you have applied for any object like combo box;list box;edit text fie
ld and I am very impressed about manual and automation .Can you explain detailed
explanation regarding the live environment in companies and Can you send some g
ood tutorials on winrunner..and Especially i am very new to the testing enviornm
ent specially manual , what are the intiatiives need to be taken to make myself
perfect on manual testing, and can you please list out the websites which quote
examples of manual testing and i would like to know some sites regarding to prac
tice Manual testing with samples and other stuff # September 16, 2006 4:06 PM
Praveen Kumar.N said: Hi! Madam I’m Praveen Kumar.N new to testing field. I want
more information about manual testing plz send manual testing notes thanks mada
m .This is my mail id:
navathi_0522@yahoo.com # September 18, 2006 11:45 AM
Praveen Kumar.N said: Please send Answers : And more questions & Answers pls sen
d me SEMANTIC SPACE INTERVIEW QUESTIONS 1. What is configuration Management 2. W
hat is change management 3. What are Severity and priority levels 4. What is Dat
a integrity and Data validity 5. What are the browsers available and explain the
ir versions 6. Is it possible that Quality variates project to project 7. What a
re GUI Map files and explain their Contents 8. What is Data base check point and
why we go for that 9. What is the difference between the Client server applicat
ion and a Web application 10. Does Winrunner Supports Web applications 11. What
is process Management 12. What is an Error, Defect, Bug 13. What is Quality 14.
Which version of Winrunner you are using 15. What is Build Verification and why
we go for it 16. What is Defect density 17. What is Integration testing 18. What
is Static testing and types of Static testing 19. What is Validation testing 20
. what is Data driven testing and why we go for data driven testing 21. what is
the definition of Testing 22. What is Sanitation Testing
TESTING INTERVIEW QUESTIONS (SECOND ROUND) 1. 2. 3. 4. 5. What are joins and sub
joins in the data bases what is data driven testing what is verification and val
idation What is Quality Assurance (QA) and Quality Control (QC) Is Verification
is related to QA and Validation is related to QC ?
6. which type of model you follow basically in your project 7. what is a use cas
e 8. How to test a Bike 9. how to test a Lift (Elevator). 10. which configuratio
n Management tool do you use 11. which Bug tracking tool do you use 12. explain
Bug life cycle 13. what is Regression testing 14. what is ALPHA testing ans BETA
testing 15. What types of testings comes under Non functional testing 16. what
is TEST DIRECTOR 17. what is CMM and CMM i 18. whar are Expressions in Winrunner
19. What is a Compile module 20. Is it Necessary to open the tool first or the
application first 21. after getting a bug what will you do 22. if you add a new
object or a new module for the existing application then how will you test the a
pplication 23. which Defect tracking tool do you use 24. what is change manageme
nt 25. What is smoke Testing 26. what is sanity testing 27. A application is giv
en to you but the requirements and functionalities are missing what will you do
to start the testing 28. which testing documents will be received by the client
SYNCOTA INTERVIEW QUESTIONS 1.what is a test plan 2.Actually when will be the te
sting people will be involved in the project 3.Define low priority and high seve
rity 4.Whom do you report the Bugs 5.what are the contents present in a test pla
n 6.which model will you follow 7.Which Bug tracking tool do you use and what ar
e the contents present in it 8.If a bug is reported what will be the Next work d
one 9. How to write test cases using Use case diagrams 10.For a given condition
(X>=0<100) how many test cases you can write ACCENTURE INTERVIEW QUESTIONS 1.wha
t is BVA and ECP 2.Do we have recovery manger in Winrunner 3 how does the winrun
ner recognizes the project 4 how is winrunner is used in the project
BLUESTAR INFOTECH INTERVIEW QUESTIONS 1. 2. 3. 4. 5. 6. What is the difference b
etween Sleep and wait in winrunner what is integration testing and types of test
ing present what is system testing what is data driven testing what is functiona
lity testing if requirements are given to you then how do you write the test cas
es for it
Account number = Ok cancel For above given form the valid account number starts
from 1 to 1000 so is it necessary to input the 1,2,3 ….998,999,1000 test cases t
o check the conditions of valid account numbers I,e is it compulsory to write 10
00 test cases for the above form
STAG SOFTWARE INTERVIEW QUESTIONS 1.what are the types of recording modes in win
runner 2.what are the three modes of running a test in winrunner 3.what is synch
ronization point 4.what are the contents present in a test case 5.do we need tes
ting for the project 6.what is code review and code walk through 7. At which pha
se the testing starts (begin) in the project 8. How do we test Client server app
lications and a Web applications 9. what is verification and validation 10. what
is adhoc testing 11. what is traceability matrix 12. what is base line document
13. what is Test Life Cycle 14. what is regression testing and retesting 15. wh
at is a BUG LIFE CYCLE 16. what is a Bug 17. what are defects 18. what is functi
onality testing and system testing. 19. a project has to be released in one day
but the testing people got that project from the developers half of the day befo
re so what they have to do to complete the testing process. 20 what are severity
level and priority levels
AZTEC SOFTWARE INTERVIEW QUESTIONS 1. What is BVA and ECP 2. Which version of WI
NRUNNER and QTP you are using in the project 3. What is the use of Recovery mana
ger in QTP 4. What is retesting and regression testing 5. Write the SQL queries
for the following EMP table to select the employee id and his details from emp t
able 6. For example: employee dept and employee id and employee name and employe
e salary 7. what is a sub and what is a driver 8. What are your roles and respon
sibilities in navathi_0522@yahoo.com cell:9949035183 # September 18, 2006 11:55
AM
Praveen Kumar.N said: TESTING INTERVIEW QUESTIONS 1. Explain Classical water fal
l model 2. Integration testing is conducted by developers or testers 3. an appli
cation is given how do you test for example the money deposited in account no.2
should be transferred to Account no.1 Account no: 1 Account no: 2 Ok Cancel 4. w
hat is V model 5. What is BUG life cycle 6. What is alpha testing and beta alpha
testing 7. What is verification testing and validation testing 8. What are ISO
and CMM standards levels 9. Which should be given more preference I.e. severity
or priority ? 10. How to use the test director in your project 11. What is use o
f recovery manager in QTP 12. What are the add ins in QTP 13. What are expressio
ns in QTP 14. if the developers are not convinced with your bug in this case wha
t will you do
15. if the developers are developing the application then what is the job assign
ed to the testers 16. What is system testing 17. What is smoke testing 18. What
is sanity testing 19. What is sanitation testing # September 18, 2006 11:56 AM
Iqbal Shaikh said: Respected Madem, I am iqbal i have visited this site it is gr
eat, it really helps people specially the freshears. I am really thankfull to yo
u for providing this material. I have some questions of which i am not getting p
roper answers, can i get it form you. I yes please send me a mail i will let you
know the questions. Thank You. # October 1, 2006 5:00 AM Software Testing - Tes
ting Tools » Blog Archive » Automation Testing versus Manual Testing said: PingB
ack from http://www.bugtest.info/2005/automation-testing-versus-manualtesting.ht
ml # May 19, 2007 9:38 AM New Comments to this post are disabled © 2008 Microsof
t Corporation. All rights reserved. Terms of Use | Trademarks | Privacy Statemen
t