lOMoARcPSD|32646394

STE-S-24 - STE 22518 summer 2024 model answer paper.

STE 22518 model answer paper summer
Computer Engineering (Anjuman-I-Islam’s A. R. Kalsekar Polytechnic)

Scan to open on Studocu

Studocu is not sponsored or endorsed by any college or university

Downloaded by Sakshi (sakshi1482005@gmail.com)
 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
SUMMER – 2024 EXAMINATION
Model Answer – Only for the Use of RAC Assessors

Subject Name: Software Testing Subject Code: 22518

Important Instructions to examiners:
1) The answers should be examined by key words and not as word-to-word as given in the model answer scheme.
2) The model answer and the answer written by candidate may vary but the examiner may try to assess the
understanding level of the candidate.
3) The language errors such as grammatical, spelling errors should not be given more Importance (Not applicable for
subject English and Communication Skills.
4) While assessing figures, examiner may give credit for principal components indicated in the figure. The figures drawn
by candidate and model answer may vary. The examiner may give credit for any equivalent figure drawn.
5) Credits may be given step wise for numerical problems. In some cases, the assumed constant values may vary and
there may be some difference in the candidate’s answers and model answer.
6) In case of some questions credit may be given by judgement on part of examiner of relevant answer based on
candidate’s understanding.
7) For programming language papers, credit may be given to any other program based on equivalent concept.
8) As per the policy decision of Maharashtra State Government, teaching in English/Marathi and Bilingual (English +
Marathi) medium is introduced at first year of AICTE diploma Programme from academic year 2021-2022. Hence if
the students in first year (first and second semesters) write answers in Marathi or bilingual language (English
+Marathi), the Examiner shall consider the same and assess the answer based on matching of concepts with model
answer.

Q. Sub Answer Marking

No. Q. Scheme
N.

1 Attempt any FIVE of the following: 10 M

a) Enlist objectives of software testing. 2M

Ans 1. Finding Errors:Testing is process of executing a program with an intention of ½ M for

finding an error. each
objective
2. Creating good test cases: A good test case is one that has a high probability of
finding yet undiscovered error.

3. Quality Improvement : Defects are fixed by the developer, so quality is improved.

4. Satisfying customer requirements: Testing demonstrates to the customer that

software works properly as per specification.

b) Compare Alpha testing and Beta testing. (Any two differences). 2M

Page No: 1 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
Ans 1 M for
each valid
point

c) Define a test plan. 2M

Ans A Test Plan is a detailed document that describes the test strategy, objectives, schedule, 2 M for
estimation, deliverables, and resources required to perform testing for a software product. correct
Test Plan helps us determine the effort needed to validate the quality of the application definition
under test. The test plan serves as a blueprint to conduct software testing activities as a
defined process, which is minutely monitored and controlled by the test manager.

d) List any four skills of software tester. 2M

Ans 1) Analytics skills ½ M for

each skill
2) Communication skills

3) Knowledge of test management tools

4) Negotiation skills

e) State the classification of defects. 2M

Ans 1. Requirement/Specification Defects: ½ M for

each
Requirement-related defects arise in a product when one fails to understand what the classificat
customer requires. ion

These defects may be due to the customer gap, where the customer is unable to define his
requirements.

Producer gap, where the developing team is not able to make a product as per requirements.

2. Design Defects:

Design defects occur when system components, interactions between system components,
interactions between the outside software/hardware, or users are incorrectly designed.

Design defects generally refer to the way of design creation or its usage while creating a
product.

Page No: 2 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
3. Coding Defects:

This defect arises when variables are not initialized properly, or variables are not declared
correctly, or database is not created properly.

Coding also needs adequate commenting to make it readable and maintainable in future.

4. Testing Defects:

These would encompass incorrect, incomplete, missing inappropriate test cases and test
procedures.

f) State the need of automated testing tool. (Any two). 2M

Ans Need for automated testing tools are: Any four

