JAYAWANT SHIKSHAN PRASARAK MANDAL’s

Bhivrabai Sawant Polytechnic

(Approved by AICTE, New Delhi, Govt. of Maharashtra, Affiliated to MSBTE Mumbai)
Gat No. 720 (1&2), Wagholi, Pune-Nagar Road, Pune-412207)
Phone: 020 – 65335100 Tele fax: - + 91-020-65335100
E-mail: bspoly@rediffmail.com Website: www.jspm.edu.in
(Academic Year 2023-24)

Unit V (PIP) Solution

Course: - Software Testing Course Code : 22518

Que. Bloom’s Relevance

No. Level to
CO
1 1,2 Write any four limitations of Manual Testing

Marking Scheme (2M)

Answer Limitations of Manual Testing are as given below: COI504.5
1.Manual testing is slow and costly.
2.It is very labor intensive; it takes a long time to complete tests.
3.Manual tests don’t scale well. As the complexity of the software increases the complexity of the testing
problem grows exponentially. This leads to an increase in total time devoted to testing as well as total cost of
testing.
Manual testing is not consistent or repeatable. Variations in how the tests are performed as inevitable, for various
reasons.
4.One tester may approach and perform a certain test differently from another, resulting in different results on
the same test, because the tests are not being performed identically.
Lack of training is the common problem, although not unique to manual software testing.
5.GUI objects size difference and color combinations are not easy to find in manual testing.
6.Not suitable for large scale projects and time bound projects.
7.Batch testing is not possible, for each and every test execution Human user interaction is mandatory.
Comparing large amount of data is impractical.
8.Processing change requests during software maintenance takes more time
 2 1,2 State the need of automated testing tools. COI504.5

Marking Scheme (2M)

Answer ● 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

these to a test engineer.

● Once automated tests are created, they can easily be repeated, and they can be

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.

 3 1,2 Define software matrix and measurement. COI504.4
Marking Scheme (2M)
Answer Software Measurement: A measurement is an manifestation of the size, quantity, amount or
dimension of a particular attributes of a product or process. Software measurement is a titrate
impute of a characteristic of a software product or the software process. It is an authority within
software engineering. Software measurement process is defined and governed by ISO Standard.

Software Metric: A software metric is a measure of software characteristics which are

measurable or countable. Software metrics are valuable for many reasons, including measuring
software performance, planning work items, measuring productivity, and many other uses.
Within the software development process, many metrics are that are all connected. Software
metrics are similar to the four functions of management: Planning, Organization, Control, or
Improvement.

4 1,2 Differentiate between manual testing & automation testing. COI504.5

Marking Scheme (4M)
Answer Manual Testing Automation Testing

For observation manual testing allow human For observation automation testing does not
factor. allow human factor.

Automation testing can not give the

Manual testing checks the user-friendliness.
guarantee of user-friendliness.

In manual testing investment is required for In automation testing investment is required

humans resources because here humans test for automation tools because here testing is
the software instead of any software tools. done by some software tools.

Automation testing is not time consuming

Manual testing is time consuming because
because here process is done by some
here process is done by humans or manual.
software tools.
 In manual testing, there is a chance of human In automation testing, there is no chance of
errors because here testing is done by human errors because here testing is done by
humans. tools.

In manual testing, there is a possibility of In automation testing, there is no permission

Exploratory testing. of random testing.

In manual testing, there is no need of In automation testing, there is must a need of

programming knowledge. programming knowledge.

Automation testing uses frameworks like

Manual testing doesn’t use frameworks.
Data Drive, Keyword etc.

For nightly execution manual testing can not For nightly execution automation testing can
be batched. be batched.

5 1,2 Enlist factors considered for selecting a testing tool for test automation COI504.5
Marking Scheme 2M
Answer Factors considered for selecting testing tool for test automation are as follows:

 Compatibility with AUT (Application Under Test)

 Platform supported and tested

 Ease of Use

 Popularity

 Documentation and Support

 License Cost

 Test Management and Reporting

  Integration with other Tools

6 1,2 COI504.5
State the Advantages and Disadvantages of using testing tools
Marking Scheme (4M)
 Reduction of repetitive work: Repetitive work is very boring if it is done manually. People
tend to make mistakes when doing the same task over and over. Examples of this type of
repetitive work include running regression tests, entering the same test data again and
Answer again (can be done by a test execution tool), checking against coding standards (which can
be done by a static analysis tool) or creating a specific test database (which can be done by
a test data preparation tool).
 Greater consistency and repeatability: People have tendency to do the same task in a
