GOVERNMENT POLYTECHNIC, AMRAVATI

(AN AUTONOMOUS INSTITUTE OF GOVERNMENT OF MAHARASHTRA)

CURRICULUM DEVELOPMENT CELL

--------------------------------------------------------------------------------------------------------------
PROGRAMME TITLE: DIPLOMA IN COMPUTER ENGINEERING/INFORMATION
TECHNOLOGY
COURSE CODE: FC 5463
COURSE TITLE: SOFTWARE TESTING

TEACHING SCHEME:
TOTAL CONTACT
LEVEL OF PRERE- WEEKLY TOTAL TOTAL HOURS
COURSE QUISITE CONTACT HRS. CREDITS WEEKS
L T P L T P
V - 03 - 02 05 16 48 - 32

EXAMINATION SCHEME:

THEORY(Marks) PRACTICAL(Marks)
ESE ESE PA TOTAL ESE PA TOTAL
PAPER (Marks)
HRS.
3Hrs MAX. 70 30* 100 25# 25^ 150
MIN. 28 --- 40 10 10
@: Internal Assessment #: External assessment-Practical based $: online examination
(*) Under the Theory PA, Out Of 30 Marks, 20 Marks is the Average of Two Tests and 10 Marks are for Micro project-
(^) Under practical PA Continuous Assessment of Practical Work is to be done by Course Teacher as per CDC norms.
For the courses having only practical examination, PA has two parts (i) Continuous Assessment of Practical
work - 60% and (ii) microproject-40%.

1. RATIONALE:
In today’s software environment writing bug-free code is challenging task, which make
software testing important tool to get the quality software. Testing techniques include the
process of executing a program or application with the intent of finding software bugs and
verifying that the software product is fit for use . Students will learn the way to find bugs by
applying types, levels and methods of software testing on applications with effective test
planning approach. It also covers manual testing.

2. COURSE OUTCOMES (COs)

At the end of this course, student will be able to: -
1) Apply various software testing methods.
2) Prepare test cases for different types and levels of testing.
3) Prepare test plan for an application.
4) Identify bugs to create defect report of given application.
5) Test software for performance measures using automated testing tools.
6) Apply different testing tools for a given application.

[1]
 3. DETAILED CONTENTS: THEORY

Unit Unit Outcomes (UOs) Topic and Sub-topics CO Hrs Marks

(In cognitive domain) No.
Unit 1. 1a. Identify errors and 1.1 Software Testing, Objectives 1 06 08
Basics of bugs in the given of Testing.
Software Testing program. 1.2 Failure, Error, Fault, Defect,
and Testing 1b. Prepare test case for Bug Terminology.
Methods the given application. 1.3 Test Case, When to Start and
1c. Describe the Entry Stop Testing of Software
and Exit Criteria for (Entry and Exit Criteria).
the given test 1.4 Verification and Validation (V
application. Model), Quality Assurance,
1d. Validate the given Quality Control.
application using V 1.5 Methods of Testing: Static and
model in relation with dynamic Testing
quality assurance. 1.6 The box approach: White Box
1e. Describe features of Testing: Inspections,
the given testing Walkthroughs, Technical
method. Reviews, Functional Testing,
Code Coverage Testing, Code
Complexity Testing.
1.7 Black Box Testing:
Requirement Based Testing,
Boundary Value Analysis,
Equivalence Partitioning,
Unit 2. 2a.Apply specified 2.1 Levels of testing 2 10 14
Types and testing level for a web Unit Testing: Driver, Stub
Levels of Testing based application. Integration Testing: Top-
2b. Apply Acceptance Down Integration, Bottom-Up
testing for given web Integration, Bi-Directional
based application. Integration
2c. Apply the given 2.2 Testing on Web Application:
performance testing Performance Testing:
for an application. Load Testing, Stress Testing.
2d.Generate test cases for Security Testing. Client-
the given application Server Testing
using regression and 2.3 Acceptance Testing: Alpha
GUI testing. Testing and Beta Testing.
Special Tests: Regression
Testing, GUI Testing,
Unit 3. 3a. Prepare test plan for 3.1 Test Planning : Preparing a 3 10 12
Test the given application. Test Plan, Deciding Test
Management 3b. Identify the resource Approach, Setting Up
requirement of the Criteria for Testing,
given application. Identifying Responsibilities,
3c. Prepare test cases for Staffing, Resource
the given application. Requirements, Test
3d. Prepare test report of Deliverables, Testing Tasks
executed test cases 3.2 Test Management: Test
for given application. Infrastructure Management,

[2]
 Test People Management.