needs:
• An automated testing tool can playback pre-recorded and predefined actions,
compare the results to the expected behavior and report the success or failure of ½ M for
these to a test engineer. any 4
• Once automated tests are created, they can easily be repeated, and they can be needs.
extended to perform tasks impossible with manual testing.
• Automated Software Testing Saves Time and Money.
• Software tests must be repeated often during development cycles to ensure quality.
• Every time source code is modified software tests should be repeated. For each
release of the software, it may be tested on all supported operating systems and
hardware configurations. Manually repeating these tests is costly and time
consuming.
• Once created, automated tests can be run repeatedly at no additional cost, and they
are much faster than manual tests.
• Testing Improves Accuracy, Even the most conscientious tester will make mistakes
during monotonous manual testing. Automated tests perform the same steps
precisely every time they are executed and never forget to record detailed results.
• They can even be run on multiple computers with different configurations.
• Automated software testing can look inside an application and see memory
contents, data tables, file contents, and internal program states to determine if the
product is behaving as expected.
g) Define the terms error and defect in relation with software testing. 2M

Ans Error: An error is a human action that produces the incorrect result. 1 M for
each
Defect: A defect is an error or a bug in the application which is created. A programmer definition
while designing and building the software can make mistakes or errors. These mistakes or
errors mean that there are flaws in thesoftware. These are called defects.

2. Attempt any THREE of the following: 12 M

a) Write any four differences between quality assurance and quality control. 4M

Page No: 3 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
Ans 1 M for
each valid
point

b) Explain GUI testing with example. 4M

Ans GUI Testing 2 M for

explanatio
There are two types of interfaces for a computer application. n and 2 M
for
1.Command Line Interface is where you type text and the computer responds to that example.
command.

2.GUI stands for Graphical User Interface where you interact with the computer using
images rather than text.

• GUI testing is the process of testing the system's Graphical User Interface of the
Application Under Test.
• GUI testing involves checking the screens with the controls like menus, buttons,
icons, and all types of bars - toolbar, menu bar, dialog boxes and windows, etc.
• GUI is what the user sees. A user does not see the source code. The interface is
visible to the user.
• Especially the focus is on the design structure, images that they are working properly
or not.

GUI Testing Guidelines or traits:

1. Check Screen Validations

Page No: 4 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
2. Verify All Navigations

3. Check usability Conditions

4. Verify Data Integrity

5. Verify the object states

6. Verify the date Field and Numeric Field Format

Example: Prerequisite: User should be on www.flipkart.com

Test Test Case Name Actual Input Expected Actual Statu

Case Output Output s
No

TC-1 Already have an Click on Link should Link is Pass

account link already have be clickable. clickable.
an account
link It should go It is going to
to login page login page

TC-2 Login page Click on It should It is showing Pass

already have show mobile mobile
an account number number
link /email Id /email Id
field in form field in form

TC-3 Password Enter It should It is showing Pass

password show password in
=”123456” password in encrypted
encrypted form
form

TC-4 Language option 1.click on It should It is showing Pass

login option show page page content
content in in hindi
2.click on hindi
hindi link

TC-5 Placement of text 1.click on It should It is showing Pass

box and button on login option show mobile mobile
page number number
/email Id, /email Id,
password password
field and field and
submit submit button

Page No: 5 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
button in in form on
form on proper
proper position
position

TC-6 Navigation 1.click on It should It is Pass

login option convert converting
arrow into arrow into
2.Go to cursor cursor
mobile
number text
box

c) Describe the contents of "Test Summary Report' used in test reporting. 4M

Ans Test summary Report: The final step in a test cycle is to recommend the suitability of a Correct
product for release. explanatio
n4M
A report that summarizes the result of a test cycle is the test summary report.

There are two types of test summary report:

1. Phase wise test summary, which is produced at the end of every phase.

2. Final test summary report, which has all the details of testing done by all phases and
teams.

A summary report should be presented.

1.Test Summary Report Identifier

2 Description: Identify the test items being reported in this report with test id.
3 Variances: Mention any deviation from test Solution, test procedures, if any.
4 Summary of results should include: Tests that failed with any root cause description
and severity of impact of defect found by tests.
5 Comprehensive assessment and recommendation for release should include: “Fit for
release” assessment and Recommendation of release.

d) Differentiate between static and dynamic testing tools. (any four points) 4M

