1- Testing life cycle:

Requirement Analysis
Test Planning
Test case development
Test Environment setup
Test Execution
Test Cycle closure

2- Testing levels and types:

Levels:
Unit
Component
Integration
System
Acceptance
Types:
Functional Testing
Non-Functional Testing
White-box Testing
Change-related Testing
Confirmation
Regression

3- Defect Report
A defect report filed during dynamic testing typically includes:
 An identifier
 A title and a short summary
 Date of the defect report, issuing organization, and author
 environment
 The development lifecycle phase(s) in which the defect was observed
 A description of the defect to enable reproduction and resolution, including logs, database
dumps screenshots, or recordings (if found during test execution)
 Expected and actual results
 degree of impact (severity) of the defect on the interests of stakeholder(s)
 Urgency/priority to fix Certified Tester Foundation Level Syllabus International Software
 State of the defect report (e.g., open, deferred, duplicate, waiting to be fixed, awaiting
confirmation testing, re-opened, closed)
 Conclusions, recommendations and approvals
 Global issues, such as other areas that may be affected by a change resulting from the defect
 Change history, such as the sequence of actions taken by project team members with respect
to the defect to isolate, repair, and confirm it as fixed
 References, including the test case that revealed the problem
4- Defect life cycle
New
Assigned
Open
Fixed or Rejected
Ready for test
Retest Passed or Failed
Closed or Re-opened
5- Priority vs Severity
Severity is defined as the degree of impact a Defect has on the development or operation of a
component application being tested.
Priority is defined as the order in which a defect should be fixed.
6- Test Matrix:
Test matrix is used to capture actual quality, effort, the plan, resources and time required to
capture all phases of software testing
7- Requirement trackability matrix
The relationship between test cases and requirements is shown with the help of a document.
This document is known as a traceability matrix.
8- What is white box testing and list the types of white box testing?
White box testing technique involves selection of test cases based on an analysis of the internal
structure (Code coverage, branches coverage, paths coverage, condition coverage, etc.) of a
component or system. It is also known as Code-Based testing or Structural testing. Different
types of white box testing are
- Statement Coverage
- Decision Coverage
9- Explain what Test Plan is? What is 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.
o Test Strategy
o Test Objective
o Exit/Suspension Criteria
o Resource Planning
o Test Deliverables
10- On what basis you can arrive at an estimation for your project?
- To estimate your project, you have to consider the following points
o Divide the whole project into the smallest tasks
o Allocate each task to team members
o Estimate the effort required to complete each task
o Validate the estimation

11- Ambiguity analysis

Ambiguity results from unclear or incomplete/inadequate critical information in the
requirements or in their interpretation. ... And, it is extremely critical to review all ambiguous
 requirements at an early phase to reduce costs and delays in timelines and to create
valid test cases and build good quality software
12- Webservices types
SOAP and REST
13- XML schema
is a description of a type of XMLdocument, typically expressed in terms of constraints on the
structure and content of documents of that type, above and beyond the basic syntactical
constraints imposed by XML itself
14- WSDL file
The Web Services Description Language is an XML-based interface description language that is
used for describing the functionality offered by a web service.
15- technical challenge
16- How to overcome the challenge of not having input documentation for testing?
IF the detailed standard documentation like BRD and FSD are unavailable, the tester will have
to depend on some point of reference.
a) Screenshots
b) A previous version of the application
c) Wireframes …etc

Database

1- difference between where and having

The HAVING clause was added to SQL because the WHERE keyword could not be used with
aggregate functions.
2- tables relationship types (recursive relationship)
One to One
One to Many
Many to Many
Recursive

3- SQL constraints
NOT NULL - Ensures that a column cannot have a NULL value
UNIQUE - Ensures that all values in a column are different
PRIMARY KEY - A combination of a NOT NULL and UNIQUE. Uniquely identifies each row in a
table
FOREIGN KEY - Uniquely identifies a row/record in another table
CHECK - Ensures that all values in a column satisfies a specific condition
DEFAULT - Sets a default value for a column when no value is specified
INDEX - Used to create and retrieve data from the database very quickly
4- primary key and forgiven key
PRIMARY KEY - A combination of a NOT NULL and UNIQUE. Uniquely identifies each row in a
table
FOREIGN KEY - Uniquely identifies a row/record in another table
5- unique identifier
UNIQUE - Ensures that all values in a column are different