1 mark

1- Loop testing: Loop Testing is defined as a software testing type, that completely focuses on the
validity of the loop constructs

2-Validation: It is a dynamic mechanism of testing and validating the actual product. It can find bugs
that the verification process cannot catch

3- Verification: The verifying process includes checking documents, design, code, and program. It
finds bugs early in the development cycle

4-Traceability matrix: It is a high-level document to map and trace user requirements with test cases
to ensure that for each and every requirement adequate level of testing is being achieved

5- Boundary value testing: Boundary value testing is focused on the values at boundaries. This
technique determines whether a certain range of values are acceptable by the system or not. It is
very useful in reducing the number of test cases. It is most suitable for the systems where an input is
within certain ranges.

6- Cause-effect graph: Cause Effect Graphing based technique is a technique in which a graph is used
to represent the situations of combinations of input conditions.

7- Application of cookies: Shopping Cart - Personalized Sites – Marketing - User Sessions

8- Grey box testing: is a software testing technique which is a combination of Black Box Testing
technique and White Box Testing technique

9- boundary value analysis: The basic idea in normal boundary value testing So these extreme ends
like Start- End, Lower- Upper, Maximum-Minimum, Just Inside-Just Outside values are called
boundary values and the testing is called "boundary testing".

10- Gray box testing process: 1-Identify inputs -2- Identify the outputs -3- Identify the major paths -
4- Identify Subfunctions -5- Develop inputs for Subfunctions -6- Develop outputs for Subfunctions -7-
Execute test case for Subfunctions -8- Verify the correct result for Subfunctions-9- Repeat steps 4 &
8 for other Subfunctions -10- Repeat steps 7 & 8 for other Subfunctions

4MARKS
1- types of loop test and why do loop testing?
 Types of loop Test:
a. Simple loop
b. Nested loop
c. Concatenated loop
d. Unstructured loop
 Loop Testing is done for the following reasons:
a. Testing can fix the loop repetition issues
b. Loops testing can reveal performance/capacity bottlenecks
c. By testing loops, the uninitialized variables in the loop can be determined
d. It helps to identify loops initialization problems
 2- Reasons for Operational risks
These risks occur due to failed system, external risks due to events and lack of process
implementation. Causes of Operational risks: Priority conflicts are not resolved properly.
Responsibilities have not been resolved properly.

3- Methods to calculate test metrics. Advantages and disadvantages of Statement coverage

 Calculated metrics is usually followed by the test manager for test reporting purpose (%
Complete, % Test Coverage).
 Advantage of statement coverage:
- It verifies what the written code is expected to do and not to do
- It measures the quality of code written
- It checks the flow of different paths in the program and it also ensure that whether
those paths are tested or not
 Disadvantage of statement coverage:
- It cannot test the false conditions.
- It does not report that whether the loop reaches its termination condition.
- It does not understand the logical operators.

6MARKS
1- explain about resource planning and its types

******//////

2- EXPLAIN ABOUT PROCESSES OF SOFTWARE TEST ENVIRONMENT SETUP

******/////
3- Why is RTM (Requirement traceability Matrix) is IMPORTANT?
- Requirement Traceability assures good ‘Quality’ of the application as all the features
are tested. 
- Requirement Traceability Matrix aids for software application getting tested in the
stipulated time duration, the scope of the project is well determined and its
implementation is achieved as per the customer requirements and needs and the
cost of the project is well controlled
- Defect Leakages are prevented as a whole of the application is tested for its
requirements
4- Which parameter is included for the RTM?
Requirements Traceability Matrix (RTM) is used to trace the requirements to the tests that
are needed to verify whether the requirements are fulfilled
5- differentiate the boundary value analyses test and equivalence class testing?
 Equivalence Class Testing: 
- It is used to minimize the number of possible test cases to an optimum level while
maintains reasonable test coverage.
- An equivalence class is a set or range of input domain values that can reasonably be
expected to cause “similar” responses from the application under test
- Test cases: In Equivalence class testing, we find two types of equivalence classes.
 Input domain
 Output domain
 - The key of equivalence class testing is the choice of the equivalence relation that
