Professional Documents
Culture Documents
QA QC
1.works at organization level. 1.works at product level
2.comes out with new 2.Identifies the defects in the
techniquesto prevent the defects. project.
3.Reacts based on the feedback 3.inds the defects and logs them
from QC. for finding defects.
4.Identify tools required at 4.Use the tools provided by QC.
organization level
5.Does regular quality audits to 5.Conduct various testing
verify the adherenceto process by activitiesto check the quality of
each project. the s/w before it released to
client.
QA:
It is responsible to define the process,templates,guidelines and
checklists to develop the s/w.Quality Audit also comes under QA
activities.
QC:
It is responsiblefor checking the project quality through various
activities like executing tests,reviewing documents,verifying
checkilist.QC is nothing but testing team.
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.
few examples:
High Severity and Low Priority -> Application doesn't allow customer
expected configuration.
High Severity and High Priority -> Application doesn't allow multiple user's.
Low Severity and High Priority -> No error message to prevent wrong
operation.
Low Severity and low Priority -> Error message is having complex meaning.
1.High Severity -Low priority
Supposing, you try the wildest or the weirdest of operations in a
software (say, to be released the next day) which a normal user would
not do and supposing this renders a run -time error in the application,
the severity would be high.The priority would be low as the operations
or the steps which rendered this error by most chances will not be
done by a user.
2.Low Severity -High priority
An example would be- you find a spelling mistake in the name of the
website which you are testing.
Say, the name is supposed to be Google and its spelled there as
'Gaogle'.Though, it doesnt affect the basic functionality of the
software,it needs to be corrected before the release.
Hence, the priority is high.
3.High severity--- High Priority
A bug which is a show stopper.i.e, a bug due to which we are unable
to proceed our testing.
An example would be a run time error during the normal operation of
the software,
which would cause the application to quit abruptly.
4.Low severity --- low priority
Cosmetic bugs
18.what is basis for testcase review?
the main basis for the test case review is
1.testing techniques oriented review
2.requirements oriented review
3.defects oriented review.
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,then how you can report the bug?
While reporting this bug into bugtracking tool you will generate the
testcase means put the steps to reproduce the bug.
-Test deliverables
-Staffing plan
-Risks and contingencies
-Milestones and deliverables
-Approvals.
31.How you can decide the number of testcases are enough for
testing the given module?
1)There should be existing testcase for each and every functionality.
2)Each requirement must have its own testcase
3)Peer reviewe is done for the test cases
OR
The developed test cases are coverd all the functionality of the
application we can say testcases are enough.If u know the
functionality covered or not u can use RTM.
32.What is the difference between Retesting and Data Driven
Testing?
Retesting:it is manual process in which apllication will be tested with
entire new set of data.
DataDriven Testing(DDT)-It is a Automated testing process inwhich
application is tested with multiple test data.DDT is very easy
procedure than retesting because the tester should sit and need to
give different new inputs manually from front end and it is very
tedious and boring prodedure.
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 carefully 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.
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
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)
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.
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 control
Tool Mainly useful to developer, to storing code and maintains version
Copying a code from VSS By developer is called CHECK-IN Upload the
code in to VSS is called CHECK-OUT.
Driver testing:
in bottom up approach, small modules r developed.to test them a
dummy core module called driver is developed.
Example-intrst Amount=GetInterestAmount(1000,12,6)
If(intrstAmount=60){
Printf(“GetInterestAmount function is working fine”)
}
Else{
Printf(“GrtInterestAmount function is not working fine”)
}
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
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