Government Polytechnic Waghai

Computer Engineering Department

Important Question
Software Testing(4360706) Date:- 05-04-2025

CO1 Describe importance of Software Testing to enhance the quality of software

products.
1 Define Software Testing. Write Down the importance of Software Testing. 3
2 Describe Verification and Validation model (V-model) of software testing. Write 7
down the minimum two characteristics and advantages of the V model.
3 Describe Software Testing Life cycle (STLC) in detail. 7
4 Differentiate Between Automation Testing and Manual Testing. 3
5 What are the differences between the Software Development Life Cycle (SDLC) and 3
the Software Testing Life Cycle (STLC)?
6 Compare the testing approaches in the Waterfall and Agile SDLC models. 4
Agile Testing Waterfall Testing

In agile testing, testing is not In waterfall testing, testing is a

a separate phase. separate phase.

In agile testing, testing is In waterfall testing, testing is

performed alongside the carried out only after the
development. completion of development.

In agile testing, development In waterfall testing, development

team and testing team work team and testing team work
together. separately.

In waterfall testing, testers may or

In agile testing, testers are
may not be involve in the
involved in the requirements.
requirements..

In agile testing, acceptance In waterfall testing, acceptance

testing is carried out after testing is carried out only in the
every iteration. end.

In agile testing, regression In waterfall testing, regression

testing is carried out after testing is carried out only in the
every iteration. end.
 In agile testing, there is no In waterfall testing, there is
time delays between coding normal time delays between
and testing. coding and testing.

In agile testing, different In waterfall testing, testing levels

testing levels overlap. can’t overlap.

Waterfall testing methodologies

Agile testing methodologies
are very rigid compared to agile
are more flexible.
testing.

In agile testing, the test plan

In waterfall testing, the test plan
is reviewed after each
is not discussed during a cycle.
cycle/sprint.

7 Analyze the impact of testing principles on the effectiveness of software testing 3

processes.
Ans.
 Early identification of defects leads to a decrease in the cost and effort of
fixing them. The earlier bugs are found, the easier and cheaper they are to
resolve.
 Testers can focus on the most critical and high-risk areas of the application,
ensuring maximum coverage for the most important functionality, rather
than trying to test everything.
 testers focus their efforts on the high-risk components that are more likely
to have defects, improving testing efficiency.
 It emphasizes the need to continuously improve and expand test cases to
uncover more complex or hidden defects, rather than relying on the same
tests over and over.
 ensure that the software meets not just functional requirements but also
user needs and expectations.
 Continuous feedback enables quicker identification of issues and fosters
collaboration between developers and testers.

 ખામીઓની વહેલી ઓળખ તેમને સુધારવાના ખર્ચ અને પ્રયત્નોમાાં ઘટાડો તરફ દોરી

જાય છે . જે ટલી વહેલી ભૂલો મળી આવે છે , તેટલી જ ઝડપથી તેનુાં નનરાકરણ કરવુાં સરળ

અને સસતુાં બને છે .

• testers એનલલકેશનના સૌથી મહત્વપૂણચ અને ઉચ્ર્-જોખમવાળા ક્ષેત્રો પર ધ્યાન કેનરિત કરી

શકે છે , દરેક વસતુનુાં પરીક્ષણ કરવાનો પ્રયાસ કરવાને બદલે, સૌથી મહત્વપૂણચ કાયચક્ષમતા માટે

મહત્તમ કવરેજ સુનનનચર્ત કરે છે .

• testers તેમના પ્રયત્નો ઉચ્ર્-જોખમવાળા ઘટકો પર ધ્યાન કેનરિત કરે છે જે માાં ખામીઓ

હોવાની શક્યતા વધુ હોય છે , જે નાથી પરીક્ષણ કાયચક્ષમતામાાં સુધારો થાય છે .

 • તે એક જ test પર વારાંવાર આધાર રાખવાને બદલે, વધુ જટટલ અથવા છુ પાયેલા ખામીઓને

ઉજાગર કરવા માટે test કેસોમાાં સતત સુધારો અને નવસતરણ કરવાની જરૂટરયાત પર ભાર મૂકે છે .

• ખાતરી કરો કે સોફ્ટવેર ફક્ત કાયાચત્મક આવશ્યકતાઓ જ નહીં પરાંતુ વપરાશકતાચની જરૂટરયાતો

અને અપેક્ષાઓ પણ પૂણચ કરે છે .

• સતત પ્રનતસાદ સમસયાઓની ઝડપી ઓળખને સક્ષમ કરે છે અને નવકાસકતાચઓ અને પરીક્ષકો

વચ્ર્ે સહયોગને પ્રોત્સાહન આપે છે .