Ans Static Techniques Dynamic Techniques 1 M each

for 4
points.
Testing that is done without physically Testing in which system components are
executing a program or system. physically executed to identify defects.

No execution of code, product, Execution of test cases is an example of

documentation. a dynamic testing technique.

Page No: 6 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
Helps in establishing conformance to Dynamic testing is a validation
requirements view technique which includes dummy or
actual execution of work products to
evaluate it with expected behavior.

Checking the software product and It includes black box testing

related artifacts without executing them. methodology such as system testing and
structural white box testing.

The work product is reviewed by the The testing methods evaluate the
reviewer with the help of a checklist, product with respect to requirements
standards, any other artifact, knowledge, defined; designs created and mark it as
and experience, to locate the defect with ‘pass’ or ‘fail’.
respect to the established criteria.

It may include reviews, walkthroughs, This technique establishes ‘fitness for

inspection, and audits. use’ view.

3. Attempt any THREE of the following: 12 M

a) Distinguish between white box testing and black box testing. (any four points) 4M

Ans White box testing Black Box Testing 1 M for

each point
The tester needs to have the This technique is used to test
knowledge ofinternal code or the softwarewithout the
program. knowledge of internal code or
program
It aims at testing the structure It aims at testing the functionality
of the itembeing tested. of thesoftware
It is also called structural testing, It also knowns as data driven,
clear box closed boxtesting, data-, and
testing, code-based testing, or functional testing.
glass boxtesting.
Testing is best suited for a lower This type of testing is ideal for
level of testing like Unit Testing or higher levelsof testing like System
Integration testing. Testing, Acceptance testing.

Statement Coverage, Branch Equivalence partitioning, Boundary

coverage, and valueanalysis are Black Box testing
Path coverage are White technique
Box testingtechniques.
Can be based on detailed design Can be based on Requirement
documents. specification document
b) Explain the need of test deliverables & test plan for test planning. 4M

Ans Need of
The need of test deliverables for test planning include: Test

Page No: 7 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
deliverabl
es 2 M
Need of
Test plan
2M

Test Plan A test plan is a systematic approach to testing a system, i.e. software. The plan
typically contains a detailed understanding of what the eventual testing workflow will be.
Need of test plan:

• Test Plan Ensures all Functional and Design Requirements are implemented as
specified in the documentation.
• To provide a procedure for Unit and System Testing.
• To identify the documentation process for Unit and System Testing.

• To identify the test methods for Unit and

System Testing.

• P lanning Activities like:

1. Preparing test plan
2. Scope management
3. Deciding Test approach/ strategy
4. Setting up criteria for testing
5. Identifying responsibilities, staffing & Training needs:
6. Identifying Resource Requirement
7. Identifying Test Deliverables
8. Testing task
Page No: 8 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
c) Explain defect management process with suitable diagram. 4M

Ans Diagram-
Defect Management Process 1 M,

• Defects found during Verification and validation process in SDLC must be recorded Explanati
so that it helps in further analysis and root causes of the defect. on- 3 M

• The defects found during these phases are used to find weak areas of project /process so
that action can be initiated to strengthen it.

Defect Management Process: Prevention

• It is a process of improving quality and productivity by preventing the defects into a
software product.
• It is virtually impossible to eliminate the defects altogether.

• Implementation of techniques, methodology and standard processes are used to reduce

the risk of defects.

• Defect prevention is intended to remove the possibility of any defects before it occurs.

Defect Management Process: Deliverable Baselining

• Once the defect is fixed, retested and found to be closed, the product is created again.

• If the newly created product satisfies the acceptance criteria, it is base lined.

• Only base lined work products can go to the next stage.

Defect Management Process: Defect Discovery

• A defect is said to be discovered when it is brought to the attention of the developers and
acknowledged (i.e., “Accepted”) to be valid one.
• Team should find defects before they become major problems. As soon as a team finds
the defects, they should report them so that those can be resolved.
Page No: 9 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________

• Team should also make sure that defects should be acknowledged by developers and
should be valid one.
Defect Management Process: Defect Resolution

• Work by the development team to prioritize, schedule and fix a defect, and
document the resolution.
• This also includes notification back to the tester to ensure that the resolution is verified.

