Manual Testing Notes - TheTestingAcademy
Manual Testing Notes - TheTestingAcademy
https://thetestingacademy.com
Manual Testing
Interview Question and Answer
Freshers
Q1 What is Software Testing?
y
Software testing is a process of executing a program or application with the
intent of finding a software bug.
m
Q1.1 What do you understand by software testing?
de
Software testing is a validation process that confirms that a system works as
per the business requirements. It qualifies a system on various aspects such
as usability, accuracy, completeness, efficiency, etc. ANSI/IEEE 1059 is the
ca
global standard that defines the basic principles of testing.
gA
● Software testing is really required to point out the defects and errors
that were made during the development phases.
● It’s essential since it makes sure that the customer finds the
eT
● It’s important to ensure that the application should not result into any
failures because it can be very expensive in the future or in the later
stages of the development.
● It’s required to stay in business.
y
● Gaining confidence in and providing information about the level of
m
quality.
● To prevent defects.
de
● To make sure that the end result meets the business and user
requirements.
● To ensure that it satisfies the BRS that is Business Requirement
ca
Specification and SRS that is System Requirement Specifications.
● To gain the confidence of the customers by providing them a quality
product.
gA
Software testing is a huge domain but it can be broadly categorized into two
areas such as :
es
● Manual Testing – This is the oldest type of software testing where the
testers manually execute test cases without using any test automation
eT
y
Q7 What is Black Box Testing?
m
Black box testing involves testing a system with no prior knowledge of its
internal workings. A tester provides an input, and observes the output
generated by the system under test. This makes it possible to identify how the
de
system responds to expected and unexpected user actions, its response time,
usability issues and reliability issues.
ca
Black box testing is a powerful testing technique because it exercises a
system end-to-end. Just like end-users “don’t care” how a system is coded or
architected, and expect to receive an appropriate response to their requests, a
gA
tester can simulate user activity and see if the system delivers on its promises.
Along the way, a black box test evaluates all relevant subsystems, including
UI/UX, web server or application server, database, dependencies, and
integrated systems.
tin
structure, design, and coding are tested to verify input-output flow and
improve design, usability, and security. In white box testing, code is visible to
eT
testers, so it is also called Clear box testing, Open box testing, Transparent
box testing, Code-based testing, and Glass box testing.
A unit is a single testable part of a software system and tested during the
development phase of the application software.
TheTestingAcademy
https://thetestingacademy.com
The purpose of unit testing is to test the correctness of isolated code. A unit
component is an individual function or code of the application. White box
testing approach used for unit testing and usually done by the developers.
Whenever the application is ready and given to the Test engineer, he/she will
start checking every component of the module or module of the application
independently or one by one, and this process is known as Unit testing or
components testing.
y
Q11 What is Integration Testing?
Integration Testing is defined as a type of testing where software modules
m
are integrated logically and tested as a group. A typical software project
consists of multiple software modules, coded by different programmers. The
de
purpose of this level of testing is to expose defects in the interaction between
these software modules when they are integrated
Integration Testing focuses on checking data communication amongst these
ca
modules.
● Graph-Based Testing
● Error Guessing Technique
Th
y
Q16 What is regression testing?
m
Regression testing is a software testing practice that ensures an
application still functions as expected after any code changes, updates,
de
or improvements. Regression testing is responsible for the overall stability
and functionality of the existing features.
ca
Q17 What is Smoke and Sanity Testing?
:- Smoke Testing is performed to ascertain that the critical functionalities of
the program are working fine.
gA
:- Sanity Testing is done to check the new functionality/bugs have been fixed.
UI testing is a testing type that helps testers ensure that all the fields, labels,
buttons, and other items on the screen function as desired. It involves
checking screens with controls, like toolbars, colors, fonts, sizes, icons, and
es
:- Validation is the process of checking if the software (end product) has met
the client's true needs and expectations
y
Q22 What is the difference between a bug, a defect and an
m
error?
Error :- We can say that a mistake made by a programmer during coding is
de
called an error.
Defect :- an error found during the testing in the development phase is called a
ca
defect.(Deviation from requirement)
not.
eT
performing the test scenario, the test engineer needs to consider the
test cases for each scenario.
TheTestingAcademy
https://thetestingacademy.com
Phases Explanation
y
Requirement Analysis QA team understands the requirement in terms of
m
what we will testing & figure out the testable
requirements.
de
Test Planning In this phase, the test strategy is defined. Objective
& the scope of the project is determined.
ca
Test Case Here, detailed test cases are defined and developed.
Development The testing team also prepares the test data for
gA
testing.
Test Cycle Closure It involves calling out the testing team member
eT
y
m
The following figure is a graphical representation of the various stages
of a typical SDLC.
de
ca
gA
tin
es
eT
Th
y
the technical feasibility study is to define the various technical approaches that
m
can be followed to implement the project successfully with minimum risks.
Stage 2: Defining Requirements
de
Once the requirement analysis is done the next step is to clearly define and
document the product requirements and get them approved from the customer
or the market analysts. This is done through an SRS (Software Requirement
ca
Specification) document which consists of all the product requirements to be
designed and developed during the project life cycle.
Stage 3: Designing the Product Architecture
gA
SRS is the reference for product architects to come out with the best
architecture for the product to be developed. Based on the requirements
specified in SRS, usually more than one design approach for the product
architecture is proposed and documented in a DDS - Design Document
tin
Specification.
This DDS is reviewed by all the important stakeholders and based on various
es
A design approach clearly defines all the architectural modules of the product
along with its communication and data flow representation with the external
and third party modules (if any). The internal design of all the modules of the
Th
y
product defects are reported, tracked, fixed and retested, until the product
m
reaches the quality standards defined in the SRS.
de
Once the product is tested and ready to be deployed it is released formally in
the appropriate market. Sometimes product deployment happens in stages as
per the business strategy of that organization. The product may first be
ca
released in a limited segment and tested in the real business environment
(UAT- User acceptance testing).
Then based on the feedback, the product may be released as it is or with
gA
● New: When a new defect is logged and posted for the first time. It is
assigned a status as NEW.
eT
● Assigned: Once the bug is posted by the tester, the lead of the
tester approves the bug and assigns the bug to the developer team.
Th
● Open: The developer starts analyzing and works on the defect fix.
testing remains pending from the testers end, the status assigned is
“pending retest.”
● Retest: Tester does the retesting of the code at this stage to check
whether the defect is fixed by the developer or not and changes the
status to “Re-test.”
y
m
de
ca
gA
tin
es
eT
● Verified: The tester re-tests the bug after it got fixed by the
Th
● Reopen: If the bug persists even after the developer has fixed the
bug, the tester changes the status to “reopened”. Once again the bug
goes through the life cycle.
TheTestingAcademy
https://thetestingacademy.com
● Closed: If the bug is no longer exists then tester assigns the status
“Closed.”
y
● Deferred: If the present bug is not of a prime priority and if it is
m
expected to get fixed in the next release, then status “Deferred” is
assigned to such bugs.
de
● Not a bug: If it does not affect the functionality of the application then
the status assigned to a bug is “Not a bug”.
ca
Q27 What is the difference between Severity and Priority?
gA
Priority is basically a parameter that decides the order in which we should fix
tin
the defects.
y
the refill must have ink.
m
1. The grip of the pen: Verify if you are able to hold the pen
comfortably.
de
2. Writing: Verify if you are able to write smoothly.
3. Verify that the pen is not making any sound while writing.
4. Verify the ink flow. It should not overflow nor get a break either.
ca
5. Verify the quality of the material used for the pen.
6. Verify if the company or pen name is visible clearly.
7. Verify if the pen color or text written on the pen is not getting
gA
removed easily.
8. Verify, whether the width of the line drawn by the pen is as per the
expectations or not.
tin
9. Verify the ink color, it should be consistent from the start till the
end.
es
12. Verify if the ink will not get dried easily by keeping the pen
open for some time. [Not for ink pen]
13. Verify if any other refill fits in the pen or not.
Th
14. Verify that the pen doesn’t have sharp edges or corners.
15. Verify if the ink and external assembly of the pen is made of
non-toxic material.
TheTestingAcademy
https://thetestingacademy.com
1. Put the pen in water and then try to write. Verify if you are able to
write with this pen. The pen can get wet because of the water spill
on the table or during the rainy season. It can be due to any
reason.
2. Drop the pen from some height (Table height) in the upside-down
position. Verify if you are able to write with this pen. By mistake,
y
the pen can any time fall on the ground. So testing this possibility
m
to know its impact, will help us in knowing the quality of the pen.
de
For both the above test cases, the frequency that these scenarios will happen
may not be very high but it is not even very low. So by knowing its impact, we
ca
will be able to know more about the quality of the pen.
4. Verify if the tip or nib of the pen is not destroyed after continuous
writing for hours.
eT
degrees).
TheTestingAcademy
https://thetestingacademy.com
y
● Verify the paint’s type and color.
m
● Verify if the chair’s material is brittle or not.
● Check if cushion is provided with chair or not.
de
● Check the condition when washed with water or the effect of water on
the chair.
● Verify that the dimension of chair is as per the specifications.
ca
● Verify that the weight of the chair is as per the specifications.
● Check the height of the chair’s seat from floor.
gA
field.
● Verify that the user is able to login by entering valid credentials and
clicking on the ‘Login’ button.
● Verify that the user is able to login by entering valid credentials and
pressing Enter key.
TheTestingAcademy
https://thetestingacademy.com
● Check that the user is not able to login with an invalid username and
password.
● Verify that the validation message gets displayed in case the user
leaves the username or password field blank.
y
● Verify that the reset button functionality is on the login page. Clicking
m
on it should clear the textbox’s content.
de
the login page.
● Verify that closing the browser should not log out an authenticated
ca
user. Launching the application should lead the user to the login state
only.
gA
● Verify the login session timeout duration. So, once logged in a user
cannot be authenticated for a lifetime.
● Verify that once logged in, clicking the back button doesn’t log out the
user.
TheTestingAcademy
https://thetestingacademy.com
● Verify if SQL Injection attacks work on the login page. The application
should not be vulnerable to SQL injection attacks.
● Verify that the XSS vulnerability should not work on the login page.
1 To 3 Years Of Experience
y
m
Q1 What is Quality Assurance and what are the different
activities involved in Quality assurance?
de
Quality assurance is a process-driven approach that checks if the process of
developing the product is correct and conforming to all the standards. It is
considered a preventive measure. This is because it identifies the weakness
ca
in the process to build software. It involves activities like document review, test
case review, walk-throughs, inspection.
testing, etc.
eT
● 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
y
coverage, reusability, etc.
m
● Gray box testing – In gray box testing, the tester has partial
access to the internal architecture of the system e.g. the tester
de
may have access to the design documents or database structure.
This information helps the tester to test the application better.
ca
Q4 Is there any difference between retesting and
regression testing?
gA
y
● The decision-making ability to analyze when to stop testing
m
● Ability to work under time constraints
● Ability to decide which tests to execute first
● Testing the entire application using an optimized number of test
de
cases
Ans. A test scenario is derived from a use case. It is used for end-to-end
testing of a feature of an application. A single test scenario can cater to
multiple test cases. Scenario testing is particularly useful when there is a time
es
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.
Th
TheTestingAcademy
https://thetestingacademy.com
y
○ Actual result – The actual result after executing the test steps.
m
○ Test Result – Pass/Fail status of the test execution.
○ Automation Status – Identifier of automation – whether the
application is automated or not.
de
○ Date – The test execution date.
○ Executed by – Name of the person executing the test case.
ca
Q10 What are some defect reporting attributes?
Ans. Some of the attributes of a Defect report are-
gA
defect title.
● Defect Description – A detailed description of the defect.
● Steps to reproduce – The steps to reproduce the defect.
es
the defect.
● Defect Severity – Based on the criticality of the defect, this field
can be set to minor, medium, major, or show stopper.
Th
● Priority – Based on the urgency of the defect, this field can be set
on a scale of P0 to P3.
TheTestingAcademy
https://thetestingacademy.com
y
or not. This data is created based on the business requirements.
m
Q13 What is defect priority?
Ans. A defect priority is an urgency of fixing the defect. Normally the defect
de
priority is set on a scale of P0 to P3 with the P0 defect having the most
urgency to fix.
ca
Q14 What is defect severity?
Ans. Defect severity is the severity of the defect impacting the functionality.
Based on the organization, we can have different levels of defect severity
gA
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.
y
Q19 What is Dynamic Testing?
Ans. The type of testing performed by executing or running the application
m
under test either manually or using automation is called dynamic testing.
de
Q20 Explain the different types of specification-based test
design techniques.
Ans. Specification-based test design techniques are also referred to as
ca
black-box 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-
gA
lying in the classes will have the same effect on the application.
For example, for testing a Square program (a program that prints the square
of a number), the equivalence classes can be-
y
Set of Negative numbers, whole numbers, decimal numbers, sets of large
m
numbers, etc.
de
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
ca
the range of 0-100, the boundary value analysis will include test data – 0,1,
99, 100
gA
Decision tables are particularly helpful in designing test cases for complex
business scenarios involving the verification of applications with multiple
combinations of input.
eT
Th
y
between the application and actors(users). These use cases are used for
m
depicting requirements and hence can also serve as a basis for acceptance
testing.
de
Q27 What is Test Coverage?
Ans. It is a metric that measures the amount of testing performed on software
while executing the test cases. Test coverage for any software can be
ca
calculated as the percentage of the number of test areas or coverage items
covered with respect to the total number of test areas.
The higher the test coverage, the more the part of the software gets covered
gA
by test cases and hence, the more effective the testing will be.
y
● Regression testing
m
Q31 What are the different levels of testing?
Ans. Testing can be performed at different levels during the development
process. Performing testing activities at multiple levels helps in the early
de
identification of bugs. The different levels of testing are –
1. Unit Testing
2. Integration Testing
ca
3. System Testing
4. Acceptance Testing
gA
y
Exploratory testing is a type of software testing where the tester actively
explores the application under test to identify defects, rather than following a
m
predetermined test plan or script. It's an iterative and interactive process that
allows the tester to gain a deeper understanding of the software and to
de
uncover unexpected issues or behaviors.
SDLC deals with development/coding of the software while STLC deals with
validation and verification of the software
es
testing?
Static testing: During the Static testing method, the code is not executed,
and it is performed using the software documentation.
y
Q41 What is acceptance testing?
m
Ans. Acceptance testing is 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.
de
Q42 What is UAT Testing?
Ans UAT testing is the last phase of the testing lifecycle. Its main focus is to
ca
validate that software is working in accordance with business requirements. It
also ensures that the application is user-friendly and can handle complex
scenarios at its best before releasing the product to real-world users.
gA
Ans. Beta testing is the testing done by end-users at the end user’s site. It
allows users to provide direct input about the software to the development
company.
TheTestingAcademy
https://thetestingacademy.com
y
Ans. In the case of Adhoc testing although there are no predefined or
documented test cases still testers have an understanding of the application.
m
While in the case of monkey testing testers don’t have any understanding of
the application.
de
Q49 What is exploratory testing?
Ans. Exploratory testing is a type of testing in which new test cases are added
ca
and updated while exploring the system or executing test cases. Unlike
scripted testing, test design and execution go parallel in exploratory testing.
application.
y
Q56 What is usability testing?
m
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
de
application.
hardware.
y
the application under test.
m
Q64 What is penetration testing?
Ans. Penetration testing or pen testing is a type of security testing in which an
application is evaluated(safely exploited) for different kinds of vulnerabilities
de
that any hacker could exploit.
ca
Q65 What is robustness 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
gA
Ans. Backend testing is a type of testing that involves testing the backend of
the system which comprises testing the databases and the APIs in the
eT
application.
Q68 What is A/B testing?
Ans. A/B testing is a type of testing in which the two variants of the software
Th
product are exposed to the end-users and on analyzing the user behavior on
each variant, the better variant is chosen and used thereafter.
y
Ans.
m
● Black-box testing is a type of testing in which the internal architecture
of the code is not required for testing. It is usually applicable for system
and acceptance testing.
de
● white-box testing requires internal design and implementation
knowledge of the application being tested. It is usually applicable for
Unit and Integration testing.
ca
Q72 What is the difference between smoke and sanity
testing?
gA
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.
eT
y
Q75. When should you stop the testing process?
m
The testing activity ends when the testing team completes the following
milestones.
de
Test case execution
The successful completion of a full test cycle after the final bug fix marks the
end of the testing phase.
ca
Testing deadline
The end date of the validation stage also declares the closure of the validation
gA
the intended level of code coverage (CC) ratio, then it can choose to end the
validation.
es
only operational time between failures and does not include repair times,
assuming the item is repaired and begins functioning again. MTBF figures are
often used to project how likely a single unit is to fail within a certain period of
Th
time.
y
○ Deadlines are breached
m
● Set a green flag if:
○ The entire functionality gets covered in test cases
○ All critical and major bugs must have a ‘CLOSED’ status
de
Q78 What are unit testing and integration testing?
Unit testing has many names such as module testing or component testing.
ca
Many times, it is the developers who test individual units or modules to check
if they are working correctly.
gA
Whereas, integration testing validates how well two or more units of software
interact with each other.
tin
● Bottom-up approach
No. System testing should start only if all modules are in place and they work
correctly. However, it should be performed before UAT (user acceptance
testing).
Th
y
7. GUI Objects Size difference and Color combinations etc.. are not easy
m
to find in Manual Testing.
de
more.
9. Executing the same tests, again and again, is time taking process as
ca
well as Tedious.
10. For every release you must rerun the same set of tests which can be
gA
tiresome.
testing.
Q82 What Test Plans consists of?
Test design, scope, test strategies, approach are various details that Test plan
Th
y
Here are the two principal reasons that make it impossible to test a program
entirely.
m
● Software specifications can be subjective and can lead to different
interpretations.
de
● A software program may require too many inputs, outputs, and path
combinations.
assert that the correct input is getting passed between various software
modules and sub-systems.
tin
y
the unavailability of proper documentation for testing?
m
If the standard documents like System Requirement Specification or Feature
Description Document are not available, then QAs may have to rely on the
de
following references, if available.
● Screenshots
● A previous version of the application
ca
● Wireframes
Another reliable way is to have discussions with the developer and the
gA
business analyst. It helps in solving the doubts, and it opens a channel for
bringing clarity on the requirements. Also, the emails exchanged could be
useful as a testing reference.
tin
Smoke testing is yet another option that would help verify the main
functionality of the application. It would reveal some very basic bugs in the
application. If none of these work, then we can just test the application from
es
y
m
Q93 Why developers shouldn’t test the software they wrote?
de
Developers make poor testers. Here are some reasons why:
● They try to test the code to make sure that it works, rather than testing
all the ways in which it doesn't work.
● Since they wrote it themselves, developers tend to be very optimistic
ca
about the software and don't have the correct attitude needed for
testing: to break software.
● Developers skip the more sophisticated tests that an experienced tester
gA
would perform to break the software. They follow the happy path to
execute the code from start to finish with proper inputs, often not
enough to get the confidence to ship software in production.
tin
However, it doesn't mean that developers shouldn't test the software before
sending it to the tester. Developer testing helps find many bugs that are
caused by programming errors. These are hard to find for a tester because
es
following tasks.
1. Automatically run the software.
2. Feed the input data to the system.
3. Examine the output with the expected outcome.
4. Fail the test if the results don’t match. Otherwise, pass the test.
TheTestingAcademy
https://thetestingacademy.com
Q96 What are the different HTTP status codes that a server
y
can return?
m
An HTTP status code is a three-digit number that indicates the status of an
incoming HTTP request, that is, if the request has been completed or not.
de
A server can send the following five types of responses for an HTTP request.
ca
1. Information (100 - 199): These status codes provide a temporary
gA
2. Success (200 - 299): Indicate that the incoming HTTP request was
successfully received, understood, and accepted.
es
3. Redirect (300 - 399): These status codes indicate further actions the
client should take to satisfy the HTTP request. It can mean that the
eT
4. A client error (400 - 499): Indicate a problem with the client who
initiated the HTTP request.
5. Server error (500 - 599): The 5XX status code indicates a problem on
the server while processing the request.
TheTestingAcademy
https://thetestingacademy.com
y
Q98 Which test cases are written first: white boxes or black
m
boxes?
Test cases for the black box testing are usually written first, followed by test
de
cases for the white box testing. An outline of the design or project plan and
the requirements document is required to write black-box test cases.
ca
Documents such as these are readily available at the beginning of the project.
The initial phase of a project isn't the right time to start white box testing
gA
The only difference is that the browser automation can test this very quickly
and often, whereas the same test would take a human tester a long time. It’s
part of automated testing. Some essential tools for browser testing include
Selenium, protractor.js, and cypress.
TheTestingAcademy
https://thetestingacademy.com
y
relationship between the requirements and other artifacts of the project right
from start to end. In simple words, it maps between test cases and customer
m
requirements.
de
Q101 What is the MAIN benefit of designing tests early in
the life cycle?
ca
It helps prevent defects from being introduced into the code.
3 To 5 Years Of Experience
Q19. When should you opt for manual testing over automation testing?
There are a lot of cases when manual testing is best suited over automation
testing, like:
y
● Short-time projects: Automated tests are aimed at saving time and
resources yet it takes time and resources to design and maintain them.
m
For example, if you are building a small promotional website, it can be
much more efficient to rely on manual testing.
de
● Ad-hoc Testing: In ad-hoc testing, there is no specific approach. Ad-hoc
testing is a totally unplanned method of testing where the
understanding and insight of the tester is the only important factor. This
ca
can be achieved using manual testing.
● Exploratory Test: This type of testing requires the tester’s knowledge,
experience, analytical, logical skills, creativity, and intuition. So human
gA
Top-Down – Testing happens from top to bottom. That is, high-level modules are
tested first, and after that low-level modules. Lastly, the low-level modules are
y
incorporated into a high-level state to guarantee the framework is working as it is
m
expected to.
de
Bottom-Up – Testing happens from base levels to high-up levels. The lowest level
modules are tested first and afterward high-level state modules. Lastly, the high-level
ca
state modules are coordinated to a low level to guarantee the framework is filling in
as it has been proposed to.
gA
tin
es
eT
Th
TheTestingAcademy
https://thetestingacademy.com
Q38. What is the difference between static testing and dynamic testing?
Static Testing is a white box testing Dynamic testing includes the process
technique, it includes the process of of execution of code and is done at
exploring the records to recognize the later stage of the software
y
the imperfections in the very early development lifecycle. It validates
m
stages of SDLC. and approves the output with the
de
expected results.
ca
Static Testing is implemented at the Dynamic testing starts during the
verification stage. validation stage.
gA
y
● Test cases completed with certain percentage passed
m
● When the test budget is depleted
● Coverage of code or functionality or requirements reaches a specified point
de
● Bug rate falls below a certain level
● When Beta or alpha testing period ends
ca
Q40. What if the software is so buggy it can’t really be tested at all?
Often testers encounter a bug that can’t be resolved at all. In such situations, the
gA
best bet is for testers to go through the process of reporting whatever bugs or
blocking-type problems initially show up, with the focus being on critical bugs. Since
tin
this type of problem can cause severe problems such as insufficient unit testing or
insufficient integration testing, poor design, improper build or release procedures, etc
es
Q41. How you test a product if the requirements are yet to freeze?
It’s possible that a requirement stack is not available for a piece of product. It might
Th
Q44. What are the cases when you’ll consider to choose automated testing
over manual testing?
Automated testing can be considered over manual testing during the following
situations:
y
● Tests need to be executed in a standard runtime environment
● When you have less time to complete the testing phase
m
● When there is a lot of code that needs to be repeatedly tested
● Reports are required for every execution
de
Q45. What is ‘configuration management’?
Every high-functioning organization has a “master plan” that details how they are
ca
supposed to operate and accomplish tasks. Software development and testing are
no different. Software configuration management (SCM) is a set of processes,
gA
● code
tin
● documentation
● problems
● change requests
es
to ensure that the overall product meets the requirements specified. So, no. The
system testing must start only if all units are in place and are working properly.
System testing usually happens before the UAT (User Acceptance Testing).
y
reducing the test execution time as the test scripts written once, can be run
m
automatically any number of times without any human intervention.
de
Ques.12. What are some advantages of automation testing?
ca
Ans. Some advantages of automation testing are-
gA
during testing.
eT
scripts.
y
2. Additional effort to write scripts is required upfront.
m
3. Automation scripts are limited to verification of the tests that are
de
coded. These tests may miss some error that is very glaring
Volume Testing.
TheTestingAcademy
https://thetestingacademy.com
Q47. What are some best practices that you should follow when writing test
cases?
Few guidelines that you need to follow while writing test cases are:
● Prioritize which test cases to write based on the project timelines and the risk
factors of your application.
● Remember the 80/20 rule. To achieve the best coverage, 20% of your tests
y
should cover 80% of your application.
m
● Don’t try to test cases in one attempt instead improvise them as you progress.
de
● List down your test cases and classify them based on business scenarios and
functionality.
ca
● Make sure test cases are modular and test case steps are as granular as
possible.
gA
● Write test cases in such a way that others can understand them easily &
modify if required.
● Always keep end-users’ requirements in the back of your mind because
tin
● Monitor your test cases regularly. Write unique test cases and remove
eT
Automation testing isn’t a replacement for manual testing. No matter how good
automated tests are, you cannot automate everything. Manual tests play an
important role in software development and come in handy whenever you have a
case where you cannot use automation. Automated and manual testing each have
their own strengths and weaknesses. Manual testing helps us understand the entire
problem and more flexibly explore other angles of tests. On the other hand,
TheTestingAcademy
https://thetestingacademy.com
automated testing helps save time in the long run by accomplishing a large number
of surface-level tests in a short time.
y
m
Ans. Test design techniques are different standards of test designing that
allow systematic and widely accepted test cases. The different test design
de
techniques can be categorized as static test design techniques and
dynamic test design techniques.
ca
1. Static Test Design Techniques – The test design techniques
gA
■ Walkthrough
■ Informal reviews
Th
■ Technical reviews
■ Audit
■ Inspection
■ Management review
○ Static design techniques using tools
TheTestingAcademy
https://thetestingacademy.com
y
evaluates the compliance of the code with
m
the different coding standards.
■ Analysis of code metrics – The tool used for
de
static analysis is required to evaluate the
ca
different metrics like lines of code,
complexity, code coverage, etc.
gA
architecture.
○ Structure-based – Structure-based test design
Th
y
m
de
Ques.45. What is structure-based testing?
ca
Ans. Structure-based test design techniques are also referred to as white
box testing. In these techniques, the knowledge of the code or internal
gA
architecture of the system is required to carry out the testing. The various
kinds of testing structure-based or white testing techniques are-
tin
y
have 2n test scripts.
m
● Multiple condition testing – In multiple condition testing, the
de
different combinations of condition outcomes are tested at least
ca
once. Hence for 100% coverage, we will have 2^n test scripts.
This is very exhaustive and very difficult to achieve 100%
gA
coverage.
tin
points).
TheTestingAcademy
https://thetestingacademy.com
5 To 7 Years Of Experience
y
m
de
ca
gA
tin
es
eT
Th