8 Discuss the role of quality assurance in software testing. 3

• Software Quality Assurance (SQA) is simply a way to assure quality in the
software.
• It is the set of activities that ensure processes, procedures as well as
standards are suitable for the project and implemented correctly.
• Software Quality Assurance is a process that works parallel to Software
Development.
• It focuses on improving the process of development of software so that
problems can be prevented before they become major issues.
• Software Quality Assurance is a kind of Umbrella activity that is applied
throughout the software process.
• સોફ્ટવેર ક્વોનલટી એસયોરરસ (SQA) એ સોફ્ટવેરમાાં ગુણવત્તાની ખાતરી
આપવાનો એક માગચ છે .
• તે પ્રવૃનત્તઓનો સેટ છે જે સુનનનચર્ત કરે છે કે પ્રટિયાઓ, પ્રટિયાઓ તેમજ માપદાંડો
પ્રોજે ક્ટ માટે અનુકૂળ છે અને તેનો યોગ્ય રીતે અમલ કરવામાાં આવ્યો છે .
• સોફ્ટવેર ગુણવત્તાની ખાતરી એ એક પ્રટિયા છે , જે સોફ્ટવેર ડેવલપમેરટને સમાાંતર
કામ કરે છે .
• તે સોફ્ટવેરના નવકાસની પ્રટિયાને સુધારવા પર ધ્યાન કેનરિત કરે છે , જે થી સમસયાઓ
મુખ્ય સમસયા બને તે પહેલાાં તેને અટકાવી શકાય.
• સોફ્ટવેર ગુણવત્તાની ખાતરી એ એક પ્રકારની અમ્બ્રેલા પ્રવૃનત્ત છે , જે સમગ્ર સોફ્ટવેર
પ્રટિયા દરનમયાન લાગુ પડે છે .

CO2 Apply black-box and white-box testing techniques effectively.

1 Differentiate between Black Box Testing and White Box Testing. 4
2 Explain Unit Testing and Integration Testing with example. 4
3 List out the various techniques of Block Box Testing. Describe any two techniques 7
used in Black Box Testing with example.
4 Explain Smoke Testing with example. 3
5 Describe Regression Testing with example. 4
• This type of testing is done to ensure that new code changes do not have
any side effects on the existing functionalities.
• It ensures that the old code still works once the latest code changes are
done.
• Is the practice of running an old test suite after each change or the bug fix
to ensure that no new bug has been introduced due to the change.
 Regression Testing Example – Amazon
 Consider the e-commerce giant Amazon, which is a multi-billion-dollar
business that relies on its website for revenue generation. To uphold its
functionality, reliability, and performance, regression testing plays a crucial
role.
Let’s take a scenario of Adding a New Product Category.
Imagine that Amazon decides to expand its product offerings by introducing a new
category called “Smart Home Devices” alongside existing categories like
“Electronics” and “Clothing.”
Possible regression cases would be:
 Homepage Functionality: Verify that the homepage displays the new “Smart
Home Devices” category alongside existing ones without any display issues.
 Category Navigation: Ensure that users can smoothly navigate to the “Smart
Home Devices” category page and return to the homepage without glitches.
 Search Functionality: Ensure that the search bar accurately returns results
for smart home devices when users search for them and do not mix with
other products.
 User Accounts: Verify that user accounts can be created, updated, and
utilized for purchasing smart home devices and other products.
 Payment Processing: Test payment gateways specific to purchases and
guarantee secure and error-free transactions.
 Mobile Responsiveness: Check that the website remains mobile-responsive,
allowing users to access and shop for smart home devices on various
devices.

6 List out the various techniques of White Box Testing. Describe any two techniques 7
used in White Box Testing with example.
7 Explain the difference between black-box testing and white-box testing approaches 7
in software testing.

Black Box White Box

Testing without knowledge of Testing with knowledge of

the internal code structure; the internal code structure;
focuses on inputs and focuses on logic, paths, and
outputs. structures.

focus on Functionality and focus on Internal logic, code

user requirements. structure, and pathways.

No knowledge of the internal Detailed knowledge of the

code or system architecture. internal code and system
architecture.
 test basis are Requirements, test basis are Source code,
specifications, and user algorithms, and internal logic.
scenarios.

type of test are Functional type of test are Unit testing,

testing, system testing, integration testing, and code
acceptance testing. coverage analysis.

Broad, focusing on overall Narrower, focusing on

system functionality. specific code paths and logic.

Test cases derived from Test cases derived from

functional requirements and code and design documents.
user stories.

Test management tools, and Debuggers, code analysis

functional testing tools. tools, and unit testing
frameworks.

8 Describe the techniques used in equivalence partitioning and boundary value 7

