1.Differentiate
between QA and QC?
QA:It
is process oriented
it envolve in entire process of software
developement.
Preventin oriented.
QC:
It is product oriented.
work to examin the quality of product.
Dedection orientd.
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.
3.What
is a test case?
Test
case is set of input values, execution preconditions, expected results and
execution post conditions, developed for a particular objective or test
conditons, such as to exercise a paticular program path or to verify compliance
with a specific requiremnt.
4.What
is the purpose of test plan in your project?
Test
plan document is prepared by the test lead, it contains the contents like
introduction, objectives, test strategy, scope, test items, program modules
user procedures, features to be tested features not to tested approach, pass or
fail criteria, testing process, test deliverables, testing, tasks, responsibilities,
resources, schedule, environmental requirements, risks & contingencies, change
management procedures, plan approvals, etc all these things help a test manager
understand the testing he should do & what he should follow for testing
that particular project.
5.When
the relationship occur between tester and developer?
developer
is the one who sends the application to the tester by doing all the necessary
code in the application and sends the marshal id to the tester.The tester is
the one who gives all the input/output and checks whether he is getting reqd
output or not.A developer is the one who works on inside interfacing where as
the tester is the one who works on outside interfacing
6.What
is the MAIN benefit of designing tests early in the life cycle?
It helps prevent defects from being introduced into the code.
It helps prevent defects from being introduced into the code.
7.What is risk-based testing?
Risk-based testing is
the term used for an approach to creating a test strategy that is based on
prioritizing tests by risk. The basis of the approach is a detailed risk
analysis and prioritizing of risks by risk level. Tests to address each risk
are then specified, starting with the highest risk first.
8.A wholesaler sells printer cartridges. The
minimum order quantity is 5. There is a 20% discount for orders of 100 or more
printer cartridges. You have been asked to prepare test cases using various
values for the number of printer cartridges ordered. Which of the following
groups contain three test inputs that would be generated using Boundary Value
Analysis?
4, 5, 99
9.What is the KEY
difference between preventative and reactive approaches to testing?
Preventative tests
are designed early; reactive tests are designed after the software has been
produced.
10.What is the purpose of exit criteria?
The
purpose of exit criteria is to define when a test level is completed.
11.Traceability Matrix?
Traceability
matrix nothing but it contains table of linking information. Which is used for
tracing back for the reference whenever there is a questionable situation
12.Test Case-definition and prepared
by whom?
Test case is nothing but it is an idea of test engineer based on the customer
requirements. Prepared by test engineer
13.Use Case-definition and prepared
by whom?
Use case is nothing but it will describe the all the functionalities in the
application. Prepared by business analyst
14.Test Plan- definition and
prepared by whom?
Plan is a strategic document which describes how to perform a task in
effective, efficient and optimized way. Test plan prepared by test lead
15.Seviority and Priority?
Seviority:
seviority is nothing but seriousness of the defect
Priority:
in what sequence defect has to be rectified
16.Explain what is Test
Plan ? What are the information that should be covered in Test Plan ?
A test plan can be
defined as a document describing the scope, approach, resources and schedule of
testing activities and a test plan should cover the following details.
- Test Strategy
- Test Objective
- Exit/Suspension Criteria
- Resource Planning
- Test Deliverables
17. How you can
eliminate the product risk in your project ?
To eliminate product
risk in your project, there is simple yet crucial step that can reduce the
product risk in your project.
- Investigate the specification documents
- Have discussions about the project with all stakeholders including the developer
- As a real user walk around the website
18. What are
the common risk that leads to the project failure?
The common risk that
leads to a project failure are
- Not having enough human resource
- Testing Environment may not be set up properly
- Limited Budget
- Time Limitations
19. On
what basis you can arrive to an estimation for your project?
To estimate your
project , you have to consider following points
- Divide the whole project into a smallest tasks
- Allocate each task to team members
- Estimate the effort required to complete each task
- Validate the estimation
20. Explain how
you would allocate task to team members ?
Task
|
Member
|
|
|
|
|
|
|
|
|
21.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
22.What is
meaning by protype in SDLC ?
This
is a cyclic version of the linear model. In this model, once the requirement
analysis is done and the design for a prototype is made, the development
process gets started.Once the prototype is created, it is given to the customer
for evaluation. The customer tests the package and gives his/her feed back to
the developer who refines the product according to the customer's exact expectation.
After a finite number of iterations, the final software package is
given
to the customer. In this methodology, the software is devolved as a result of
periodic shuttling of information between the customer and developer. This is
the most popular development model in the contemporary IT industry. Most of the
successful software products have been developed using this model - as it is
very difficult (even for a whiz kid!)to comprehend all the requirements of a
customer in one shot. There are many variations of this model skewed with
respect to the project management styles of the companies.
New
versions of a software product evolve as a result of prototyping.
23.what is
difference between desktop and web application?
The
biggest d/f b/w Desktop and web application is- Desktop App (DA) is the machine independent,
hence evry change has only reflects at the machine level. Where as Web App (WA) is the Internet
dependent program, hence any change in the program reflects at every where,
where it becomes use.
EX......Suppose there are 5 machines in DA, 5
time installedindividually at every machine and if there is any change made in
DA then at every machine change has to be made.
In WA where the program or Application at the Server or at the one common machine, then if changes made
at only central or server or common machine all the changes get reflected at every
client machine.
24.Difference
between application testing and product testing?
Product
testing means when any company does testing for their own (company's) product
ex... Nortan AntVirus is the Symantec's product; if Symantec test the Nortan
ie. Called as the Product testing. Where as if any company take some projects
from some other companies like ABC company takes projects from IBM and test
that project on some charges ie called as Application Testing.
25.what is a
broken link in web testing and how test it.
When
we clicked on Hyperlink if it opens Page can't be displayed then that Hyperlink
is called as Broken link
26.Bug Life Cycle?
Defect
life cycle is a cycle which a defect goes through during its lifetime
27.Bug,Defect,Error,failure-Definitions
and Differences?
Error:
When we get the wrong output i.e. syntax error, logical error
Fault: When everything is correct but we are not able to get a result
Failure: We are not able to insert any input or after deploying the application into client environment that time if it is not work then we can say failure
Fault: When everything is correct but we are not able to get a result
Failure: We are not able to insert any input or after deploying the application into client environment that time if it is not work then we can say failure
Defect: if it is not working as for the customer
expectations
28.RegressionTesting,Re-Testing,Adhoc
Testing--->Definitions?
Regression
: It is a type of testing in which one will
perform testing on the already tested functionalities again and again.
It is usually done in two
scenarios.
1. Whenever the testers has raised the defects, rectified by the
developers and next build is released to the testing department then the test
engineer’s will test the defect functionality as well as the related
functionality once again.
2. Whenever some new features are incorporated by the developers, next
build is released to the testing department then the test engineers will once
again test the related functionalities of the new features in order to confirm
that they are working same as previous.
Note: -
Testing the new functionalities for the first time is known as new testing but
not Regression Testing.
Retesting: It is a type of testing in which one will test the
same functionality again and again with different sets of values in order to
come to a conclusion whether it is working or not.
Adhoc
Testing: It is a type of testing
in which one will perform testing on the application in his own style after
understanding the requirements clearly.
29.SDLC(Software Development Life
Cycle)---phases?
Six
Phases:
1.Initial
phase(or)Requirement phase: in this phase they will gather the customer
requirements
2.Analysis
Phase: they will analyzing the customer requirements
3.Design
Phase: they will divide the whole project
4:Coding
phase: they will developing the script based on the customer requirements
5.Testing
phase: we will test the application
6.Delivery
and Maintenance phase:
They
will install or deployed or delivery the application in the client environment
30.STLC(Software Testing Life cycle)-----phases?
Six
phases:
1.TestPlaning: test plan prepared by test
lead. test pan having some contents
1.0 Introduction
1.1
Objective
1.2
Reference Document
1.0
Coverage Of Testing
1.1
Features To Be Testing
1.2
Features Not To Be Testing
3.0 Test Strategy
3.1
Levels Of Testing
3.2
Types of testing
3.3
Test design techniques
3.4
Configuration management
3.5
Test metrics
3.6
Terminology
3.7
Automation Plan
3.8
List of automated tools
4.0
Base
criteria
4.1 Acceptance
criteria
4.2 Suspension criteria
5.0 Test Deliverable
6.0 Test Environment
7.0 Resource Planning
8.0 Scheduling
9.0 Staffing& Training
10.0 Risks & Contingencies
11.0 Assumptions
12.0 Approval Information
2.Test
Development: we will write the test cases based on the customer requirements
3.Test
Execution: in this phase we will compare the expected value and actual value
4.Result
Analysis: if it is actual value is expected value then we will give status pass
Otherwise
we will raise the defect
5.Bug
Tracking: Defect life cycle is a cycle which a defect goes through during its
lifetime
6.Reporting:
we will raise the defect using defect profile template
Levels
of Testing:
1.Unit
Testing:
Unit is nothing but it is a smallest part of the
application.
It is a level of testing in which one will
perform testing on the units. It is a white box testing and usually developers
or white box testers will perform.
2.Module
Testing:
Module: Module is
defined as a group of related functionalities to perform a major task
It is a level of tasting
in which one will perform testing on the modules. It is a black box testing and
usually test engineers perform it.
3.Integration
Testing:
It is a level of testing
in which the developers will develop some interfaces to integrate the modules
and test whether the interfaces are working fine or not. It is a
white box testing usually developers or white box tasters perform.
The developers may follow one of the following approaches
while integrating the modules.
1.Top-down approach
2.Bottom –up approach
3.Hybrid or Sandwich approach
4.Bigbang approach
1.Top-down approach: -
In this approach one will develop the parent modules first and then integrate
them with the related child modules
2.Bottom-up approach: -
In this approach one will develop the child modules first and integrate them to
the parent modules
3.Hybrid approach Or
Sandwich approach:- This is a mixed approach of both the top down and bottom up
approaches
4.Big bang approach:-In
this approach one will wait till all the modules are ready and finally they
will integrate all the modules at a time
ÞSTUB: - While integrating the modules in top down
approach if at all any mandatory module is missing then that module is replace
with a temporary program known as STUB
ÞDRIVER: -While integrating the modules in bottom up
approach. If at all any mandatory module is missing then that module is
replaced with a temporary program known as DRIVER
4.System
Level Testing:
It is a level of testing
in which one will install the complete application in to the environment and
then perform testing on it. At this level different types of testing will be
done one among those is system integration testing.
5.User Acceptence Testing(U.A.B):
It is the level of testing in which one will perform
the same system testing in the presence of the user in order to make him accept
the application. It is a black box testing and usually Test engineer performs
it.
There
are two types of user acceptance testing’s available
1)alpha
testing
2)beta
testing
a a-
Testing (Alpha Testing): -
It is a
type of user acceptance testing in which the test engineers will test the
application in our company, in the presence of the customer.
Advantage:
- If at all any defects are found then there is a chance of rectifying them
immediately.
b-Testing
(Beta): -
It
is a type of user acceptance testing done in the clients place either by the end-users
or by the third party testing experts before actual implementation.
Drawback:
If at all any defects are found then there is no chance of rectifying them
immediately.
31.What determines the
level of risk?
The likelihood
of an adverse event and the impact of the event determine the level of risk.
32. When is used
Decision table testing?
Decision table
testing is used for testing systems for which the specification takes the form
of rules or cause-effect combinations. In a decision table the inputs are
listed in a column, with the outputs in the same column but below the inputs.
The remainder of the table explores combinations of inputs to define the
outputs produced.
33. What is the MAIN
objective when reviewing a software deliverable?
To identify defects
in any software work product.
34. Which of the
following defines the expected results of a test? Test case specification or
test design specification.
Test case
specification defines the expected results of a test.
35. What is the
benefit of test independence?
It avoids author bias
in defining effective tests.
36.when
testing will starts in a project?
the
testing is not getting started after the coding.after release the build the
testers perform the smoke test.smoke test is the first test which is done by
the testing team.this is according to the testing team.but, before the
releasing of a build the developers will perform the unit testing.
37.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.
38.what
is the difference between functional testing and regression testing
functional
testing is a testing process where we test the functionality/behaviour of each
functional component of the application...i.e.minimize button, transfer
button,l inks etc. i.e we check what is each component doing in that
application...
regression
testing is the testing the behaviour of the application of the unchanged areas
when there is a change in the build.i.e we check whether the changed requirement
has altered the behaviour of the unchanged areas.the impacted area may be the
whole of the application or some part of the application...
39.Do
u know abt integration testing,how do u integrate diff modules?
integration
testing means testing an application to verify the data flows between the
module.for example, when you are testing a bank application ,in account balence
it shows the
100$as
the available balence.but in database it shows the 120$. main thing is
"integration done by the developers and integration testing done by the
testers"
40. As part of
which test process do you determine the exit criteria?
The exit criteria is determined on the bases of 'Test Planning'.
41. What is
beta testing?
Testing performed by potential customers at their own locations.
42.
Given the following fragment of code, how many tests are required for 100%
decision coverage?
if width >
length
thenbiggest_dimension = width
if height > width
thenbiggest_dimension = height
end_if
elsebiggest_dimension
= length
if height > length
thenbiggest_dimension = height
end_if
end_if
4
43. You have
designed test cases to provide 100% statement and 100% decision coverage for
the following fragment of code. if width > length then biggest_dimension =
width else biggest_dimension = length end_if The following has been added to
the bottom of the code fragment above. print "Biggest dimension is "
&biggest_dimensionprint "Width: " & width print "Length:
" & length How many more test cases are required?
None, existing test
cases can be used.
44. Rapid
Application Development?
Rapid Application
Development (RAD) is formally a parallel development of functions and
subsequent integration. Components/functions are developed in parallel as if
they were mini projects, the developments are time-boxed, delivered, and then
assembled into a working prototype. This can very quickly give the customer
something to see and use and to provide feedback regarding the delivery and
their requirements. Rapid change and development of the product is possible
using this methodology. However the product specification will need to be developed
for the product at some point, and the project will need to be placed under
more formal controls prior to going into production.
45.If there is
no sufficient 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 Functionality and GUI Testing
4) Walkthrough with the Product
46.What is
meaning by prototype in SDLC ?
This
is a cyclic version of the linear model. In this model, once the requirement
analysis is done and the design for a prototype is made, the development
process gets started.Once the prototype is created, it is given to the customer
for evaluation. The customer tests the package and gives his/her feed back to
the developer who refines the product according to the customer's exact expectation.
After a finite number of iterations, the final software package is given to the
customer. In this methodology, the software is devolved as a result of periodic
shuttling of information between the customer and developer. This is the most
popular development model in the contemporary IT industry. Most of the
successful software products have been developed using this model - as it is
very difficult (even for a whiz kid!)to comprehend all the requirements of a
customer in one shot. There are many variations of this model skewed with
respect to the project management styles of the companies.
New
versions of a software product evolve as a result of prototyping.
47.what is
difference between desktop and web application?
The
biggest d/f b/w Desktop and web application is- Desktop App (DA) is the machine independent,
hence evry change has only reflects at the machine level. Whereas Web App (WA) is the Internet
dependent program, hence any change in the program reflects at every where,
where it becomes use.
EX......
Suppose there are 5 machines in DA, 5 time
installed individually at every machine and if there is any change made in DA
then at every machine change has to be made.
In WA where the program or Application at the Server or at the one common machine, then if changes made
at only central or server or common machine all the changes get reflected at every
client machine.
48.Difference
between application testing and product testing?
Product
testing means when any company does testing for their own (company's) product
ex... Norton AntiVirus is the Symantec's product; if Symantec test the Norton
ie. Called as the Product testing. Where as if any company take some projects
from some other companies like ABC company takes projects from IBM and test
that project on some charges ie called as Application Testing.
49.what is a
broken link in web testing and how test it.
When
we clicked on Hyperlink if it opens Page can't be displayed then that Hyperlink
is called as Broken link
boundry
value analusis is a technique for test data selection.Test engineer chooses the
values that lie along the data extreems.It includes max,mim,justinside,justout
side,typicalvalues and errorvalues.
Boundary
Value Analysis is a technique used for writing the test cases..for example:If a
particular field accepts the
values
from 1 to 1000, then we test that field by entering only 1, 1000, 0, 1001,
999,2.
i.e we
check on the boundaries and then
minimum-1
, minimum +1 and maximum+1, maximum-1.
No comments:
Post a Comment