Defect Management Process: Process Improvement

• All problems are due to failures in the process involved in creating software.

• Defects give an opportunity to identify the problem with process used and update them.

• Better processes mean better products with less defect.

Defect Management Process: Management Reporting

• Analysis and reporting of defect information to assist management with risk

management, process improvement and project management.
d) Give any four differences between manual and automated testing. (Any 4 points) 4M

Ans Manual testing Automation Testing 1 M for

each point

Test cases are executed manually Test cases are executed with the help of
tools

Time required to execute test cases is high Time required to execute test cases is low

Initial investment required for manual Initial investment for automation testing
testing is lower is higher

Manual testing won’t be as accurate as it Automation testing can be accurate as it

includes human errors is performed by tools and scripts

It provides human observation, can be Cannot guarantee user friendliness or

used to assess user friendliness and good customer experience
customer experience

It is suitable for almost any software It is suitable only for stable systems and
product used mainly for regression.

Page No: 10 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
4. Attempt any THREE of the following: 12 M

a) State the process of performance testing. 4M

Ans 1 M for
diagram
3 M for
explanatio
n

1. Identify the Testing Environment:

Identifying the hardware, software, network configurations and tools available allows the
testing team to design the test and identify performance testing challenges early on.

2. Determine Performance criteria:

In addition to identifying metrics such as response time, throughput and constraints, identify
what are the success criteria for performance testing.

3. Plan and Design Performance Tests:

Identify performance test scenarios that take into account user variability, test data, and
target metrics. This will create one or two models.

4. Configure the Test Environment:

Prepare the elements of the test environment and instruments needed to monitor resources.

5. Implement Your Test Design:

Develop the tests.

6.Execute Tests:

In addition to running the performance tests, monitor and capture the data generated.

7. Analyze, Report, Retest:

Page No: 11 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
Analyze the data and share the findings. Run the performance tests again using the same
parameters and different parameters.
b) Explain people management in test planning. 4M

Ans People management in test planning involves coordinating and leading a team of testers to 1 M for
ensure that the testing process is efficient, thorough, and effective. each
aspect or
Below listed are some key aspects of people management in test planning: point
1. Team Composition: Assemble a diverse team with complementary skills and
experiences. Consider factors like technical expertise, domain knowledge, and
testing methodologies.
2. Clear Objectives: Communicate the objectives of the testing phase clearly to your
team. Ensure everyone understands the goals, scope, and expected outcomes of the
testing effort.
3. Assigning Roles and Responsibilities: Clearly define roles and responsibilities
within the testing team. Assign tasks based on individual strengths and expertise,
while also providing opportunities for skill development.
4. Setting Expectations: Establish clear expectations regarding timelines, quality
standards, and reporting mechanisms. Ensure everyone understands their individual
and collective responsibilities.
5. Effective Communication: Foster open and transparent communication within the
team. Encourage regular updates, discussions, and feedback sessions to address any
issues or challenges promptly.
6. Risk Management: Identify potential risks and challenges early in the planning
phase. Work with your team to develop mitigation strategies and contingency plans
to address any unforeseen issues during testing.

c) Explain test infrastructure management with its component. 4M

Ans Test Infrastructure Management 1 M for

diagram
3 M for
explanatio
n

Page No: 12 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
Test Infrastructure is made up of three essential elements:

• Test Case Database (TCDB)

• Defect Repository
• Configuration Management Repository and Tools

• Test Case Database (TCDB)

• Test Case
• Purpose: Record all the static information about the test.
• Attributes: Test case ID, Test case name, Test case Owner
• Test case product cross reference.
• Purpose: Provides mapping between test and corresponding feature
• Attributes: Test Case ID, Module ID
• Test case run history.
• Purpose: When was test run? What was the result?
• Attribute: Test Case ID, Run date, Time taken, Status
• Test Case –Defect Cross Reference
• Purpose: Provides mapping between test case and
defect
• Attribute: Test Case ID , Defect
ID
• Defect Repository
• It captures relevant details of defect.
• It is tool of communication.
• Defect Metrics are derived from defect repository.