determines the classes
- Valid Equivalence Classes: It represents the valid input values to program under test
for which the system behaves correct/normal
- Invalid Equivalence Classes: This class represents the erroneous input values (i.e.
invalid/unexpected conditions). For these conditions, either the system should reject
them or it should escalate to user / do exception handling
- Input domain is formed from one valid sequence and two invalid sequences.
- The output domain is obtained from different types of output of a problem
 Boundary Value Testing: 
- Boundary value testing is focused on the values at boundaries. This technique
determines whether a certain range of values are acceptable by the system or not. It
is very useful in reducing the number of test cases. It is most suitable for the systems
where an input is within certain ranges
- Boundary testing is the process of testing between extreme ends or boundaries
between partitions of the input values.

- The basic idea in normal boundary value testing So these extreme ends like Start-
End, Lower- Upper, Maximum-Minimum, Just Inside-Just Outside values are called
boundary values and the testing is called "boundary testing".
- to select input variable values at their:
• Minimum
• Just above the minimum
• A nominal value
• Just below the maximum
• Maximum
-
6- List out the methods to calculate the test metric
- Process Metrics: It can be used to improve the process efficiency of the SDLC
(Software Development Life Cycle)
- Product Metrics: It deals with the quality of the software product
- Project Metrics: It can be used to measure the efficiency of a project team or any
testing tools being used by the team members
- Manual test metrics are classified into two classes
1- Base Metrics
2- Calculated Metrics
- Base metrics is the raw data collected by Test Analyst during the test case
development and execution (# of test cases executed, # of test cases). While
calculated metrics are derived from the data collected in base metrics.
- Calculated metrics is usually followed by the test manager for test reporting purpose
(% Complete, % Test Coverage)
7- Statement coverage with example
 Statement Coverage, as the name itself suggests, it is the method of validating whether
each and every line of the code is executed at least once.
 Statement Coverage is a white box testing technique in which all the executable
statements in the source code are executed at least once.
It is used for calculation of the number of statements in source code which have
been executed. The main purpose of Statement Coverage is to cover all the possible
paths, lines and statements in source code.
Statement coverage is used to derive scenario based upon the structure of the code
under test.

 Example: Consider the below pseudocode:

For Statement Coverage – we would only need one test case to check all the lines of
the code.
That means:
If I consider TestCase_01 to be (A=40 and B=70), then all the lines of code will be
executed
Number of executed statements = 6
Total number of statements = 7

Statement Coverage: 6/7 = 85%

But overall if you see, all the statements are being covered by 2nd scenarios
considered. So, we can conclude that overall statement coverage is 100%

8- Test criteria and it’s types

/////****
9- Conditional coverage testing with example
- Condition Coverage or expression coverage is a testing method used to test and
evaluate the variables or sub-expressions in the conditional statement.
- The goal of condition coverage is to check individual outcomes for each logical
condition.
- Condition coverage offers better sensitivity to the control flow than decision
coverage. In this coverage, expressions with logical operands are only considered.
- For example, if an expression has Boolean operations like AND, OR, XOR, which
indicates total possibilities
- Condition coverage does not give a guarantee about full decision coverage.
- The formula to calculate Condition Coverage:

 Example:
 - For the above expression, we have 4 possible combinations
TT
FF
TF
FT
- Consider the following input

X=3
(x<y) TRUE
Y=4
Condition Coverage is
¼ = 25%
A=3
(a>b) FALSE
B=4

8MARKS
1- What is cookie? cookie testing?
 A cookie:
is small information stored in a text file on the user’s hard drive by a web server.
This information is later used by the web browser to retrieve information from that
machine.
Cookies are nothing but the user’s identity and are used to track where the user navigated
throughout the website pages
Software Testing type that checks Cookie created in your web browser.
A cookie is a small piece of information that is stored in a text file on user's (client) hard
drive by the web server. This piece of information is then sent back to the server each time
the browser requests a page from the server.
Cookie contains personalized user data or information that is used to communicate between
different web pages.
The purpose of a cookie is to make rapid interaction between users and websites
 to do Cookies Testing:
- Disabling cookies: Disable all cookies and attempt to use the site's major functions
- Corrupting cookies: Manually edit the cookie in notepad and change the parameters
with some random values
 - Cookie’s encryption: Sensitive information like passwords and usernames should be
encrypted before it is sent to our computer
- Cookie testing with multiple browsers: Check your website page is writing the
cookies properly on a different browser as expected
- Checking the deletion from your web application page
- Selectively rejecting cookies: Delete all the cookies for the websites and see how the
website reacts to it
- Access to cookies: Cookies written by one website should not be accessible by others
- No overuse of cookies: If the application under test is a public website, there should
not be overuse of cookies
- Testing with the different setting: Testing should be done properly to check that
website is working well with different cookie setting
- Categorize cookies separately: Cookies should not be kept in the same category of
the viruses, spam or spyware

2- explain the concept of GUI testing and its technique?

 GUI Testing is a software testing type that checks the Graphical User Interface of the
Software.
The purpose of Graphical User Interface (GUI) Testing is to ensure the functionalities of
software application work as per specifications by checking screens and controls like menus,
buttons, icons, etc.
A user does not see the source code. The interface is visible to the user. Especially the focus
is on the design structure, images that they are working properly or not.
 Now the basic concept of GUI testing is clear. The few questions that will strike in your mind
will be
- Why do GUI testing?
- Is it really needed?
- Does testing of functionally and logic of Application is not more than enough?
- why to waste time on UI testing?
 GUI Testing Techniques can be categorized into three types:
a- Manual Based Testing: Under this approach, graphical screens are checked
manually by testers in conformance with Under this approach, graphical screens
are checked manually by testers in conformance with
b- Record and Replay:
1-GUI testing can be done using automation tools. This testing is done in 2 parts.
2-During Record, test steps are captured by the automation tool.
3- During playback, the recorded test steps are executed on the Application
Under Test.
c- Model Based Testing: A model is a graphical description of a system’s behaviour.
It helps us to understand and predict the system behaviour. Models help in a
generation of efficient test cases using the system requirements

3- What are the roles and responsibilities of the software testing team? Explain it briefly!
 QA Leader:
- Acts as a point of contact for inter and intra departmental interaction
- Represents the software testing team as well as enables customer relationship
- Deciding the test budget and schedule
 - Identifying the testing activities for other team members like testers or test
engineers
- Planning the entire testing process
- Checking the availability of the resources to execute testing activities
- Identifying if the process of testing is going in sync with the software development
- Preparing the status report of testing activities
- Sharing updates on testing with the project manager
- Planning pre and post-test meetings
 Test Lead:
- The Major Role and Responsibilities of a Test Lead include the following:
- Technical expertise related to the test program and approach.
- Provides support for customer interface, staff planning, and supervision, as well as
progress status reporting.
- Validating the quality of the testing requirements such as testability, test design, and
script, test automation, etc.
- Staying updated about the latest test approaches and tools
- Assisting the software testing team to be aware of the latest trends in the world of
software testing.
- Arranging walk-through for test design and procedure.
- Implementing the test process.
- Ensuring that test-product documentation is complete
 Test Engineer:
- The role of a test engineer is to determine the best way to create a process that can
enable one to test a particular product in the best possible manner.
- Test engineers can have different expertise based on which they are assigned a role
in a company.
a- Usability Test Engineer
b- Manual Test Engineer
c- Automated Test Engineer
d- Network Test Engineer
e- Test Library and Configuration Specialist
f- Tester

4- Explain briefly about requirement traceability metric

- It is a high-level document to map and trace user requirements with test cases to
ensure that for each and every requirement adequate level of testing is being
achieved.
- The process to review all the test cases that are defined for any requirement is
called Traceability.
- Traceability enables us to determine which requirements spawned the most number
of defects during the testing process.
- The focus of any testing engagement is and should be maximum test coverage.
- Requirements Traceability Matrix establishes a way to make sure we place checks on
the coverage aspect.
- Requirement Traceability assures good ‘Quality’ of the application as all the features
are tested
- Defect Leakages are prevented as a whole of the application is tested for its
requirements
- Types of Traceability Matrix:
1- Forward Traceability
2- Backward Traceability
3- Bi-Directional Traceability