analysis in software testing.
9 List four types of non-functional testing techniques commonly used in software 4
testing, along with a brief explanation of each.
10 You are tasked with testing a new mobile banking application. Describe how you 7
would apply the black-box testing approach to ensure the security features of the
application are robust.
ans:
 the focus should be on validating the application's functionality without
knowing its internal code structure.

Authentication & Authorization

 Incorrect login: Input wrong credentials (e.g., invalid

username/password) and verify that the app denies access and returns
a generic error message.
 Brute force attack: Simulate multiple failed login attempts (e.g., 5-10
times) and check if the application locks the account or asks for a
CAPTCHA/2FA.
  Two-factor authentication (2FA): Verify that the app prompts for
and validates a second factor (e.g., OTP via SMS or an authentication
app) after entering valid login credentials.
 Role-based access: Test the access control for different roles. Ensure
regular users cannot access admin features and vice versa.

Session Management

 Session timeout: Leave the application idle for a set period and check
if it logs out the user or prompts them for re-authentication.

Data Encryption & Protection

 Encryption during transmission: Verify that all communication between the

mobile app and the backend is encrypted using HTTPS/TLS.

Error Handling and Logging

 Error messages: Ensure that error messages do not reveal sensitive

information. For example, an error message should not indicate whether
the issue is with the username, password, or backend system.
 Detailed logs: Verify that logs do not contain sensitive information, such as
passwords, credit card numbers, or other personal data.

Boundary Value Analysis (BVA)

 Test boundary inputs (e.g., extremely large or small values, edge

cases) for fields like account numbers or transaction amounts to ensure
the system handles them securely.
 Example: Try entering an account number with 50 characters (if the
limit is 40 characters) to check if the system handles this input without
vulnerability.

Equivalence Partitioning

 Divide input values into equivalence classes and test each class with
representative values.
 Example: Test valid, invalid, and boundary inputs for the login form
(e.g., valid email/password, invalid email, password with too few
characters).

11 State the purpose of smoke testing in software development and provide a brief 4
description of how it is conducted.
12 You are part of a development team tasked with creating a new web application. 7
Describe how you would incorporate static testing techniques to ensure the quality
of the codebase throughout the development process.
Ans:
 • Static Testing is a type of software testing in which software application is
tested without code execution
• Static Testing also known as Verification testing or Non-execution testing is
a type of Software Testing method that is performed to check the defects in
software without actually executing the code of the software application.
• The main objective of static testing is to improve the quality of software
applications by finding errors in early stages of software development
process.
there are different stages where you need to perform static testing.

 Stage 1: Requirement phase: When the requirements are

documented and available for review, you can start with static testing.
With this, you can make sure that the requirements are clear,
complete, consistent, and unambiguous. This reduces the risk of
misunderstandings or missing requirements later in development.
 Stage 2: UX design phase: Once the design documents are prepared
and the software development is about to start, you can perform static
testing here. To catch design flaws, identify potential performance
bottlenecks, and ensure that the design adheres to technical and
functional requirements.
 Stage 3: Coding phase: As the software is being developed, you can
perform static testing, especially before proceeding with dynamic
[Link] find coding errors, and syntax violations, and ensure
adherence to coding standards without executing the code. This can
be done through peer reviews, code walkthroughs, or static code
analysis tools.
 Stage 4: Test planning phase: After you get the test case plan, you
can proceed with static testing. This will ensure that the test cases
cover all the requirements and that there are no ambiguities or missing
test scenarios. Reviewing test documentation ensures that the tests
will be effective in detecting defects.
  Stage 5: Maintenance phase: Post getting the complete software,
whenever there are any changes made during the maintenance phase,
you can perform static testing. This is to ensure that changes or
enhancements are properly documented and that they do not
introduce new issues.

CO3 Develop effective test cases based on specifications, utilizing appropriate

templates and methodologies.
1 Differentiate between Test Cases and Test Scenarios. 3
2 Design Test Cases on Login Module of website. 4
3 Describe Test case Template with example by considering any two functional 7
requirement of any one web application module
4 Explain Test Planning of Software testing management in detail. 3
5 Design Test Cases on Inbox Functionality of Gmail. 4
6 Describe RTM (Requirement Traceability Matrix) in software testing with example. 7
7 Construct setting up criteria for testing in software testing management. 3
8 Explain the key components of test planning in software development. 4
9 Discuss the significance of test reporting in software testing management. 7
10 Construct significance of deciding the test approach in software testing 3
management.
11 Describe the process of creating test cases in software testing. 4
12 Explain the concept of a Requirements Traceability Matrix (RTM) in software testing. 7

BY

Aarti R Chaudhari

Computer Engg Department

[Link]