slightly different way even when they think they are repeating something exactly. A tool
will exactly reproduce what it did before, so each time it is run the result is consistent.
 Objective assessment: If a person calculates a value from the software or incident reports,
by mistake they may omit something, or their own one-sided preconceived judgments or
convictions may lead them to interpret that data incorrectly. Using a tool means that
subjective preconceived notion is removed and the assessment is more repeatable and
consistently calculated. Examples include assessing the cyclomatic complexity or nesting
levels of a component (which can be done by a static analysis tool), coverage (coverage
measurement tool), system behavior (monitoring tools) and incident statistics (test
management tool).
 Ease of access to information about tests or testing: Information presented visually is
much easier for the human mind to understand and interpret. For example, a chart or
graph is a better way to show information than a long list of numbers – this is why charts
 and graphs in spreadsheets are so useful. Special purpose tools give these features directly
for the information they process. Examples include statistics and graphs about
test progress (test execution or test management tool), incident rates
(incident management or test management tool) and performance (performance testing
tool).
Disadvantages:

 Unrealistic expectations from the tool: Unrealistic expectations may be one of the
greatest risks to success with tools. The tools are just software and we all know that there
are many problems associated with any kind of software. It is very important to have clear
and realistic objectives for what the tool can do.
 People often make mistakes by underestimating the time, cost and effort for the initial
introduction of a tool: Introducing something new into an organization is hardly
straightforward. Once you purchase a tool, you want to have a number of people being
able to use the tool in a way that will be beneficial. There will be some technical issues to
overcome, but there will also be resistance from other people – both need to be handled
in such a way that the tool will be of great success.
 People frequently miscalculate the time and effort needed to achieve significant and
continuing benefits from the tool: Mostly in the initial phase when the tool is new to the
people, they miscalculate the time and effort needed to achieve significant and continuing
benefits from the tool. Just think back to the last time you tried something new for the
very first time (learning to drive, riding a bike, skiing). Your first attempts were unlikely to
be very good but with more experience and practice you became much better. Using a
testing tool for the first time will not be your best use of the tool either. It takes time to
develop ways of using the tool in order to achieve what is expected.
 Mostly people underestimate the effort required to maintain the test assets generated
 by the tool: Generally people underestimate the effort required to maintain the test assets
generated by the tool. Because of the insufficient planning for maintenance of the assets
that the tool produces there are chances that the tool might end up as ‘shelf-ware’, along
with the previously listed risks.
 People depend on the tool a lot (over-reliance on the tool): Since there are many benefits
that can be gained by using tools to support testing like reduction of repetitive work,
greater consistency and repeatability, etc. people started to depend on the tool a lot. But
the tools are just a software they can do only what they have been designed to do (at least
a good quality tool can), but they cannot do everything. A tool can definitely help, but it
cannot replace the intelligence needed to know how best to use it, and how to evaluate
current and future uses of the tool. For example, a test execution tool does not replace the
need for good test design and should not be used for every test – some tests are still
better executed manually. A test that takes a very long time to automate and will not be
run very often is better done manually.

7 1,2 Elaborate the concept of Software Metrics? Describe Product and Process metrics with suitable COI504.5
example
Marking Scheme (4M)
Answer Software Metric:

A software metric is a measure of software characteristics which are measurable or

countable. Software metrics are valuable for many reasons, including measuring software
performance, planning work items, measuring productivity, and many other uses. Within the
software development process, many metrics are that are all connected. Software metrics are
similar to the four functions of management: Planning, Organization, Control, or Improvement.
 Product Metric:

These are the measures of various characteristics of the software product. The two
important software characteristics are:

 Size and complexity of software.

 Quality and reliability of software.
 Process Metric:
 These are the measures of various characteristics of the software development
process. For example, the efficiency of fault detection. They are used to measure
the characteristics of methods, techniques, and tools that are used for developing
software.

8 List what are the different guidelines to be followed while selecting dynamic test tools. COI504.5
1,2
Marking Scheme (4M)
Answer
Criteria for Selecting Test Tools:
The Categories for selecting Test Tools are,
1. Meeting requirements-
There are plenty of tools available in the market but rarely do they meet allthe
requirements of a given product or a given organization. Evaluating different tools for
different requirements involve significant effort, money, and time. Given of the
plethora of choice available, huge delay is involved in selecting and implementing test
tools.
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. A good number of test tools require
their libraries to be linked with product binaries.
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.
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.

Subject Teacher Module Coordinator H.O.D.