3.3 Test Process: Base Lining a
Test Plan, Test Case
Specification.
3.4 Test Reporting: Executing
Test Cases, Preparing Test
Summary Report.
Unit 4. 4a. Classify defects on 4.1 Defect Classification, Defect 4 08 12
Defect the basis estimated Management Process.
Management impact. 4.2 Defect Life Cycle, Defect
4b. Prepare defect Template
template on the 4.3 Estimate Expected Impact of
given application. a Defect, Techniques for
4c. Apply defect Finding Defects, Reporting a
management process Defect.
on the given
application.
4d.Write procedure to
find defect using the
given technique.
Unit 5. 5a. Improve testing 5.1 Manual Testing and Need for 5 08 12
Automated efficiency using Automated Testing Tools,
Tools and automated tool for Advantages and
Measurements given application. disadvantages of Using
5b. Identify different Tools
testing tools to test 5.2 Selecting a Testing Tool
the given application. 5.3 When to Use Automated
5c. Describe Metrics Test Tools, Testing Using
and Measurement for Automated Tools.
the given application. 5.4 Metrics and Measurement:
5d. Explain Object Types of Metrics, Product
oriented metrics used Metrics and Process Metrics,
in the given testing Object oriented metrics in
application testing.
Unit 6. 6a.Able to use bug 6.1 Selenium Testing Tool: 6 06 12
Use of different tracking Tool Features, Web driver,
Software testing 6b. Able to create Use of selenium to write
tools automation script tests, Methods,
6c. Apply testing tool 6.2 Mantis Bug Tracker:
for given application Features, User interface,
Creating Projects, Reporting
bugs
6.3 Test link: Features of
Test link, Creating Test
projects, Creating Test
plan, Creating test suite,
Creating test case,
Assigning test case to test
Plan

[3]
4. LIST OF PRACTICALS:

Sr PRACTICAL OUTCOMES (PrOs) CO

No. NO.
1 Identify system specification & design test cases for purchase order 1
Management.
2 Analyze and design test cases for simple calculator application.(BB Testing) 1
3 Design test cases for e-commerce (Flipkart, Amazon) login form 2
4 Design test cases for Web Pages Testing any Web Sites 2
5 Prepare test plan for an identified Mobile application. 3
6 Design test plan and test cases for Notepad (MS Window based) Application. 3
7 Prepare defect report after executing test cases for Withdrawn of amount from 4
ATM Machine.
8 Prepare defect report after executing test cases for any login form. 4
9 Design and run test cases for WordPad (MS Windows based). Using an Automated 5
tool.
10 Design and run test cases for MS Word application using an Automation Tool. 5
11 Test given website (Google, Facebook) using selenium. 6
12 Perform Bug tracking of a given application using mantis Bug Tracker. 6

Note
i. A suggestive list of PrOs is given in the above table. More such PrOs can be added to
attain the COs and competency. All above practicals need to be performed so that the
student reaches the ‘Precision Level’ of Dave’s ‘Psychomotor Domain Taxonomy’ as
generally required by the industry.

ii. The ‘Process’ and ‘Product’ related skills associated with each PrO are to be assessed
according to a suggested sample given below:

Sr. Performance Indicators Weightage

No. in %
1 Preparation of system specification, designing test plan 40
using MS Excel.
2 Preparation of defect report 20
3 Execution of test cases using automation tool. 20
4 Answer to sample questions 10
5 Submit report in time 10
Total 100

The above PrOs also comprise of the following social skills/attitudes which are Affective
Domain Outcomes (ADOs) that are best developed through the laboratory/field based
experiences:
a. Follow safety practices.
b. Practice good housekeeping.
c. Demonstrate working as a leader/a team member.
d. Maintain tools and equipment.
e. Follow ethical Practices.

[4]
 The ADOs are not specific to any one PrO, but are embedded in many PrOs. Hence, the
acquisition of the ADOs takes place gradually in the student when s/he undertakes a series of
practical experiences over a period of time. Moreover, the level of achievement of the ADOs
according to Krathwohl’s ‘Affective Domain Taxonomy’ should gradually increase as
planned below:
• ‘Valuing Level’ in 1st year
• ‘Organizing Level’ in 2nd year
• ‘Characterizing Level’ in 3rd year

5. SUGGESTED STUDENT ACTIVITIES

Other than the classroom and laboratory learning, following are the suggested student-
related co-curricular activities which can be undertaken to accelerate the attainment of the
various outcomes in this course.
a. Prepare journal based on practical performed in laboratory.
b. Give seminar on relevant topic.
c. Use different open source software testing for developed softwares.
d. Undertake micro-projects.

6. SUGGESTED INSTRUCTIONAL STRATEGIES

