Documentos de Académico
Documentos de Profesional
Documentos de Cultura
2.what is a bug?
A computer bug is an error, flaw, mistake, failure, or fault in a computer program
that prevents it from working correctly or produces an incorrect result.
7.If a bug has high severity then usually that is treated as high priority,then
why do priority given by testengineers/project managers and severity given
by testers?
High severity bugs affects the end users ....testers tests an application with the users
point of view, hence it is given as high severity.High priority is given to the bugs
which affects the production.Project managers assign a high priority based on
production point of view.
17.give me some example for high severity and low priority defect?
if suppose the title of the particular concern is not spelled corectly,it would give a
negative impact.eg ICICC is spelled as a tittle for the project of the concern
ICICI.then it is a high severity,low priority defect.
20.What is difference between the Web application testing and Client Server
testing?
Testing the application in intranet(withoutbrowser) is an example for client -server.
(The company firewalls for the server are not open to outside world. Outside people
cannot access the application.)So there will be limited number of people using that
application.
Testing an application in internet(using browser) is called webtesting. The application
which is accessable by numerous numbers around the world(World wide web.)
So testing web application, apart from the above said two testings there are many
other testings to be done depending on the type of web application we are testing.
If it is a secured application (like banking site- we go for security testing etc.)
If it is a ecommerce testing application we go for Usability etc.. testings.
26.If you have executed 100 test cases ,every test case passed but apart
from these testcase you found some defect for which testcase is not
prepared,thwn how you can report the bug?
While reporting this bug into bugtracking tool you will generate the testcase imean
put the steps to reproduce the bug.
27.what is the diffn betn web based application and client server application
The basic difference between web based application & client server application is that
the web application are 3 trier & client based are 2 trier.In web based changes are
made at one place & it is refelected on other layers also whereas client based
separate changes need be installed on client machine also.
36.what r the client side scripting languages and server side scripting
languages
client side scripting langages are
javascript,VbScript,PHP...etc
Server side Scripting languages are
Perl,JSP,ASP,PHP..etc
Clent side scipting languages are useful to validate the inputs or user actions from
userside or client side.
Server side Scripting languages are to validate the inputs at server side.
This scripting languages provide security for the application. and also provides
dynamic nature to web or client server application
cleint side scripting is good because it won't send the unwanted input's to server for
validation.from frontend it self it validated the user inputs and restricts the user
activities and guides him
37.if a very low defect (user interface )is detected by u and the developer
not compramising with that defect what will u do?
user interface defect is a high visibility defect and easy to reproduce.
Follow the below procedure
1.Reproduce the defect
2.Capture the defect screen shots
3.Document the proper inputs that you are used to get the defect in the derfect
report
3.send the defect report with screen shots,i/ps and procedure for defect
reproduction.
before going to this you must check your computer hard ware configuration that is
same as developper system configuration.and anlso check the system graphic drivers
are properly
installed or not.if the problem in graphic drivers the User interface error will come.
so first check your side if it is correct from your sidethen report the defect by
following the above method.
38.if u r only person in the office and client asked u for some changes and u
didn,t get what the client asked for what will u do?
Onething here is very important.Nobody will ask test engineer to change software
that is
not your duty,even if it is related to testing and anybody is not there try to listen
care fully if you are not understand ask him again and inform to the corresponding
people immediately.
Here the cleint need speedy service,we(our company) should not get any blame from
customer side.
39.how to get top two salaries from employee tables
Select * from emp e where 2>=(select count(*) from emp e where sal>e.sal) order
by desc sal.
40.How many Test-Cases can be written for the calculator having 0-9
buttons, Add,Equalto buttons.The testcases should be focussed only on add-
functionality but mot GUI.What are those test-cases?
Test-Cases for the calculator
so here we have 12 buttons totalie 0,1,2,3,4,5,6,7,8,9,ADD,Equalto -12 buttons
here u can press atleat 4 buttons at a time minimum for example 0+1= for zero u
should press 'zero' labled buttonfor plus u should press '+' labled buttonfor one u
should press 'one' labled buttonfor equalto u should press 'equalto' labled button
0+1=here + and = positions will not varyso first number position can be varied from
0 to 9 i.e from permutation and combinations u can fill that space in 10 waysin the
same waysecond number position can be varied from 0 to 9 i.e from permutation
and combinations u can fill that space in 10 ways
Total number of possibilities are =10x10=100
This is exhaustive testing methodology and this is not possible in all cases.
In mathematics we have one policy that the the function satisfies the starting and
ending values of a range then it can satisfy for entire range of values from starting to
ending.
then we check the starting conditions i.e one test case for '0+0=' (expected values
you know thatis '0')then another testcase for '9+9='(expected values you know
thatis '18')only two testcases are enough to test the calculator functionality.
42.How will you prepare Test plan. What are the techniques involved in
preparing the Test plan.
Test plan means planning for the release. This includes Project background
Test Objectives: Brief overview and description of the document
Test Scope: setting the boundaries
Features being tested (Functionalities)
Hardware requirements
Software requirements
Entrance Criteria (When to start testing):
Test environment established, Builder received from developer, Test case prepared
and reviewed.
Exit criteria (when to stop testing):
All bug status cycle are closed, all functionalities are tested, and all high and medium
bugs are resolved.
Project milestones: dead lines
47.In which way tester get Build A, BUild B, ....Build Z of an application, just
explain the process..
After preparation of testcases project manager will release software release note in
that Document there will be URL path of the website link from from that we will
receive
the build In case of web server projects, you will be provided with an URL or a
92.168.***.*** (Web address) which will help you access the project using a
browser from your system.
In case of Client server, the build is placed in the VSS (Configuration tool) which will
help you get the .exe downloaded to your computer.
1.Build No
2.Version Name
3.Client OS
4.Feature set
5.Main Feature
6.Defined Testcases on each feature.
7.QA engineer Name
8.Test ecases executed.(Includes pass and fail)
9.Testcases on HOLD(Includes blocking testcases and deferred Testcases)
10.Covereage Report(Which includes the coverage ratings in % ,like % of testcases
covered,% of testcases failed)
Coming to Test report,generally we will prepare Test report ,once we rolled out the
product to our client.This document will be prepared by TL and delivered to the
client.Mainly,this document describes the what we have done in the
project,chievements we have reached,our
learnings in throughout the project etc...The other name for Test report is Project
Closure Report and we will summerize the all the activities,which have taken place in
through out the project.Here I am giving your the contents covered in the Test
Report.
1.Test Environment(Should be covered the OS,Application or webservers,Mahchine
names,Database,etc...)
2.Test Methods(Types of Tests,we have done in the project like Functional
Testing,Platform Testing,regression Testing,etc..
3.Major areas Covered.
4.Bug Tracking Details.(Includes inflow and outflow of the bus in our delivered
project)
5.Work schedule(When we start the testing and we finished)
6.Defect Analasys
6.1 Defects logged in different types of tests like Funcational Test,regressiion Test as
per area wised.
6.2 State of the Defects at end of the Test cycle.
6.3 Root cause analysys for the bugs marked as NOT A BUG.
7.QA observations or learnings throught the life cycle.
HIGH LEVEL TC
1.Verify that User is able to login with valid login and valid password.
2.Verify that User is not able to login with invalid login and valid password.
etc...
..
3.Verify that Reset button clears the filled screen.
4.Verify that a pop up message is displayed for blank login.
etc...
etc..
LOW LEVEL TC
1.Verify that after launching the URL of the application below fields are displayes in
the screen.
1.Login Name 2.Password.3.OK BUTTON 4.RESET button etc..
5.check box,provided for the label "remember my pwd" is unchecked.
2.Verify that OK button should be disabled before selecting login and passwrod
fields.
3.Verify that OK button should ne enabled after selecting login and password.
4.Verify that User is able to check the check box,providedfor the label "remember my
pwd".
etc..
In this way,we can categorise all the testcases under HIGH LEVEL and LOW LEVEL.
56.if a project is long term project , requirements are also changes then test
plan will change or not?why
Yes..definitely. If requirement changes, the design documents, specifications (for
that particualr module which implements the requiremnts) will also change. Hence
the test plan would also need to be updated. This is because "REsource Allocation" is
one section in the test
plan. We would need to write new test cases,review, and execute it. Hence resource
allocation would have to be done accordingly. As a result the Test plan would change
57.explain VSS
Virtual Sourse Safe...
After complition of all phages From devolopment side devoloper store the code in
devolopment folder of VSS,Testing team copying code from that folder to testing
folder, after compliting above phages from testing, testers put the build in base line
folder.It is version contrrole Tool
Mainly useful to devoloper, to storing code and maintains version Copying a code
from VSS By devoloper is called CHECK-IN Upload the code in to VSS is called
CHECK-OUT.
66.How do you select test cases for Regression Testing(The point is when
there is change code how do you come know which part of code or modules
it will affect).
Consider an example of a form which has a username,password and and Login
button.
There is a code change and a new button "Reset" is introduced. Regression
testing(for that build) will include testing only the "Login" button and not the Reset
button (testing Reset button will be a part of cunation testing). Hence the Regression
tester need not worry about the change in code,functionality. But he has to make
sure that the existing functionality is working as desired.Testing of "Reset" button
will be included as a part of Regression, for the next build
67.can any one explain the example of high servity and low priority, low
servity and high priority, high servity andhigh priority, low servity and low
priority
1.high severity and high priority. Database connectivity cannot be established by
multiple users.
2. low severity and low priority. Small issues like, incorrect number of decimal digits
in the output.
3. low severity and high priority. Images not updated.
4. high severity and low priority. In a module of say 2 interfaces, the link between
them is broken or is not functioning.
(1)High priority & High Severity:If u click on explorer icon or any other icon then
system crash.
(2)low prority & low severity:In login window ,spell of ok button is "Ko".
(3)Low priority & high serverty:In login window ,there is an restruction login name
should be 8 character if user enter 9 or than 9 in that case system get cresh.
(4)High priority & low severty :Suppose logo of any brand company is not proper in
their product.so it affect their business.
68.what will be the Test case for ATM Machine & Coffe Machine?
test cases for ATM Machine
1.successful insection of ATM card
2.un successful operation due to insert card in wrong angle
3.un successful operation due to invalid account Ex:other bank card or time expired
card
4.successful entry of PIN number
5.un successful operation due to enter wronr PIN number 3times
6.successful selection of language
7.successful selection of account type
8.un successful operation due to invalid account type
10.successful selection of withdral operation
11.successful selection of amount to be withdral
12.successful withdral operation
13.unsuccessful withdral operation due to wrong denominations
14. unsuccessful withdral operation due to amount is greaterthan day limit
15.unsuccessful withdral operation due to lack of money in ATM
16. unsuccessful withdral operation due to amount is greaterthan possible balance
17.unsuccessful withdral operation due to transactions is greaterthan day limit
18. unsuccessful withdral operation due to click cancel after insert card
19.unsuccessful withdral operation due to click cancel after insert card & pin number
20.unsuccessful withdral operation due to click cancel after insert card , pin number
& language
21.unsuccessful withdral operation due to click cancel after insert card , pin number ,
language &account type
22.unsuccessful withdral operation due to click cancel after insert card , pin number ,
language ,account type & withdral operation
23.unsuccessful withdral operation due to click cancel after insert card , pin number ,
language ,account type ,withdral operation &amount to be withdral
5.testing
6.delivery and maintainance
In the initial phase project manager can prepare a document for the requirements,
team leader will prepare a team which is having test engineers, developer will
provided by the project manager, testee will prepare test cases for that particular
project
Analysis phase all the members have a meeting to finalise the technology to develop
that project, the employee, time ,...
Designing phase the project manager like senior level management will give the
directions and source code to the team members to develop the actual code, that is
guidelines will be given in this phase
Coding phase developer will develop the actual code using the source code and they
release the application to the testee
Testing phase they deploy their test cases to that application and prepare a bug
profile document if there is any defect/bug in that application and send it back to
developer, developer may rectify and releases tha application as nezt build and if the
bug not undestand it will send to the prject lead in the delivery phase the sr test eng
can deploy the application in the client environment
Maintainance phase if the client get any prblem with the application it may solved by
the prject lead withe help of testers and developers
77.what are the document needed to create a test case?How u tell it is test
case?
System requirements specification, Use case document, Test Plan
78.in customer details form having fields like customer name,customer
address. after completion of this module, client raise the change as insert
the two radio buttons after customer address. how you can check as a
tester.
1.First we need to verify wheater the radio button are there are not?
2.Conform the radio buttons are present after the customer address or not.
3.verify the no of radio button.
4. verify only one radio button should be checked intially when we open the
Customer details form(if it is mentioned in FS )
5. verify the functionality of the radio buttons i.e if we check one ratio button
,second radio button should be unchecked.
6. verify the spell check of radio button lable name.
7. verify the allignment of radio buttons in the form.
79.at the time of testing web based applications and client server
apllications, what you absorved as a tester?
We generally check for the links,data retrieving and posting.
We perform load and stress testing especially for Web based and Client-Server
applications.
85.What is the difference between low and high level test cases? examples
please..
High level Test cases are those which covers major functionality in the application
(i.e retrive, update display ,cancel (functionality related testcases) ,database
testcases ).
Low level test cases are those which are related to UI related testcases.
86.Is it mandatory to use USECASES or directly one can write test casesfrom
requirments?
Its not mandatory to write Use Cases, If the requirements are clear you can go
ahead with Test Cases. Use Cases are written to know the business flow of the
module/application.
92.What is the difference between Project Based Testing and Product Based
Testing?
Project based is nothing but client requirements. product based is nothing but
market requirements. Ex.striching shirt is a project based and ready made shirt is
product based
93.what is testing process in related to Application testing Testing process is the one
which tells you how the application should be tested in order to minimize the bugs in
the application.
One main thing no application can be released as bug free application which
impossible.
107.If there is no sufficent time for testing & u have to complete the testing
then what will u do?
When I have less time to test the Product then I will take these following steps---
1) Sanity or smoke testing
2) Usabilty Testing
3) Formal Functionaltyand GUI Testing
4) Walkthrough with the Prduct
112. What are test case formats widely use in web based testing?
A. Web based applications deal with live web portals. Hence the test cases can be
broadly classified as. front end , back end, security testing cases, navigation based,
field validations, database related cases. The test cases are written based on the
functional specifications and wire-frames.
113. How to prepare test case and test description for job application?
A. Actually the question seems to be vague,... see naukri is one of biggest job site
globally and it has is own complex functionality normally a Test case is derived from
a SRS (or) FRS basically and test description is always derived from a Test case. Test
description is nothing but the steps which has to be followed for the TC what u
wrote. And the TC is nothing which compares the expectation and the
actual(outcome)result.
114. What is the difference between Functional and Technical bugs? Give an
example for each.?
Functional Bugs : Bugs found when Testing the Functionality of the AUT.
Technical bugs: Related to Communication which AUT makes.Like H/W,DB ! where
these could not be connected properly.
For small groups or projects, a more ad-hoc process may be appropriate, depending
on the type of customers and projects. A lot will depend on team leads or managers,
feedback to developers, and ensuring adequate communications among customers,
managers, developers, and testers.
The most value for effort will often be in (a) requirements management processes,
with a goal of clear, complete, testable requirement specifications embodied in
requirements or design documentation, or in 'agile'-type environments extensive
continuous coordination with end-users, (b) design inspections and code inspections,
and (c) post-mortems/retrospectives.
119. Why is it often hard for management to get serious about quality
assurance?
Solving problems is a high-visibility process; preventing problems is low-visibility.
This is illustrated by an old parable: In ancient China there was a family of healers,
one of whom was known throughout the land and employed as a physician to a great
lord.
129. What’s the difference between functional testing, system test, and
UAT?
Functional Testing:- testing that ignores the internal mechanism of a system or
component and focuses solely on the outputs generated in response to selected
inputs and execution conditions. this is a black box testing.
System Testing:- System testing is black box testing, performed by the Test Team,
and at the start of the system testing the complete system is configured in a
controlled environment. The purpose of system testing is to validate an application's
accuracy and completeness in performing the functions as designed. System testing
simulates real life scenarios that occur in a "simulated real life" test environment and
test all functions of the system that are required in real life. System testing is
deemed complete when actual results and expected results are either in line or
differences are explainable or acceptable, based on client input.
UAT:- Acceptance testing is black box testing that gives the client/ customer/ project
manager the opportunity to verify the system functionality and usability prior to the
system being released to production. The acceptance test is the responsibility of the
client/customer or project manager, however, it is conducted with the full support of
the project team. The test team also works with the client/customer/project manager
to develop the acceptance criteria.
· Expected results.
Test cases will be prepared by the tester based on BRD & FS.
135. What other groups did you interact with (developers, users, analysts)
Who would you rather work with?
Analysts
140. What is the difference b/w unique key and primary key?
ANS: Unique allows single Null, Primary Key doesn't allow Null. Primary key only
allows Foreign Key mapping.
144. What type of testing u perform first while doing BLACK BOX testing ?
ANS: It depends on the project and time availability. If it is a normal project with
comfortable time lines, we start the testing with UI and validations. These are also
called as Unit Level checks.
152. How can u identify by seeing the web page that it is a security?
ANS: when we open the any security site , it automatically use the HTTPS protocol
(HYPER TEXT TRANSFER PROTOCAL secure) HTTPS is an encrypted form of HTTP
used for sending sensitive data like credit card numbers between the browser and
the web server. This is also sometimes called Secure HTTP or SSL (which stands for
Secure Sockets Layer).
158. What is the best test case that you have written in your project till
now?
ANS: Pls pick a testcases which has data dependency b/w two different projects.
161. What are the concepts a test engineer should have knowledge of?
ANS: Windows/Database/ Web/ManualTesting (TestPlan,TestCases, diff phases of
testing, Bug)/One automation tool.
Q - How to prepare test case and test description for job application?
A - Actually the question seems to be vague,... see naukri is one of biggest job site globally and it
has is own complex functionality normally a Test case is derived from a SRS (or) FRS basically
and test description is always derived from a Test case. Test description is nothing but the steps
which has to be followed for the TC what u wrote. And the TC is nothing which compares the
expectation and the actual(outcome)result.
Q - What is the difference between Functional and Technical bugs? Give an example for
each.?
Functional Bugs : Bugs found when Testing the Functionality of the AUT.
Technical bugs: Related to Communication which AUT makes.Like H/W,DB ! where these could
not be connected properly.
Q - Give proper Seq. to following testing Types Regression, Retesting, Funtional, Sanity
and Performance Testing.?
A - The proper sequence in which these types of testing are performed is - Sanity, Functional,
Regression, Retesting, Performance.
Verification typically involves reviews and meetings to evaluate documents, plans, code,
requirements, and specifications. This can be done with checklists, issues lists, walkthroughs,
and inspection meetings. Validation typically involves actual testing and takes place after
verifications are completed. The term 'IV & V' refers to Independent Verification and Validation.
A lot depends on the size of the organization and the risks involved. For large organizations with
high-risk (in terms of lives or property) projects, serious management buy-in is required and a
formalized QA process is necessary.
Where the risk is lower, management and organizational buy-in and QA implementation may be a
slower, step-at-a-time process. QA processes should be balanced with productivity so as to keep
bureaucracy from getting out of hand.
For small groups or projects, a more ad-hoc process may be appropriate, depending on the type
of customers and projects. A lot will depend on team leads or managers, feedback to developers,
and ensuring adequate communications among customers, managers, developers, and testers.
The most value for effort will often be in (a) requirements management processes, with a goal of
clear, complete, testable requirement specifications embodied in requirements or design
documentation, or in 'agile'-type environments extensive continuous coordination with end-users,
(b) design inspections and code inspections, and (c) post-mortems/retrospectives.
Q - Why is it often hard for management to get serious about quality assurance?
Q - What's an 'inspection'?
An inspection is more formalized than a 'walkthrough', typically with 3-8 people including a
moderator, reader, and a recorder to take notes.
The subject of the inspection is typically a document such as a requirements spec or a test plan,
and the purpose is to find problems and see what's missing, not to fix anything. Attendees should
prepare for this type of meeting by reading thru the document; most problems will be found during
this preparation. The result of the inspection meeting should be a written report.
Q - What is a 'walkthrough'?
A 'walkthrough' is an informal meeting for evaluation or informational purposes. Little or no
preparation is usually required.