• Configuration Management Repository and Tools

• Keeps track of change control of all the files/entities that makeup a
software product.
• Keeps track of version control of all the files/entities that makeup a
software product.
d) Describe any four limitations of manual testing. 4M

Ans Limitation of manual testing 1 M for

each
1. Time-consuming: Manual testing requires time since test cases must be executed limitation
manually. Complex software program testing could take some time. Testing teams
might not have enough time to cover all test cases because of the delay in software
development.
2. Human Error: Human errors can happen when testing is done manually. By failing
to test particular scenarios or by making mistakes when executing test cases, testers
may come up with erroneous results. These mistakes can make it impossible to find
flaws, which would affect the caliber of the software.

Page No: 13 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________

3. Not reusable- The test cases created for manual testing apply to a specific version
of software, but when the updates are made these test cases will become unusable
and need to be rewritten. Which does not seem to be an effective use of resources
and can lead increase the time. thus, slowing the development process
4. Difficult to Measure: It is challenging to quantify the manual testing process since
there are no objective metrics provided by manual testing to assess the software's
quality. It is difficult to assess the efficiency of the testing process since it is difficult
to keep track of the quantity of test cases executed, errors discovered, and test
coverage attained.

e) Describe acceptance testing with its advantages.

Ans Acceptance testing is software testing that evaluates whether a system meets its business Descriptio
and user requirements. Acceptance Testing is a method of software testing where a system n of
is tested for acceptability. The major aim of this test is to evaluate the compliance of the Acceptan
system with the requirements and assess whether it is acceptable for delivery or not. ce testing
It is formal testing according to user needs, requirements, and business processes conducted -2M
to determine whether a system satisfies the acceptance criteria or not and to enable the users,
customers, or other authorized entities to determine whether to accept the system or not. Advantag
Acceptance Testing is the last phase of software testing performed after System Testing and es - 2 M
before making the system available for actual use.
Advantages of Acceptance Testing
1.This testing helps the project team to know the further requirements from the users
directly as it involves the users for testing.
2.Automated test execution.
3.It brings confidence and satisfaction to the clients as they are directly involved in the
testing process.
4.It is easier for the user to describe their requirement.
5.It covers only the Black-Box testing process and hence the entire functionality of the
product will be tested.

5. Attempt any TWO of the following: 12 M

a) Prepare and write six test cases for Library Management System of college. 6M

Ans Test Test Case Actual Input Expected Actual Status 1 M for
Case Name output Output each valid
No test cases

TC1 User 1.Enter Login should Login is done Pass

Authenticatio Username: be done successfully.
n “22203A0011 successfully
”

Page No: 14 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
2.Enter
Password=”sa
ndip@1234”

TC2 Borrowing Enter Book 1.Book should 1.Book is Pass

Book Name: “Data be issued to issued to
structure using student. student.
C”
2.Book 2. Book is
marked as marked as
borrowed borrowed in
the database.

TC3 Borrowing Enter Book It should It is displaying Pass

Book Name: display message
“123abcd” message “Enter Valid
“Enter Valid book name”
Book Name”

TC4 Borrowing Enter Book It should It is displaying Pass

Book Name: “Data display message:
structure and message "Book not
algorithm” "Book not available"
available"

TC5 Returning Return a It should mark It is marking Pass

Book borrowed book Book as Book as
returned in returned in
student and student and
library library
database. database.

TC6 Fine Return a book It should Fine calculated Pass

calculation after the due display and displayed
date calculated fine in student
in student login.
login.

TC7 Notification 1.Enter book Student should Student Pass

after Name: “Data Receive receives
borrowing structure and notification for notification for
book algorithm” successfully successfully
borrowed borrowed
2.Collect book books books
from librarian.

b) With the help of diagram, describe client-server testing. 6M

Ans The Client-Server application consists of two systems, one is the Client, and the other is the 2 M for
Server. Here, the client and server interact with each other over the computer network. any
relevant

Page No: 15 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
In Client-Server application testing, the client sends requests to the server for specific diagram,
information and the server sends the response back to the client with the requested and 4 M
information. Hence, this testing is also known as two-tier application testing. for
relevant
explanatio
n