Following are suggested instructional strategies, which the teacher can adopt for the
attainment of the various outcomes in this course:
a. Massive open online courses (MOOCs) may be used to teach various topics/sub
topics.
b. The teacher needs to ensure to create opportunities and provisions for co-curricular
activities.
c. Guide student(s) in undertaking micro-projects.
d. Arrange visit to nearby industries and workshops for understanding use of testing
tools for testing of softwares.
e. Use automated tool to explain various types of testing.
f. About 10-15% of the topics/sub-topics/contents which is relatively simpler or
descriptive in nature may be given to the students for self-directed learning and
assess the development of the COs through classroom presentations. Keep the record
of the topics/sub-topics/contents given to the students.

7. SUGGESTED MICRO-PROJECTS.
Only one micro-project is planned to be undertaken by a student that needs to be assigned to
him/her in the beginning of the semester. In all semesters, the micro-project are group-based
(5-6 students) to build up skill and confidence in every student to become problem solver so
that he/she contributes to the projects of the industry. The micro-project could be industry
application based, internet-based, workshop-based, laboratory-based or field-based. Each
micro-project should encompass two or more COs which are in fact, an integration of UOs
and ADOs. Each student will have to maintain dated work diary consisting of individual
contribution in the project work and give a seminar presentation of it before submission. The
total duration of the micro-project should not be less than 16 (sixteen) student engagement
hours during the course.The student ought to submit micro-project by the end of the
semester to develop the industry oriented COs.
A suggestive list of micro-projects is given here. Similar micro-projects could be added by
the concerned faculty:
a. Library management :book issue/book stock system
b. E-commerce website testing.

[5]
 c. Generate test plan for a given application.
d. Generate defect reports for a given application.
e. Develop a test plan a given project.
f. Any other micro-projects suggested by subject faculty on similar line.

8. MAJOR EQUIPMENTS/INSTRUMENTS REQUIRED

Sr Equipment Name with Broad Specification Practical

No. No.
1 Computer system All
(Any computer system with basic configuration)
2 Selenium 3,11
3 Mantis Bug Tracker 12
4 IBM Rational Functional Tester 5
5 Spreadsheet Package 1,2,3
6 Bugzila 4

9. SUGGESTED SPECIFICATION TABLE FOR QUESTION PAPER DESIGN

Unit Unit Title Marks Distribution of Theory Marks

No. per Unit R U A
Level Level Level

1 Basics of Software Testing and 08 04 04 -

Testing Method
2 Types and Levels of Testing 14 04 06 06
3 Test Management 12 - 06 06
4 Defect Management 12 - 04 04
5 Testing Tools and Measurements 12 06 04 04
6 Use of different Software testing 12 - 06 06
tools
Total 70 14 30 26

R= Remember, U= Understanding, A=Application and above (Bloom’s Revised taxonomy)

Note: This specification table provides general guidelines to assist student for their learning
and to teachers to teach and assess students with respect to attainment of UOs. The actual
distribution of marks at different taxonomy levels (of R, U and A) in the question paper may
vary from above table.

10. SUGGESTED LEARNING RESOURCES:

Sr. Title Of Book Author Publication

No.
1. Software Testing: Principles and Srinivasan Desikan PEARSON Publisher:
Practices Gopalaswamy Pearson India
Ramesh Edition: 1st Edition, 2005
ISBN: 9788177581218,

[6]
 817758121X
2. Software Testing: Principles, Limaye M. G. Tata McGraw Hill
Techniques Education, New Delhi.
and Tools Edition: 1st Edition, 2007
ISBN 10: 0070139903 /
ISBN 13: 9780070139909
3. Software Testing: Principles and Chauhan Naresh Oxford University Press
Practices Noida – 201301, Uttar
Pradesh,
Edition: 5th Edition
4. Software Testing Singh Yogesh Cambridge University
Press, Bangluru. ISBN
978-1-107-65278-1

11. SUGGESTED SOFTWARE/LEARNING WEBSITES

a. http://www.selenium.com
b. http://en.wikipedia.org/wiki/Test_automation
c. http://en.wikipedia.org/wiki/Software_testing#Testing_tools
d. http://www.softwaretestingsoftware.com
e. www.toolsqa.com

12. COURSE CURRICULUM DEVELOPMENT COMMITTEE:

SR. NAME DESIGNATION INDUSTRY/INSTITU

NO. TE
1 Mr.P.U.Malve Lecturer in Computer Engineering. Government Polytechnic
Amravati
2 Mr.P.P.Katgaonkar Lecturer in Information Technology Government Polytechnic
Amravati
Government Polytechnic, Amravati Programme Board of Studies (Computer Engineering)
has approved the above course curriculum on 19/07/2018 and is adopted for Computer
Engineering Programme.

CHAIRMAN
PROGRAMME BOARD OF STUDIES,
COMPUTER ENGINEERING
GOVERNMENT POLYTECHNIC,
AMRAVATI.

The General Board of Studies has approved the above course curriculum on 24/07/2018
The Governing Body has approved the above course curriculum on 06/08/2018

[7]
[8]