Manual Testing
1.What is Software
Testing?
Testing?
Software testing is an activity to check whether the actual result match the expected result and to ensure that the software is defect free.
2. Why software testing is important?
Testing is important because software bugs could be expensive or even dangerous. Software bugs can potentially cause money and human loss.
Example- If the Banking site crash at the time of transaction than may be customer will face the loss of money and it will affect the reputation of Bank.
3. Types of software Testing?
1. Functional Testing
- Unit Testing
- Integration Testing
- Smoke
- User Acceptance Testing
- Localization
- Globalization
2. Non-Functional Testing
- Performance
- Endurance
- Load
- Volume
- Scalability
- Usability
3. Maintenance
- Regression
4. What is Quality
Assurance?
Assurance?
Quality assurance is an process driven approach which checks if the process of developing the product
is correct and matching to all the standards. It is considered as a
preventive measure as it identifies the weakness in the process to build a software.
is correct and matching to all the standards. It is considered as a
preventive measure as it identifies the weakness in the process to build a software.
5. What is Quality
Control?
Control?
Quality control is
product driven approach which checks that the developed product conforms to all
the specified requirements. It is considered as a corrective measure as it
tests the built product to find the defects. It involves different types of
testing like functional testing, performance testing, usability testing etc.
product driven approach which checks that the developed product conforms to all
the specified requirements. It is considered as a corrective measure as it
tests the built product to find the defects. It involves different types of
testing like functional testing, performance testing, usability testing etc.
6. What is the
difference between Verification and Validation?
difference between Verification and Validation?
Following are the major
differences between verification and validation-
differences between verification and validation-
Verification-
Verification is the process of evaluating the
artifacts as well as the process of software development in order to ensure
that the product being developed will comply to the standards
artifacts as well as the process of software development in order to ensure
that the product being developed will comply to the standards
It is static process of analyzing the
documents and not the actual end product.
documents and not the actual end product.
Verification is a process oriented approach
Answers the question – “Are we building
the product right?”
the product right?”
Validation-
Validation is the process of validating that
the developed software product conforms to the specified business requirements
the developed software product conforms to the specified business requirements
It involves dynamic testing of software
product by running it.
product by running it.
Validation is a product oriented approach.
Answers the question – “Are we building
the right product?”
the right product?”
7. What is SDLC?
Software Development
Life Cycle refers to all the activities that are performed during software
development, including – requirement analysis, designing, implementation,
testing, deployment and maintenance phases.
Life Cycle refers to all the activities that are performed during software
development, including – requirement analysis, designing, implementation,
testing, deployment and maintenance phases.
8. Explain STLC –
Software Testing life cycle.
Software Testing life cycle.
Software testing life cycle
refers to all the activities performed during testing of a software product.
The phases include-
refers to all the activities performed during testing of a software product.
The phases include-
Requirement analyses and
validation – In this phase the requirements documents are analysed and
validated and scope of testing is defined.
validation – In this phase the requirements documents are analysed and
validated and scope of testing is defined.
Test planning – In this
phase test plan strategy is defined, estimation of test effort is defined along
with automation strategy and tool selection is done.
phase test plan strategy is defined, estimation of test effort is defined along
with automation strategy and tool selection is done.
Test Design and analysis –
In this phase test cases are designed, test data is prepared and automation
scripts are implemented.
In this phase test cases are designed, test data is prepared and automation
scripts are implemented.
Test environment setup – A
test environment closely simulating the real world environment is prepared.
test environment closely simulating the real world environment is prepared.
Test execution – The test
cases are prepared, bugs are reported and retested once resolved.
cases are prepared, bugs are reported and retested once resolved.
Test closure and reporting –
A test closure report is prepared having the final test results summary,
learning and test metrics.
A test closure report is prepared having the final test results summary,
learning and test metrics.
9. What are the
different types of testing?
different types of testing?
Testing can broadly be
defined into two types-
defined into two types-
Functional testing –
Functional testing involves validating the functional specifications of the
system.
Functional testing involves validating the functional specifications of the
system.
Non Functional testing – Non
functional testing includes testing the non-functional requirements of the
system like performance, security, scalability, portability, endurance etc.
functional testing includes testing the non-functional requirements of the
system like performance, security, scalability, portability, endurance etc.
Black box testing – In black
box testing, the tester need not have any knowledge of the internal
architecture or implementation of the system. The tester interact with the
system through the interface providing input and validating the received
output.
box testing, the tester need not have any knowledge of the internal
architecture or implementation of the system. The tester interact with the
system through the interface providing input and validating the received
output.
White box testing – In white
box testing, the tester analyses the internal architecture of the system as
well as the quality of source code on different parameters like code
optimization, code coverage, code reusability etc.
box testing, the tester analyses the internal architecture of the system as
well as the quality of source code on different parameters like code
optimization, code coverage, code reusability etc.
Gray box testing – In gray
box testing, the tester has partial access to the internal architecture of the
system e.g. the tester may have access to the design documents or database
structure. This information helps tester to test the application better.
box testing, the tester has partial access to the internal architecture of the
system e.g. the tester may have access to the design documents or database
structure. This information helps tester to test the application better.
10. What is a test bed?
A test bed is a test
environment used for testing an application. A test bed configuration can
consist of the hardware and software requirement of the application under test
including – operating system, hardware configurations, software configurations,
tomcat, database etc.
environment used for testing an application. A test bed configuration can
consist of the hardware and software requirement of the application under test
including – operating system, hardware configurations, software configurations,
tomcat, database etc.
11. What is a test
plan?
plan?
A test plan is a formal
document describing the scope of testing, the approach to be used, resources
required and time estimate of carrying out the testing process. It is derived
from the requirement documents(Software Requirement Specifications).
document describing the scope of testing, the approach to be used, resources
required and time estimate of carrying out the testing process. It is derived
from the requirement documents(Software Requirement Specifications).
12. What is a test
scenario
scenario
Ans. A test scenario is
derived from a use case. It is used for end end to end testing of a feature of
an application. A single test scenario can cater multiple test cases. The
scenario testing is particularly useful when there is time constraint while
testing.
derived from a use case. It is used for end end to end testing of a feature of
an application. A single test scenario can cater multiple test cases. The
scenario testing is particularly useful when there is time constraint while
testing.
13. What is a test
case?
case?
Ans. A test case is used to
test the conformance of an application with its requirement specifications. It
is a set of conditions with pre-requisites, input values and expected results
in a documented form.
test the conformance of an application with its requirement specifications. It
is a set of conditions with pre-requisites, input values and expected results
in a documented form.
14. What are some
attributes of a test case?
attributes of a test case?
Ans. A test case can have
following attributes-
following attributes-
Test Case Id – A unique
identifier of the test case
identifier of the test case
Test Summary – One liner
summary of the test case.
summary of the test case.
Description – Detailed description
of the test case.
of the test case.
Prerequisite or
pre-condition – A set of prerequisites that must be followed before executing
the test steps.
pre-condition – A set of prerequisites that must be followed before executing
the test steps.
Test Steps – Detailed steps
for performing the test case.
for performing the test case.
Expected result – The
expected result in order to pass the test.
expected result in order to pass the test.
Actual result – The actual
result after executing the test steps.
result after executing the test steps.
Test Result – Pass/Fail
status of the test execution.
status of the test execution.
Automation Status –
Identifier of automation – whether the application is automated or not.
Identifier of automation – whether the application is automated or not.
Date – The test execution
date.
date.
Executed by – Name of the
person executing the test case.
person executing the test case.
15. What is a test
script?
script?
Ans. A test script is an
automated test case written in any programming or scripting language. These are
basically a set of instructions to evaluate the functioning of an application.
automated test case written in any programming or scripting language. These are
basically a set of instructions to evaluate the functioning of an application.
16. What is a bug?
Ans. A bug is a fault in a
software product detected at the time of testing, causing it to function in an
unanticipated manner.
software product detected at the time of testing, causing it to function in an
unanticipated manner.
Ques.17. What is a defect?
Ans. A defect is
non-conformance with the requirement of the product detected in production
(after the product goes live).
non-conformance with the requirement of the product detected in production
(after the product goes live).
Ques.18. What are some
defect reporting attributes?
defect reporting attributes?
Ans. Some of the attributes
of a Defect report are-
of a Defect report are-
Defect Id – A unique
identifier of the defect.
identifier of the defect.
Defect Summary – A one line
summary of the defect, more like a defect title.
summary of the defect, more like a defect title.
Defect Description – A
detailed description of the defect.
detailed description of the defect.
Steps to reproduce – The
steps to reproduce the defect.
steps to reproduce the defect.
Expected Result – The
expected behavior from which the application is deviating because of the
defect.
expected behavior from which the application is deviating because of the
defect.
Actual Result– The current
erroneous state of the application w.r.t. the defect.
erroneous state of the application w.r.t. the defect.
Defect Severity – Based on
the criticality of the defect, this field can be set to minor, medium, major or
show stopper.
the criticality of the defect, this field can be set to minor, medium, major or
show stopper.
Priority – Based on the
urgency of the defect, this field can be set on a scale of P0 to P3.
urgency of the defect, this field can be set on a scale of P0 to P3.
Ques.19. What are some of
the bug or defect management tools?
the bug or defect management tools?
Ans. Some of the most widely
used Defect Management tools are – Jira, Bugzilla, Redmine, Mantis, Quality
Center etc.
used Defect Management tools are – Jira, Bugzilla, Redmine, Mantis, Quality
Center etc.
Ques.20. What is defect
density?
density?
Ans. Defect density is the
measure of density of the defects in the system. It can be calculated by
dividing number of defect identified by the total number of line of code(or
methods or classes) in the application or program.
measure of density of the defects in the system. It can be calculated by
dividing number of defect identified by the total number of line of code(or
methods or classes) in the application or program.
Ques.21. What is defect
priority?
priority?
Ans. A defect priority is
the urgency of the fixing the defect. Normally the defect priority is set on a
scale of P0 to P3 with P0 defect having the most urgency to fix.
the urgency of the fixing the defect. Normally the defect priority is set on a
scale of P0 to P3 with P0 defect having the most urgency to fix.
Ques.22. What is defect
severity?
severity?
Ans. Defect severity is the
severity of the defect impacting the functionality. Based on the organisation,
we can have different levels of defect severity ranging from minor to critical
or show stopper.
severity of the defect impacting the functionality. Based on the organisation,
we can have different levels of defect severity ranging from minor to critical
or show stopper.
Ques.23. Give an example of
Low priority-Low severity, Low priority-High severity, High priority-Low
severity, High priority-High severity defects.
Low priority-Low severity, Low priority-High severity, High priority-Low
severity, High priority-High severity defects.
Ans.Low priority-Low
severity – A spelling mistake in a page not frequently navigated by users.
severity – A spelling mistake in a page not frequently navigated by users.
Low priority-High severity –
Application crashing in some very corner case.
Application crashing in some very corner case.
High priority-Low severity –
Slight change in logo color or spelling mistake in company name.
Slight change in logo color or spelling mistake in company name.
High priority-High severity
– Issue with login functionality.
– Issue with login functionality.
Ques.24. What is a blocker?
Ans. A blocker is a bug of
high priority and high severity. It prevents or blocks testing of some other
major portion of the application as well.
high priority and high severity. It prevents or blocks testing of some other
major portion of the application as well.
Ques.25. What is a critical
bug?
bug?
Ans. A critical bug is a bug
that impacts a major functionality of the application and the application
cannot be delivered without fixing the bug. It is different from blocker bug as
it doesn’t affect or blocks the testing of other part of the application.
that impacts a major functionality of the application and the application
cannot be delivered without fixing the bug. It is different from blocker bug as
it doesn’t affect or blocks the testing of other part of the application.
Ques.26. Explain bug
life cycle or the different states of a bug.
life cycle or the different states of a bug.
Ans. A bug goes through the
following phases in software development-
following phases in software development-
New – A bug or defect when
detected is in New state
detected is in New state
Assigned – The newly
detected bug when assigned to the corresponding developer is in Assigned state
detected bug when assigned to the corresponding developer is in Assigned state
Open – When the developer
works on the bug, the bug lies in Open state
works on the bug, the bug lies in Open state
Rejected/Not a bug – A bug
lies in rejected state in case the developer feels the bug is not genuine
lies in rejected state in case the developer feels the bug is not genuine
Deferred – A deferred bug is
one, fix of which is deferred for some time(for the next releases) based on
urgency and criticality of the bug
one, fix of which is deferred for some time(for the next releases) based on
urgency and criticality of the bug
Fixed – When a bug is
resolved by the developer it is marked as fixed
resolved by the developer it is marked as fixed
Test – When fixed the bug is
assigned to the tester and during this time the bug is marked as in Test
assigned to the tester and during this time the bug is marked as in Test
Reopened – If the tester is not
satisfied with issue resolution the bug is moved to Reopened state
satisfied with issue resolution the bug is moved to Reopened state
Verified – After the Test
phase if the tester feels bug is resolved, it is marked as verified
phase if the tester feels bug is resolved, it is marked as verified
Closed – After the bug is
verified, it is moved to Closed status.
verified, it is moved to Closed status.
Ques.27. What are the different
test design techniques?
test design techniques?
Ans. Test design techniques
are different standards of test designing which allow systematic and widely
accepted test cases. The different test design techniques can be categorized as
static test design technique and dynamic test design technique.
are different standards of test designing which allow systematic and widely
accepted test cases. The different test design techniques can be categorized as
static test design technique and dynamic test design technique.
Static Test Design
Techniques – The test design techniques which involves testing without
executing the code. The various static test design techniques can be further
divided into two parts manual and using tool-
Techniques – The test design techniques which involves testing without
executing the code. The various static test design techniques can be further
divided into two parts manual and using tool-
Manual static design
techniques-
techniques-
Walk through
Informal reviews
Technical reviews
Audit
Inspection
Management review
Static design techniques
using tool
using tool
Static analysis of code – It
includes analysis of the different paths and flows in the application and
different states of the test data.
includes analysis of the different paths and flows in the application and
different states of the test data.
Compliance to coding
standard – This evaluates the compliance of the code with the different coding
standards.
standard – This evaluates the compliance of the code with the different coding
standards.
Analysis of code metrics –
The tool used for static analysis is required to evaluate the different metrics
like lines of code, complexity, code coverage etc.
The tool used for static analysis is required to evaluate the different metrics
like lines of code, complexity, code coverage etc.
Dynamic Test Design
Techniques – Dynamic test design techniques involves testing by running the
system under test.
Techniques – Dynamic test design techniques involves testing by running the
system under test.
Specification based –
Specification based test design techniques are also referred to as blackbox
testing. These involve testing based on the specification of the system under
test without knowing its internal architecture.
Specification based test design techniques are also referred to as blackbox
testing. These involve testing based on the specification of the system under
test without knowing its internal architecture.
Structure based – Structure
based test design techniques are also referred to as white box testing. In this
techniques the knowledge of code or internal architecture of the system is
required to carry out the testing.
based test design techniques are also referred to as white box testing. In this
techniques the knowledge of code or internal architecture of the system is
required to carry out the testing.
Experienced based – The
experienced based techniques are completely based on the experience or intution
of the tester. Two most common forms of experienced based testing are – adhoc
testing and exploratory testing.
experienced based techniques are completely based on the experience or intution
of the tester. Two most common forms of experienced based testing are – adhoc
testing and exploratory testing.
Ques.28. Explain the
different types of specification based test design technique?
different types of specification based test design technique?
Ans. Specification based test
design techniques are also referred to as blackbox testing. It involves testing
based on the specification of the system under test without knowing its
internal architecture. The different types of specification based test design
or black box testing techniques are-
design techniques are also referred to as blackbox testing. It involves testing
based on the specification of the system under test without knowing its
internal architecture. The different types of specification based test design
or black box testing techniques are-
Equivalence partitioning –
Grouping test data into logical groups or equivalence classes with the
assumpation that all the data items lying in the classes will have same effect
on the application.
Grouping test data into logical groups or equivalence classes with the
assumpation that all the data items lying in the classes will have same effect
on the application.
Boundary value analysis –
Testing using the boundary values of the equivalence classes taken as the test
input.
Testing using the boundary values of the equivalence classes taken as the test
input.
Decision tables – Testing
using decision tables showing application’s behaviour based on different
combination of input values.
using decision tables showing application’s behaviour based on different
combination of input values.
Cause-effect graph – Testing
using graphical representation of input i.e. cause and output i.e. effect is
used for test designing.
using graphical representation of input i.e. cause and output i.e. effect is
used for test designing.
State transition testing –
Testing based on state machine model.
Testing based on state machine model.
Use case testing – Testing
carried out using use cases.
carried out using use cases.
Ques.29. Explain equivalence
class partitioning.
class partitioning.
Ans. Equivalence class
partitioning is a specification based black box testing techniques. In
equivalence class partitioning, set of input data that defines different test
conditions are partitioned into logically similar groups such that using even a
single test data from the group for testing can be considered as similar to
using all the other data in that group. E.g. for testing a Square
program(program that prints the square of a number- the equivalence classes can
be-
partitioning is a specification based black box testing techniques. In
equivalence class partitioning, set of input data that defines different test
conditions are partitioned into logically similar groups such that using even a
single test data from the group for testing can be considered as similar to
using all the other data in that group. E.g. for testing a Square
program(program that prints the square of a number- the equivalence classes can
be-
Set of Negative numbers,
whole numbers, decimal numbers, set of large numbers etc.
whole numbers, decimal numbers, set of large numbers etc.
Ques.30. What is boundary
value analysis?
value analysis?
Ans. Boundary value analysis
is a software testing technique for designing test cases wherein the boundary
values of the classes of the equivalence class partitioning are taken as input
to the test cases e.g. if the test data lies in the range of 0-100, the
boundary value analysis will include test data – 0,1, 99, 100.
is a software testing technique for designing test cases wherein the boundary
values of the classes of the equivalence class partitioning are taken as input
to the test cases e.g. if the test data lies in the range of 0-100, the
boundary value analysis will include test data – 0,1, 99, 100.
Ques.31. What is decision
table testing?
table testing?
Ans. Decision table testing
is a type of specification based test design technique or black box testing
technique in which testing is carried out using decision tables showing
application’s behavior based on different combination of input values. Decision
tables are particularly helpful in designing test cases for complex business
scenarios involving verification of application with multiple combinations of
input.
is a type of specification based test design technique or black box testing
technique in which testing is carried out using decision tables showing
application’s behavior based on different combination of input values. Decision
tables are particularly helpful in designing test cases for complex business
scenarios involving verification of application with multiple combinations of
input.
Ques.32. What is a cause
effect graph?
effect graph?
Ans. A cause effect graph
testing is black box test design technique in which graphical representation of
input i.e. cause and output i.e. effect is used for test designing. This
technique uses different notations representing AND, OR, NOT etc relations
between the input conditions leading to output.
testing is black box test design technique in which graphical representation of
input i.e. cause and output i.e. effect is used for test designing. This
technique uses different notations representing AND, OR, NOT etc relations
between the input conditions leading to output.
Ques.33. What is state
transition testing?
transition testing?
Ans. State transition
testing is a black box test design technique based on state machine model.
State transition testing is based on the concept that a system can be defined
as a collection of multiple states and the transition from one state to other
happens because of some event.
testing is a black box test design technique based on state machine model.
State transition testing is based on the concept that a system can be defined
as a collection of multiple states and the transition from one state to other
happens because of some event.
Ques.34. What is use case
testing?
testing?
Ans. A use case testing is a
black box testing approach in which testing is carried out using use cases. A
use case scenario is seen as interaction between the application and
actors(users). These use cases are used for depicting requirements and hence
can also serve as basis for acceptance testing.
black box testing approach in which testing is carried out using use cases. A
use case scenario is seen as interaction between the application and
actors(users). These use cases are used for depicting requirements and hence
can also serve as basis for acceptance testing.
Ques.35. What is structure
based testing?
based testing?
Ans. Structure based test
design techniques are also referred to as white box testing. In this techniques
the knowledge of code or internal architecture of the system is required to
carry out the testing. The various kinds of testing structure based or white
testing techniques are-
design techniques are also referred to as white box testing. In this techniques
the knowledge of code or internal architecture of the system is required to
carry out the testing. The various kinds of testing structure based or white
testing techniques are-
Statement testing – Test
scripts are designed to execute code statements and coverage is the measure of
line of code or statements executed by test scripts.
scripts are designed to execute code statements and coverage is the measure of
line of code or statements executed by test scripts.
Decision testing/branch
testing – Measure of the percentage of decision points(e.g. if-else conditions)
executed out of the total decision points in the application.
testing – Measure of the percentage of decision points(e.g. if-else conditions)
executed out of the total decision points in the application.
Condition testing– Testing
the condition outcomes(TRUE or FALSE). So, getting 100% condition coverage
required exercising each condition for both TRUE and FALSE results using test
scripts(For n conditions we will have 2n test scripts).
the condition outcomes(TRUE or FALSE). So, getting 100% condition coverage
required exercising each condition for both TRUE and FALSE results using test
scripts(For n conditions we will have 2n test scripts).
Multiple condition testing –
Testing the different combinations of condition outcomes. Hence for 100%
coverage we will have 2^n test scripts. This is very exhaustive and very difficult
to achieve 100% coverage.
Testing the different combinations of condition outcomes. Hence for 100%
coverage we will have 2^n test scripts. This is very exhaustive and very difficult
to achieve 100% coverage.
Condition determination
testing – It is an optimized way of multiple condition testing in which the
combinations which doesn’t affect the outcomes are discarded.
testing – It is an optimized way of multiple condition testing in which the
combinations which doesn’t affect the outcomes are discarded.
Path testing – Testing the
independent paths in the system(paths are executable statements from entry to
exit points).
independent paths in the system(paths are executable statements from entry to
exit points).
Ques.36. What is Statement
testing and statement coverage in white box testing?
testing and statement coverage in white box testing?
Ans. Statement testing is a
white box testing approach in which test scripts are designed to execute code
statements.
white box testing approach in which test scripts are designed to execute code
statements.
Statement coverage is the
measure of the percentage of statements of code executed by the test scripts
out of the total code statements in the application. The statement coverage is
the least preferred metric for checking test coverage.
measure of the percentage of statements of code executed by the test scripts
out of the total code statements in the application. The statement coverage is
the least preferred metric for checking test coverage.
Ques.37. What is decision
testing or branch testing?
testing or branch testing?
Ans. Decision testing or
branch testing is a white box testing approach in which test coverage is
measured by the percentage of decision points(e.g. if-else conditions) executed
out of the total decision points in the application.
branch testing is a white box testing approach in which test coverage is
measured by the percentage of decision points(e.g. if-else conditions) executed
out of the total decision points in the application.
Ques.38. What are the
different levels of the testing?
different levels of the testing?
Ans. Testing can be
performed at different levels during the development process. Performing
testing activities at multiple levels help in early identification of bugs. The
different levels of testing are –
performed at different levels during the development process. Performing
testing activities at multiple levels help in early identification of bugs. The
different levels of testing are –
Unit Testing
Integration Testing
System Testing
Acceptance Testing
Ques.39. What is unit
testing?
testing?
Ans. Unit testing is the
first level of testing and it involves testing of individual modules of the
software. It is usually performed by developers.
first level of testing and it involves testing of individual modules of the
software. It is usually performed by developers.
Ques.40. What is integration
testing?
testing?
Ans. Integration testing is
performed after unit testing. In integration testing, we test the group of
related modules. It aims at finding interfacing issues between the modules.
performed after unit testing. In integration testing, we test the group of
related modules. It aims at finding interfacing issues between the modules.
Ques.41. What are the
different types of integration testing?
different types of integration testing?
Ans. The different type of
integration testing are-
integration testing are-
Big bang Integration Testing
– In big bang integration testing, testing starts only after all the modules
are integrated.
– In big bang integration testing, testing starts only after all the modules
are integrated.
Top-down Integration Testing
– In top down integration, testing/integration starts from top modules to lower
level modules.
– In top down integration, testing/integration starts from top modules to lower
level modules.
Bottom-up Integration
Testing – In bottom up integration, testing starts from lower level modules to
higher level module up in the hierarchy.
Testing – In bottom up integration, testing starts from lower level modules to
higher level module up in the hierarchy.
Hybrid Integration Testing –
Hybrid integration testing is the combination of both Top-down and bottom up
integration testing. In this approach, the integration starts from middle layer
and testing is carried out in both the direction
Hybrid integration testing is the combination of both Top-down and bottom up
integration testing. In this approach, the integration starts from middle layer
and testing is carried out in both the direction
Ques.42. What is stub?
Ans. In case of top-down
integration testing, many a times lower level modules are not developed while
beginning testing/integration with top level modules. In those cases Stubs or
dummy modules are used that simulate the working of modules by providing hardcoded
or expected output based on the input values.
integration testing, many a times lower level modules are not developed while
beginning testing/integration with top level modules. In those cases Stubs or
dummy modules are used that simulate the working of modules by providing hardcoded
or expected output based on the input values.
Ques.43. What is driver?
Ans. In case of bottom-up
integration testing, drivers are used to simulate the working of top level
modules in order to test the related modules lower in the heirarchy.
integration testing, drivers are used to simulate the working of top level
modules in order to test the related modules lower in the heirarchy.
Ques.44. What is a test
harness? Why do we need a test harness?
harness? Why do we need a test harness?
Ans. A test harness is a
collection of test scripts and test data usually associated with unit and
integration testing. It involves stubs and drivers that are required for
testing software modules and integrated components.
collection of test scripts and test data usually associated with unit and
integration testing. It involves stubs and drivers that are required for
testing software modules and integrated components.
Ques.45. What is system
testing?
testing?
Ans. System testing is the
level of testing where the complete software is tested as a whole. The
conformance of the application with its business requirements is checked in
system testing.
level of testing where the complete software is tested as a whole. The
conformance of the application with its business requirements is checked in
system testing.
Ques.46. What is acceptance
testing?
testing?
Ans. Acceptance testing is a
testing performed by the potential end user or customers to check if the
software conforms to the business requirements and can be accepted for use.
testing performed by the potential end user or customers to check if the
software conforms to the business requirements and can be accepted for use.
Ques.47. What is alpha
testing?
testing?
Ans. Alpha testing is a type
of acceptance testing that is performed end users at the developer site.
of acceptance testing that is performed end users at the developer site.
Ques.48. What is beta
testing?
testing?
Ans. Beta testing is the
testing done by end users at end user’s site. It allows users to provide direct
input about the software to the development company.
testing done by end users at end user’s site. It allows users to provide direct
input about the software to the development company.
Ques.49. What is adhoc
testing?
testing?
Ans. Adhoc testing is an
unstructured way of testing that is performed without any formal documentation
or proper planning.
unstructured way of testing that is performed without any formal documentation
or proper planning.
Ques.50. What is monkey
testing?
testing?
Ans. Monkey testing is a
type of testing that is performed randomly without any predefined test cases or
test inputs.
type of testing that is performed randomly without any predefined test cases or
test inputs.
Ques.51. How is monkey
testing different from adhoc testing?
testing different from adhoc testing?
Ans. In case of adhoc
testing although there are no predefined or documented test cases still testers
have the understanding of the application. While in case of monkey testing
testers doesn’t have any understanding of the application
testing although there are no predefined or documented test cases still testers
have the understanding of the application. While in case of monkey testing
testers doesn’t have any understanding of the application
Ques.52. What is exploratory
testing?
testing?
Ans. Exploratory testing is
a type of testing in which new test cases are added and updated while exploring
the system or executing test cases. Unlike scripted testing, test design and
execution goes parallely in exploratory testing.
a type of testing in which new test cases are added and updated while exploring
the system or executing test cases. Unlike scripted testing, test design and
execution goes parallely in exploratory testing.
Ques.53. What is performance
testing?
testing?
Ans. Performance testing is
a type of non-functional testing in which the performance of the system is
evaluated under expected or higher load. The various performance parameters
evaluated during performance testing are – response time, reliability, resource
usage, scalabilty etc.
a type of non-functional testing in which the performance of the system is
evaluated under expected or higher load. The various performance parameters
evaluated during performance testing are – response time, reliability, resource
usage, scalabilty etc.
Ques.54. What is load
testing?
testing?
Ans. Load testing is a type
of performance testing which aims at finding application’s performance under
expected workload. During load testing we evaluate the response time,
throughput, error rate etc parameters of the application.
of performance testing which aims at finding application’s performance under
expected workload. During load testing we evaluate the response time,
throughput, error rate etc parameters of the application.
Ques.55. What is stress
testing?
testing?
Ans. Stress testing is a
type of performance testing in which application’s behaviour is monitored under
higher workload then expected. Stress testing is done to find memory leaks and
robustness of the application.
type of performance testing in which application’s behaviour is monitored under
higher workload then expected. Stress testing is done to find memory leaks and
robustness of the application.
Ques.56. What is volume
testing?
testing?
Ans. Volume testing is a
type of performance testing in which the performance of application is
evaluated with large amount of data. It checks the scalability of the
application and helps in identification of bottleneck with high volume of data.
type of performance testing in which the performance of application is
evaluated with large amount of data. It checks the scalability of the
application and helps in identification of bottleneck with high volume of data.
Ques.57. What is endurance
testing or Soak testing?
testing or Soak testing?
Ans. Endurance testing is a
type of performance testing which aims at finding issues like memory leaks when
an application is subjected to load test for a long period of time.
type of performance testing which aims at finding issues like memory leaks when
an application is subjected to load test for a long period of time.
Ques.58. What is spike
testing?
testing?
Ans. Spike testing is a type
of performance testing in which the application’s performance is measured while
suddenly increasing the number of active users during the load test.
of performance testing in which the application’s performance is measured while
suddenly increasing the number of active users during the load test.
Ques.59. What is usability
testing?
testing?
Ans. Usability testing is
the type of testing that aims at determining the ease of using the application.
It aims at uncovering the usability defects in the application.
the type of testing that aims at determining the ease of using the application.
It aims at uncovering the usability defects in the application.
Ques.60. What is
Accessibility testing?
Accessibility testing?
Ans. Accessibility is the
type of testing which aims at determining the ease of use or operation of the
application specifically for people with disabilities.
type of testing which aims at determining the ease of use or operation of the
application specifically for people with disabilities.
Ques.61. What is
compatibility testing?
compatibility testing?
Ans. Testing software to see
how compatible the software is with a particular environment – operating
system, platform or hardware.
how compatible the software is with a particular environment – operating
system, platform or hardware.
Ques.62. What is
configuration testing?
configuration testing?
Ans. Configuration testing
is the type of testing used to evaluate the configurational requirements of the
software along with effect of changing the required configuration.
is the type of testing used to evaluate the configurational requirements of the
software along with effect of changing the required configuration.
Ques.63. What is
localisation testing?
localisation testing?
Ans. Localisation testing is
a type of testing in which we evaluate the application’s
customization(localized version of application) in a particular culture, locale
or country.
a type of testing in which we evaluate the application’s
customization(localized version of application) in a particular culture, locale
or country.
Ques.64. What is
globalisation testing?
globalisation testing?
Ans. Globalisation testing
is a type of testing in which application is evaluated for its functioning
across the world in different cultures, languages, locale and countries.
is a type of testing in which application is evaluated for its functioning
across the world in different cultures, languages, locale and countries.
Ques.65. What is negative
testing?
testing?
Ans. Negative testing is a
type of testing in which the application’s robustness(graceful exiting or error
reporting) is evaluated when provided with invalid input or test data.
type of testing in which the application’s robustness(graceful exiting or error
reporting) is evaluated when provided with invalid input or test data.
Ques.66. What is security
testing?
testing?
Ans. Security testing is a
type of testing which aims at evaluating the integrity, authentication,
authorization, availabilty, confidentiality and non-repudation of the
application under test.
type of testing which aims at evaluating the integrity, authentication,
authorization, availabilty, confidentiality and non-repudation of the
application under test.
Ques.67. What is penetration
testing?
testing?
Ans. Penetration testing or
pen testing is a type of security testing in which application is
evaluated(safely exploited) for different kinds of vulnerabilities that any
hacker could expolit.
pen testing is a type of security testing in which application is
evaluated(safely exploited) for different kinds of vulnerabilities that any
hacker could expolit.
Ques.68. What is robustness
testing?
testing?
Ans. Robustness testing is a
type of testing that is performed to find the robustness of the application
i.e. the ability of the system to behave gracefully in case of erroneous test
steps and test input.
type of testing that is performed to find the robustness of the application
i.e. the ability of the system to behave gracefully in case of erroneous test
steps and test input.
Ques.69. What is A/B
testing?
testing?
A/B testing is a type of testing
in which the two variants of the software product are exposed to the end users
and on analysing the user behaviour on each variant, the better variant is
chosen and used thereafter.
in which the two variants of the software product are exposed to the end users
and on analysing the user behaviour on each variant, the better variant is
chosen and used thereafter.
Ques.70. What is concurrency
testing?
testing?
Ans. Concurrency testing is
a multi-user testing in which an application is evaluated by analyzing
application’s behaviour with concurent users acccessing the same functionality.
a multi-user testing in which an application is evaluated by analyzing
application’s behaviour with concurent users acccessing the same functionality.
Ques.71. What is all pair
testing?
testing?
Ans. All pair testing is a
type of testing in which the application is tested with all possible
combination of the values of input parameters.
type of testing in which the application is tested with all possible
combination of the values of input parameters.
Ques.72. What is failover
testing?
testing?
Ans. Failover testing is a
type of testing that is used to verify application’s ability to allocate more
resources(more servers) in case of failure and transfering of the processing
part to back-up system.
type of testing that is used to verify application’s ability to allocate more
resources(more servers) in case of failure and transfering of the processing
part to back-up system.
Ques.73. What is fuzz
testing?
testing?
Ans. Fuzz testing is a type
of testing in which large amount of random data is provided as input to the
application in order to find security loopholes and other issues in the
application.
of testing in which large amount of random data is provided as input to the
application in order to find security loopholes and other issues in the
application.
Ques.74. What is UI testing?
Ans. UI or user interface
testing is a type of testing that aims at finding Graphical User Interface
defects in the application and checks that the GUI conforms to the
specifications.
testing is a type of testing that aims at finding Graphical User Interface
defects in the application and checks that the GUI conforms to the
specifications.
Ques.75. What is risk
analysis?
analysis?
Ans. Risk analysis is the
analysis of the risk identified and assigning an appropriate risk level to it
based on its impact over the application.
analysis of the risk identified and assigning an appropriate risk level to it
based on its impact over the application.
Ques.76. What is the
difference between regression and retesting?
difference between regression and retesting?
Ans. Regression testing
involves testing the application to verify that a new code change doesn’t
affect the other parts of the application. Whereas, in retesting, we verify if
the fixed issue is resolved or not.
involves testing the application to verify that a new code change doesn’t
affect the other parts of the application. Whereas, in retesting, we verify if
the fixed issue is resolved or not.
Ques.77. What is the
difference between black-box and white-box testing?
difference between black-box and white-box testing?
Ans. Black-box testing is a
type of testing in which internal architecture of the code is not required for
testing. It is usually applicable for system and acceptance testing.
type of testing in which internal architecture of the code is not required for
testing. It is usually applicable for system and acceptance testing.
Whereas white-box testing
requires internal design and implementation knowledege of the application being
tested. It is usually applicable for Unit and Integration testing.
requires internal design and implementation knowledege of the application being
tested. It is usually applicable for Unit and Integration testing.
Ques.78. What is the
difference between smoke and sanity testing?
difference between smoke and sanity testing?
Ans. The difference between
smoke and sanity testing is-
smoke and sanity testing is-
Smoke testing is a type of
testing in which the all major functionalities of the application are tested
before carrying out exhaustive testing. Whereas, sanity testing is subset of
regression testing which is carried out when there is some minor fix in
application in a new build.
testing in which the all major functionalities of the application are tested
before carrying out exhaustive testing. Whereas, sanity testing is subset of
regression testing which is carried out when there is some minor fix in
application in a new build.
In smoke testing,
shallow-wide testing is carried out while in sanity narrow-deep testing (for a
particular functionality) is done.
shallow-wide testing is carried out while in sanity narrow-deep testing (for a
particular functionality) is done.
The smoke tests are usually
documented or are automated. Whereas, the sanity tests are generally not
documented or unscripted.
documented or are automated. Whereas, the sanity tests are generally not
documented or unscripted.
Ques.79. What is code
coverage?
coverage?
Ans. Code coverage is the
measure of the amount of code covered by the test scripts. It gives the idea of
the part of the application covered by the test suite.
measure of the amount of code covered by the test scripts. It gives the idea of
the part of the application covered by the test suite.
Ques.80. What is cyclomatic
complexity?
complexity?
Ans. Cyclomatic complexity
is the measure of the number of independent paths in an application or program.
This metric provides an indication of the amount of effort required to test
complete functionality. It can be defined by the expression –
is the measure of the number of independent paths in an application or program.
This metric provides an indication of the amount of effort required to test
complete functionality. It can be defined by the expression –
L – N + 2P, where:
L is the number of edges in
the graph
the graph
N is the number of node
P is the number of
disconnected parts
disconnected parts
Ques.81. What is dynamic
testing?
testing?
Ans. Testing performed by
executing or running the application under test either manually or using
automation.
executing or running the application under test either manually or using
automation.
Ques.82. What is an exit
criteria?
criteria?
Ans. An exit criteria is a
formal set of conditions that specify the agreed upon features or state of
application in order to mark the completion of the process or product.
formal set of conditions that specify the agreed upon features or state of
application in order to mark the completion of the process or product.
Ques.83. What is requirement
traceability matrix(RTM)?
traceability matrix(RTM)?
Ans. In software testing, a
traceability matrix is a table that relates the high level requirements with
either detailed requirements, test plans or test cases. RTM helps in ensuring
100% test coverage.
traceability matrix is a table that relates the high level requirements with
either detailed requirements, test plans or test cases. RTM helps in ensuring
100% test coverage.
Ques.84. What is pilot
testing?
testing?
Ans. Pilot testing is a
testing carried out as a trial by limited number of users to evaluate the
system and provide their feedback before the complete deployment is carried
out.
testing carried out as a trial by limited number of users to evaluate the
system and provide their feedback before the complete deployment is carried
out.
Ques.85. What is backend
testing?
testing?
Ans. Backend testing is a
type of testing that invloves testing the backend of the system which comprises
of testing the databases and the APIs in the application.
type of testing that invloves testing the backend of the system which comprises
of testing the databases and the APIs in the application.
Ques.86. What are some
advantages of automation testing?
advantages of automation testing?
Ans. Some advantages of
automation testing are-
automation testing are-
Test execution using
automation is fast and saves considerable amount of time.
automation is fast and saves considerable amount of time.
Carefully written test
scripts remove the chance of human error during testing.
scripts remove the chance of human error during testing.
Tests execution can be
scheduled for nightly run using CI tools like Jenkins which can also be configured
to provide daily test results to relevant stakeholders.
scheduled for nightly run using CI tools like Jenkins which can also be configured
to provide daily test results to relevant stakeholders.
Automation testing is very
less resource intensive. Once the tests are automated, test execution requires
almost no time of QAs. Saving Qa bandwidth for other explratory tasks.
less resource intensive. Once the tests are automated, test execution requires
almost no time of QAs. Saving Qa bandwidth for other explratory tasks.
Ques.87. What are some
disadvantages of automation testing?
disadvantages of automation testing?
Ans. Some advantages of
automation testing are-
automation testing are-
It requries skilled
automation testing experts to write test scritps.
automation testing experts to write test scritps.
Additional effort to write
scripts is required upfront.
scripts is required upfront.
Automation scripts are
limited to verification of the tests that are coded. These tests may miss some
error that is very glaring and easily identifiable to human(manual QA).
limited to verification of the tests that are coded. These tests may miss some
error that is very glaring and easily identifiable to human(manual QA).
Even with some minor change
in application, script updation and maintenance is required.
in application, script updation and maintenance is required.
Ques.88. What is mutation
testing?
testing?
Ans. Mutation testing is a
type of white box testing in which the source code of the application is
mutated to cause some defect in its working. After that the test scripts are
executed to check for their correctness by verifying the failures caused the
mutant code.
type of white box testing in which the source code of the application is
mutated to cause some defect in its working. After that the test scripts are
executed to check for their correctness by verifying the failures caused the
mutant code.
Ques.89. Write test cases
for Pen.
for Pen.
Ans. Verify the type of pen,
whether it is ball point pen, ink pen or gel pen
whether it is ball point pen, ink pen or gel pen
Verify the outer body of the
pen, whether it should be metallic, plastic or any other material as per the
specification
pen, whether it should be metallic, plastic or any other material as per the
specification
Verify that length, breadth
and other size specifications of the pen
and other size specifications of the pen
Verify the weight of the pen
Verify if the pen is with
cap or without cap
cap or without cap
Verify if the pen has rubber
grip or not
grip or not
Verify the color of the ink
of the pen
of the pen
Verify the odour of the pen
Verify the size of the tip
of the pen
of the pen
Verify the company name or
logo of the maker is correct and at desired place
logo of the maker is correct and at desired place
Verify if the pen is smooth
Verify if the pen’s ink gets
leaked in case it is tilted upside down
leaked in case it is tilted upside down
Verify if the pen’s gets
leaked at higher altitude
leaked at higher altitude
Verify the type of surfaces
the pen can write at
the pen can write at
Verify if the text written
by pen is erasable or not
by pen is erasable or not
Verify pen’s and its ink
condition at extreme temperature is as per the specification
condition at extreme temperature is as per the specification
Verify the pressure upto
which the pen’s tip can resist and work correctly
which the pen’s tip can resist and work correctly
Verify the pen is breakable
or not at a certain height as the specification
or not at a certain height as the specification
Verify text written by pen
doesn’t get faded before a certain time as per the specification
doesn’t get faded before a certain time as per the specification
Verify the effect of water,
oil and other liquid on the text written by pen
oil and other liquid on the text written by pen
Verify the condition of ink
after long period of time is as per permissible specification or not.
after long period of time is as per permissible specification or not.
Ques.90. Write test cases
for ATM Machine.
for ATM Machine.
Ans. Verify the slot for ATM
Card insertion is as per the specification
Card insertion is as per the specification
Verify that user is
presented with options when card is inserted from proper side
presented with options when card is inserted from proper side
Verify that no option to
continue and enter credentials is displayed to user when card is inserted
correctly
continue and enter credentials is displayed to user when card is inserted
correctly
Verify that font of the text
displayed in ATM screen is as per the specifications
displayed in ATM screen is as per the specifications
Verify that touch of the ATM
screen is smooth and operational
screen is smooth and operational
Verify that user is
presented with option to choose language for further operations
presented with option to choose language for further operations
Verify that user asked to
enter pin number before displaying any card/bank account detail
enter pin number before displaying any card/bank account detail
Verify that there are
limited number of attempts upto which user is allowed to enter pin code
limited number of attempts upto which user is allowed to enter pin code
Verify that if total number
of incorrect pin attempts gets surpassed then user is not allowed to continue
further- operations like blocking of card etc gets initiated
of incorrect pin attempts gets surpassed then user is not allowed to continue
further- operations like blocking of card etc gets initiated
Verify that pin is encrypted
and when entered
and when entered
Verify that user is
presented with different account type options like- saving, current etc
presented with different account type options like- saving, current etc
Verify that user is allowed
to get account details like available balance
to get account details like available balance
Verify that user same amount
of money gets dispatched as entered by user for cash withdrawal
of money gets dispatched as entered by user for cash withdrawal
Verify that user is only
allowed to enter amount in multiples of denominations as per the specifications
allowed to enter amount in multiples of denominations as per the specifications
Verify that user is prompted
to enter the amount again in case amount entered is not as per the
specification and proper message should be displayed for the same
to enter the amount again in case amount entered is not as per the
specification and proper message should be displayed for the same
Verify that user cannot
fetch more amount than the total available balance
fetch more amount than the total available balance
Verify that user is provided
the option to print the transaction/enquiry
the option to print the transaction/enquiry
Verify that user user’s
session timeout is maintained and is as per the specifications
session timeout is maintained and is as per the specifications
Verify that user is not
allowed to exceed one transaction limit amount
allowed to exceed one transaction limit amount
Verify that user is not
allowed to exceed one day transaction limit amount
allowed to exceed one day transaction limit amount
Verify that user is allowed
to do only one transaction per pin request
to do only one transaction per pin request
Verify that user is not
allowed to proceed with expired ATM card
allowed to proceed with expired ATM card
Verify that in case ATM
machine runs out of money, proper message is displayed to user
machine runs out of money, proper message is displayed to user
Verify that in case sudden
electricity loss in between the operation, the transaction is marked as null
and amount is not withdrawn from user’s account.
electricity loss in between the operation, the transaction is marked as null
and amount is not withdrawn from user’s account.
Ques.91. Write test cases
for Login.
for Login.
Ans. Verify that the login
screen is having option to enter username and password with submit button and
option of forgot password
screen is having option to enter username and password with submit button and
option of forgot password
Verify that user is able to
login with valid username and password
login with valid username and password
Verify that user is not able
to login with invalid username and password
to login with invalid username and password
Verify that validation
message gets displayed in case user leaves username or password field as blank
message gets displayed in case user leaves username or password field as blank
Verify that validation
message is displayed in case user exceeds the character limit of the user name
and password fields
message is displayed in case user exceeds the character limit of the user name
and password fields
Verify that there is reset
button to clear the field’s text
button to clear the field’s text
Verify if there is checkbox
with label “remember password” in the login page
with label “remember password” in the login page
Verify that the password is
in encrypted form when entered
in encrypted form when entered
Verify that there is limit
on the total number of unsuccessful attempts
on the total number of unsuccessful attempts
Ques.92. Write test cases
for Lift.
for Lift.
Ans. Verify the dimensions
of the lift
of the lift
Verify the type of door of
the lift is as per the specification
the lift is as per the specification
Verify the type of metal
used in the lift interior and exterior
used in the lift interior and exterior
Verify the capacity of the
lift in terms of total weight
lift in terms of total weight
Verify the buttons in the
lift to close and open the door and numbers as per the number of floors
lift to close and open the door and numbers as per the number of floors
Verify that lift moves to
the particular floor as the button of the floor is clicked
the particular floor as the button of the floor is clicked
Verify that lift stops when
up/down buttons at particular floor are pressed
up/down buttons at particular floor are pressed
Verify if there is any
emergency button to contact officials in case of any mishap
emergency button to contact officials in case of any mishap
Verify the performance of
the floor – time taken to go to a floor
the floor – time taken to go to a floor
Verify that in case of power
failure, lift doesn’t free-fall and get halted in the particular floor
failure, lift doesn’t free-fall and get halted in the particular floor
Verify lifts working in case
button to open the door is pressed before reaching the destination floor
button to open the door is pressed before reaching the destination floor
Verify that in case door is
about to close and an object is placed between the doors, if the doors senses
the object and again open or not
about to close and an object is placed between the doors, if the doors senses
the object and again open or not
Verify the time duration for
which door remain open by default
which door remain open by default
Verify if lift interior is
having proper air ventilation
having proper air ventilation
Verify lighting in the lift
Verify that at no point
lifts door should open while in motion
lifts door should open while in motion
Verify that in case of power
loss, there should be a backup mechanism to safely get into a floor or a backup
power supply
loss, there should be a backup mechanism to safely get into a floor or a backup
power supply
Verify that in case multiple
floor number button are clicked, lift should stop at each floor
floor number button are clicked, lift should stop at each floor
Verify that in case capacity
limit is reached users are prompted with warning alert- audio/visual
limit is reached users are prompted with warning alert- audio/visual
Verify that inside lift
users are prompted with current floor and direction information the lift is
moving towards- audio/video.
users are prompted with current floor and direction information the lift is
moving towards- audio/video.
Ques.93. Write test cases
for an ecommerce application.
for an ecommerce application.
Ans. Verify that user is
able to navigate through all the products across different categories
able to navigate through all the products across different categories
Verify that all the links
and banners are redirecting to correct product/category pages and none of the
links arr broken
and banners are redirecting to correct product/category pages and none of the
links arr broken
Verify that the company logo
is clearly visible
is clearly visible
Verify that all the text –
product, category name, price and product description are clearly visible
product, category name, price and product description are clearly visible
Verify that all the images –
product and banner are clearly visible
product and banner are clearly visible
Verify that category pages
have relevant product listed specific to the category
have relevant product listed specific to the category
Verify that correct count of
total products are listed on the category pages
total products are listed on the category pages
Search – Verify that on
searching all the product satisfying the search criteria are visble on the
search result page
searching all the product satisfying the search criteria are visble on the
search result page
Search – Verify the more
relevant product for the search term are displayed on the top for a particular
search term
relevant product for the search term are displayed on the top for a particular
search term
Search – Verify that count
of products is correctly displayed on the search result page for a particular
search term
of products is correctly displayed on the search result page for a particular
search term
Filtering – Verify that
filtering functionality correctly filters product based on the filter applied
filtering functionality correctly filters product based on the filter applied
Filtering – Verify that
filtering works correctly on category pages
filtering works correctly on category pages
Filtering – Verify that
filtering works correctly on the search result page
filtering works correctly on the search result page
Filtering – Verify that
correct count of total products is displayed after a filter is applied
correct count of total products is displayed after a filter is applied
Sorting – Verify that all
the sort options work correctly – correctly sort the products based on the sort
option chosen
the sort options work correctly – correctly sort the products based on the sort
option chosen
Sorting – Verify that
sorting works correctly on the category pages
sorting works correctly on the category pages
Sorting – Verify that
sorting works correctly on the search result page
sorting works correctly on the search result page
Sorting – Verify that
sorting works correctly on the pages containing filtered result, after applying
filters
sorting works correctly on the pages containing filtered result, after applying
filters
Sorting – Verify that
product count remains intact irrespective of sorting option applied
product count remains intact irrespective of sorting option applied
Ques.94. What should be the
psychology testing?
psychology testing?
The two main stakeholders in
software development life cycle – Testers and Developers have different
mindsets while approaching an application. Testers tend to have a more
stringent approach of examining the software. Most of the time they are looking
to “break the application”. Whereas, developers have the mindset to
“make the application work”.
software development life cycle – Testers and Developers have different
mindsets while approaching an application. Testers tend to have a more
stringent approach of examining the software. Most of the time they are looking
to “break the application”. Whereas, developers have the mindset to
“make the application work”.
ISTQB has defined certain psychological
factors that influence the success of testing-
factors that influence the success of testing-
Independence – Testers
should enjoy a certain degree of independence while testing the application
rather than following a straight path. This can be achieved by different
apporaches like off-shoring the QA process, getting test strategies and other
test plans by someone not following any sort of bias.
should enjoy a certain degree of independence while testing the application
rather than following a straight path. This can be achieved by different
apporaches like off-shoring the QA process, getting test strategies and other
test plans by someone not following any sort of bias.
Testing is often looked upon
as destructive activity as it aims at finding flaws in system. But QA personnel
should present testing as required and integral part, presenting it as
as destructive activity as it aims at finding flaws in system. But QA personnel
should present testing as required and integral part, presenting it as
constructive activity in
overall sofware development lifecycle by mitigating the risks at early stages.
overall sofware development lifecycle by mitigating the risks at early stages.
More often than not, tester
and developers are at the opposite end of spectrum. Testers need to have good
interpersonal skills to communicate their findings without indulging in any
sort of tussle with the developers.
and developers are at the opposite end of spectrum. Testers need to have good
interpersonal skills to communicate their findings without indulging in any
sort of tussle with the developers.
All the communication and
discussions should be focussed on facts and figures(risk analysis, priority
setting etc). Emphasizing that the collaborative work of developers and testers
will lead to better software.
discussions should be focussed on facts and figures(risk analysis, priority
setting etc). Emphasizing that the collaborative work of developers and testers
will lead to better software.
Empathy is one characterstic
that definitely helps in testing. Testers empathizing with developers and other
project stakeholders will lead to better relation between the two. Also,
empathizing with end users will lead to a software with better usability of the
product.
that definitely helps in testing. Testers empathizing with developers and other
project stakeholders will lead to better relation between the two. Also,
empathizing with end users will lead to a software with better usability of the
product.
Reference- ISTQB Foundation
Level Syllabus – The Certified Tester Foundation Level in Software Testing
Level Syllabus – The Certified Tester Foundation Level in Software Testing
Ques.95. What is the
difference between testing and debugging?
difference between testing and debugging?
Ans. Testing is the
primarily performed by testing team in order to find the defects in the system.
Whereas, debugging is an activity performed by development team. In debugging
the cause of defect is located and fixed. Thus removing the defect and
preventing any future occurrence of the defect as well.
primarily performed by testing team in order to find the defects in the system.
Whereas, debugging is an activity performed by development team. In debugging
the cause of defect is located and fixed. Thus removing the defect and
preventing any future occurrence of the defect as well.
Other difference between the
two is – testing can be done without any internal knowledge of software
architecture. Whereas debugging requires knowledge of the software architecture
and coding.
two is – testing can be done without any internal knowledge of software
architecture. Whereas debugging requires knowledge of the software architecture
and coding.
Ques.96. Explain Agile
methodology?
methodology?
Ans. Agile methodology of
software development is based on interative and incremental approach. In this
model, the application is broken down into smaller build on which different
cross functional team work together providing rapid delivery along with
adapting to changing needs at the same time.
software development is based on interative and incremental approach. In this
model, the application is broken down into smaller build on which different
cross functional team work together providing rapid delivery along with
adapting to changing needs at the same time.
Ques.97. What is scrum?
Ans. A scrum is a process
for implementing Agile methodology. In scrum, time is divided into sprints and
on completion of sprints, a deliverable is shipped.
for implementing Agile methodology. In scrum, time is divided into sprints and
on completion of sprints, a deliverable is shipped.
Ques.98. What are the
different roles in scrum?
different roles in scrum?
Ans. The different roles in
scrum are –
scrum are –
Product Owner – The product
owner owns the whole development of the product, assign tasks to the team and
act as an interface between the scrum team(development team) and the
stakeholders.
owner owns the whole development of the product, assign tasks to the team and
act as an interface between the scrum team(development team) and the
stakeholders.
Scrum Master – The scrum
master monitors that scrum rules get followed in the team and conducts scrum
meeting.
master monitors that scrum rules get followed in the team and conducts scrum
meeting.
Scrum Team – A scrum team
participate in the scrum meetings and perform the tasks assigned.
participate in the scrum meetings and perform the tasks assigned.
Ques.99. What is a scrum
meeting?
meeting?
Ans. A scrum meeting is
daily meeting in scrum process. This meeting is conducted by scrum master and
update of previous day’s work along with next day’s task and context is defined
in this meeting.
daily meeting in scrum process. This meeting is conducted by scrum master and
update of previous day’s work along with next day’s task and context is defined
in this meeting.
Ques.100. Explain TDD (Test
Driven Development).
Driven Development).
Ans. Test Driven Development
is a software development methodology in which the development of the software
is driven by test cases created for the functionality to be implemented. In
TDD, first the test cases are created and then code to pass the tests is
written. Later the code is refactored as per the standards.
is a software development methodology in which the development of the software
is driven by test cases created for the functionality to be implemented. In
TDD, first the test cases are created and then code to pass the tests is
written. Later the code is refactored as per the standards.