FIG: Client Server Application

Testing approaches of client server system is as follows.

Component Testing

➢For testing Client and server individually approach and test plan need to be defined.

➢ One may have to devise simulators to replace corresponding components while testing
the component targeted by the test.

➢ When server is tested, we may need a client simulator, while testing of client may need
server simulator.

Integration Testing

➢After successful testing of servers, clients, and network, they are brought together to form
the system and system test cases are executed.

➢ Communication between client and server is tested in integration testing.

Page No: 16 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
Performance Testing

➢ System performance is tested when number of clients are communicating with server at
a time.

➢ we can test the system under maximum load as well as normal load expected.

Concurrency Testing

➢ It may be possible that multiple users may be accessing same record at a time.

➢ Concurrency testing is required to understand the behaviour of a system under such

circumstances.

Disaster Recovery Testing

➢ When the client and server are communicating with each other, there exists a possibility
of breaking of the communication due to various reasons or failure of either client or server
or link connecting them.

➢ It may involve testing the scenario of such failure at different points in the system and
action taken by the system in each case.

Testing for extended periods

➢ In client server application it may be expected that server is running 24*7 for extended
period.

➢ one need to conduct testing over an extended period to understand if service level of
network and server deteriorates over time due to some reasons.

Compatibility Testing

➢ Servers may be in different hardware, software or operating environment than the

recommended one.

➢ Client may differ significantly from the expected environmental variables.

Page No: 17 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
➢ Testing must ensure that performance must be maintained on the range of hardware and
software configurations.

c) How to select a testing tool? Explain in detail. 6M

Ans 6 M for
correct
explanatio
n

Selection criteria for testing tool

1. Meeting requirements

• There are plenty of tools available in the market, but rarely do they meet all the
requirements of a given product or a given organization.

• Evaluating different tools for different requirements involve significant effort, money, and
time.

• The tool must match its intended use.

• Wrong selection of a tool can lead to problems like lower efficiency and effectiveness of
testing may be lost. Selection criteria for testing tool

2. Technology expectations:

• Test tools in general may not allow test developers to extends/modify the functionality of
the framework

• So, extending the functionality requires going back to the tool vendor and involves
additional cost and effort.

• Different phases of a life cycle have different quality-factor requirements. Tools required
at each stage may differ significantly. Selection criteria for testing tool

3. Training/skills:

• While test tools require plenty of training, very few vendors provide the training to the
required level.

• Organization level training is needed to deploy the test tools.

• As the user of the test suite are not only the test team but also the development team and
other areas like configuration management.

Page No: 18 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
• If the testers do not have proper training and skill, then they may not be able to work
effectively. Selection criteria for testing tool

4. Management aspects:

• A test tool increases the system requirement and requires the hardware and software to be
upgraded.

• This increases the cost of the already- expensive test tool.

• Select affordable tools. Cost and benefits of various tools must be compared before making
final decision.

6. Attempt any TWO of the following: 12 M

a) Explain the need of stubs and drivers with diagram and its importance in 6M
software testing.

Ans 2 M for
diagram,
2 M for
explanatio
n of stub
and
Driver
and 2 M
for
importanc
e of stub
and driver
Drivers: The module where the required inputs for the module under test are simulated for
the purpose of module or unit testing is known as a Driver module. The driver module may
print or interpret the result produced by the module under test.

Stubs: The module under testing may also call some other module which is not ready at the
time of testing. There is need of dummy modules required to simulate for testing, instead
of actual modules. These are called stubs.

Importance: Stubs and Drivers works as a substitute for the missing or unavailable
module. They are specifically developed, for each module, having different functionalities.
Generally, developers and unit testers are involved in the development of stubs and drivers.

Page No: 19 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
Their most common use may be seen in the integration incremental testing, where stubs are
used in top bottom approach and drivers in a bottom-up approach.

b) Explain in detail, how to prepare a test plan with suitable example. 6M

Ans Note: Consider any relevant example Template

