Question bank for CT1

1.Define following
1. Bug
The presence of error at the time of execution of the software.
2. Failure
Deviation of the software from its expected result.
3. Fault
State of software caused by an error.

2.Define software testing.

Testing is the execution of programs with an intention of finding
defects.OR Software testingis a process, to evaluate the functionality of
a software application with an intent to find whether the developed
software met the specified requirements or not and to identify the defects
to ensure that the product is defect-free in order to produce the quality
product.

3.Why do bug occur?

Requirements: 1) Constantly changing requirements.
2) Requirements not gathered properly
Specification: 1) Not written properly
2) Constantly changing
3) Not well communicated
Design:1) Not done properly
2) Quickly done
Coding: 1) Inexperienced programmer/Programmers without proper
domain knowledge
2)Software Complexity
3) Programmers are not following standards
4) Schedule Pressure or plain dumb mistake

4.Difference between QA and QC

Quality Assurance Quality Control
QA is the process of managing QC is used to verify the quality of
for quality. the output.
Activities of QA are Process Activities of QC are Reviews and
Definition and Implementation, Testing
Audits and Training
It includes Prevention oriented It includes detection-oriented
activities. activities.
Verification is an example of QA Verification is an example of QA
QA is a managerial tool QC is a corrective tool

5.Difference between Verification and Validation.

Verification Validation
Verification is a static practice of Validation is a dynamic
verifying documents, design, code mechanism of validating and
and program. testing the actual product.
It does not involve executing the It always involves executing the
code. code.
It is human based checking of It is computer-based execution of
documents and files. program.
Verification is to check whether Validation is to check whether
the software conforms to software meets the customer
specifications. expectations and requirements.
Verification is done by QA team to Validation is carried out with the
ensure that the software is as per involvement of testing team.
the specifications in the SRS
document.
 It generally comes first-done It generally follows after
before validation. verification.

6.Diffrernce between static testing and Dynamic testing.

Static Testing Dynamic Testing
Testing is done without executing Testing is done by executing the
the program program
Static testing gives assessment of Dynamic testing finds bugs in the
code and documentation software application
It is performed in the early stage It is performed at the later stage of
of the software development. the software development.
Cost of fixing bug is low Cost of fixing is high
Example: Inspection, walkthrough Example: Boundary value
analysis, Equivalence Partitioning

7.Give classification Whitebox Testing.

8.Explain walkthrough.
Aim: To review code or documents and to find defects in order to
improve quality of the product.
•More formal method than peer review.
•Presenter: Presented by author
•Review artifacts: Requirement specification, architectural documents,
diagrams or piece of code.
•Participants: Author, programmers or testers, senior programmer etc.

9.Explain boundary value analysis with example.

Most of the defects in software products hover around conditions and
boundaries. Boundary value analysis is another black box test design
technique and it is used to find the errors at boundaries of input domain
rather than finding those errors in the center of input. Each boundary has
a valid boundary value and an invalid boundary value. Test cases are
designed based on the both valid and invalid boundary values. Typically,
we choose one test case from each boundary.

10.Explain Equivalence partitioning with example.

Equivalence partitioning (EP)is a specification-based or black-box
technique. •It can be applied at any level of testing and is often a good
technique to use first.
•The set of input values that generate one single expected output is
called apartition.
•In equivalence-partitioning technique we need to test only one condition
from each partition.
•This is a software testing technique which divides the input date into
many partitions. Values from each partition must be tested atleast once.
Partitions with valid values are used for Positive Testing. While,
partitions with invalid values are used for negative testing.
Example:
11. Draw diagram for levels of testing

12.Explain unit testing.

Unit Testing is a level of software testing where individual units/
components of a software are tested. Purpose is to validate that each
unit of the software performs as designed. Unit Testing is the first level of
testing.
➢A unit is the smallest testable part of software.
➢It is executed by the Developer.
➢Unit Testing is performed by using the White Box Testing method
➢Example: -A function, method, Loop or statement in program is
working fine.
13. Draw diagram for integration testing approaches.

13. Give performance testing approaches.

Performance testing is a non-functional software testing technique
that determines how the stability, speed, scalability, and
responsiveness of an application holds up under a given workload.
Performance testing is intended to find whether the system meets its
performance requirements under normal load or abnormal level of
activities. The subtypes of Performing testing are Load Testing,
Stress Testing and Security Testing.

14. Differentiate between alpha and beta testing(4points).

Alpha Testing Beta Testing
Testing is done by end user at Testing is done by end user at
developer site. end user site
It is done in controlled Developer is not present so not
environment. done in controlled environment.
Alpha testing is not effective as it Beta test is more effective as
is done in controlled end user do not have any
environment. restriction of testing software.
 End user may have to test Beta testing is live application
software under influence of testing, not done in influence of
developer. developer.

16.What are the black box testing techniques.

1) Requirement based testing
2)Boundary value analysis
3)Equivalence Partitioning

17. When to start and stop testing.

The conditions or situations which may be seen as an entry criteria for
the initiation of testing activities.
•Requirements should be clearly defined and approved.
•Test Design and documentation plan is ready.
•Availability of the test environment supporting necessary hardware,
software, network configuration, settings and tools for the purpose of test
execution.
•Testers are trained and necessary resources are available.
•Availability of proper and adequate test data(like test cases).
•It depends upon which software development model is used.
Exit Criteria is often viewed as a single document concluding the end of
a life cycle phase. The conditions or situations which may be seen as an
exit criteria for testing activities.
•Testing Deadline
•Completion of test case execution.
•Completion of Functional and code coverage to a certain point.
•Bug rates fall below certain level and no high priority bugs are identified.
•Management decision.