- 2 M,
• Test plan gives insight into testing activity completely. Correct
• Test Plan Ensures all Functional and Design Requirements are implemented as explanatio
specified in the documentation. n-4M
• The test plan addresses various levels of testing for Unit testing, Integration testing,
System Testing, and acceptance testing.
• It explains who does testing, why test is performed, how tests are performed, how
test is conducted and when test is scheduled.
Following is the test plan for ‘Cam Scanner’ which is installed on mobile.

1 Test Plan Identifier TP_10

2 Introduction The purpose of this document is to create and test

plan for camscanner. The purpose of testing this
program is to check the correct operation of its
functionality and ease of use.

3 Test Items Working with CAMSCANNER

4 Features to be tested
• SCAN
ID CARD
DOCS
BOOK
QR CODE
• PROCESS FILES

• PDF TOOLS

• TOOLS

• SHARE

• MOVE/COPY

• RENAME

Page No: 20 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
• DELETE

5 Approach • On the test object: o functional o non-

functional
• According to the requirements o positive o
negative
• By degree of preparedness - intuitive testing
(ad hoc)

6 Item Pass/Fail All test cases with high priority are closed with the
Criteria result - pass.
The test coverage is checked and sufficient, where
the criterion of sufficiency is not less than 99%
of the coverage of requirements by tests.
The test report was compiled and approved by the
team lead and customer.

7 Suspension Criteria: The appearance and entering the bug-tracking

system of blocking bugs.

Closing the blocking bug in the bug tracking system

Resumption Criteria:

8 Test Deliverables Test plan, test case specification, test case, test
summary report

9 Test Tasks • Writing a test plan

• Writing test cases
• Development of criteria for the success of
testing.
• Conducting the testing and evaluation of the
results
• Creating test reports

10 Environmental needs Cam Scanner Mobile Application

Internet
Mobile/Computer
Android OS

11 responsibilities Function Responsible

ality and
Responsi
bilities

Page No: 21 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
Test Engineer 1
SCAN

Test Engineer 2
PROCES
S FILES

PDF Test Engineer 3

TOOLS
TOOLS Test Engineer 4
SHARE Test Engineer 5
MOVE/C Test Engineer 5
OPY
RENAM Test Engineer 6
E
DELETE Test Engineer 6
12 Staffing and To perform the tasks, you need to have the following
Training Needs knowledge and skills:

• practical knowledge application of the

WhatsApp is needed.
• knowledge and ability to apply in practice the
basic techniques of test design.
• Knowledge of various types of testing
including functional and non-functional.

13 Schedule The deadline for completion of all works and

delivery of the project is 01/07/2024 by 5.00pm

14 Risks and
Contingencies • Insufficient human resources for testing the
Possible risks during application in deadlines.
testing
• Changing the requirements for the product

15 Approvals Team Lead Test engineer 1

Test Manager

Quality Manager

c) Draw a diagram for defect life cycle and write example for defect template. 6M

Ans Defect life cycle Diagram

of defect
life cycle
- 2 M and

Page No: 22 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
Defect
Template
Example -
4M

Example of defect template for withdrawing an amount from ATM

ID Def_01

Project ATM Simulator

Product Cash Simulator ATM

Release Version v1.0

Module Home Page > Simulator

Detected Build v1.1

Version

Summary Limited denomination options in cash

withdrawal function, restricting cash
withdrawal only till 3000.

Description No option of withdrawing of amount excess of

3000

Steps to Replicate 1) Open the website

2) Select our programs

3) Proceed to Digital Inclusion tools and select

cash machine simulator (ATM)

4) Select language and skip to simulator

5) Enter the card

Page No: 23 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)

 lOMoARcPSD|32646394

MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

(Autonomous)
(ISO/IEC - 27001 - 2013 Certified)
__________________________________________________________________________________________________
6) Select the account type

7) Go to Other functions and select cash

withdrawal

Actual Results It has displaying limited options of

denominations in cash withdrawal option.

Expected Results It should add more options in denominations in

withdrawal function or it should take amount
input from the user

Attachments

Remarks Causes inconvenience to the user in terms of

limited cash withdrawal options.

Defect Severity High

Defect Priority High

Reported By abc

Assigned To xyz

Status Assigned

Page No: 24 | 24

Downloaded by Sakshi (sakshi1482005@gmail.com)