PESIT- Bangalore South Campus
Hosur Road (1km Before Electronic city)
Bangalore – 560 100
Department of MCA
COURSE INFORMATION SHEET
SOFTWARE TESTING (13MCA444)
1. GENERAL INFORMATION:
Academic Year: 2016 Semester: IV
Title Code Duration (hrs)
Lectures 48 Hrs
Software Testing 13MCA444 Seminars 4 Hrs
Total 52 Hrs
2. PRE REQUIREMENT STATEMENT:
Student should know the concepts of Software Engineering
3. COURSE DESCRIPTION:
Testing is the process of evaluating a system or its component(s) with the intent to
find whether it satisfies the specified requirements or not. Testing is executing a system in order to
identify any gaps, errors, or missing requirements in contrary to the actual requirements. This
course will give you a basic understanding on software testing, its types, methods, levels, and other
related terminologies. Finally It also contains planning, monitoring and documenting test cases.
4. LEARNING OUTCOMES
After completion of the subject the students would have learnt
1.Compare various testing concepts and levels
2.Consider, evaluate and apply adequate test techniques
3.Explain test-related measures involved in test processes
4.Plan, manage, automate software testing activities
5.Conduct and report on original research on software testing tools and techniques 6.Types of errors and fault
model.
5. FACULTY DETAILS:
Faculty Name : Mrs.Manjula.C.M.Prasad
Department : MCA
Room Number: 508
Phone Number:
Mail-id :
[email protected] Contact Hours : College Hours
Consultation Time: College Hours
6. VENUE AND HOURS/WEEK:
All lectures will normally be held in 603,604 in 6th Floor.
Lecture Hours/week: 4Hrs
7. MODULE MAP:
Class # Chapter # Topics to be covered % of portions covered
Reference Cumulative
Chapter
1 Humans, Errors and Testing,
Software Quality;
2 Requirements, Behavior and
Correctness;
3 Unit –1 Correctness Vs Reliability;
Basics of Software Testing Testing and Debugging; Test
Metrics; 13.46 13.46
4 Software and Hardware
Testing; Testing and
Verification;
5 Defect Management; Execution
History;
6 Test Generation Strategies; Static
Testing;
7 Test Generation from Predicates.
8 Sensitivity,
9 Redundancy,
10 Unit – 2 Basic Principles Restriction, Partition,
11 Visibility and Feedback 11.53 24.99
12 Test specification and cases
13 Adequacy criteria, comparing
criteria
14 Basic definitions, Test
cases,Insights from a venn diag
15 Unit -3 A perspective on Identifying test cases,
16 Testing Errors and fault taxonomies 13.46 38.45
17 Level of testing examples
18 The triangle
problem,Commission problem,
19 SATM problem
20 The currency converter, Saturn
windshield wiper
21 Unit 4- Boundary value testing, Boundary value analysis,
Equivalence class testing, Robustness testing
22 Decision table based testing Worst-case testing, special value
testing,
23 Random testing, Equivalence
classes
24 Equivalence test cases for 13.46 51.91
Triangle problem
25 Nextdate function and
commission problem
26 Guidelines and observations,
Decision tables
27 Test cases for triangle problem
28 DD paths,
29 Test coverage metrics
30 Unit-5 Path testing, Data flow Basis path testing
31 testing Guidelines and observations 13.46 65.37
32 Definition use testing
33 Slice based testing
34 Guidelines and observations
35 Traditional view of testing levels
36 Alternative life cycle models
37 The SATM systems
38 Separating integration 11.53 76.90
39 System testing
40 Unit -6 Levels of Testing, Guidelines and observations
Integration testing
41 Assumptions in fault-based
testing,
42 Mutation Analys is, Fault-based
Unit-7 Fault Based Testing Adequacy Criteria;
43 Variations on mutation Analysis;
From Test case specification to
Test Cases, 11.53 88.43
44 Scaffolding, Generic vs specific
Scaffolding,
45 Test Oracles, Self checks as
oracles,
46 Capture and Replay.
47 Quality and Process, Test and
Analysis strategies and plans,
48 Unit-8 Planning and Monitoring Risk Planning, Monitoring the
the Process, Documenting An Process,
49 alysis and Test Improving the process, The
quality team, 11.57 100.00
50 Organizing documents, Test
strategy document,
51 Analysis and test plan, Test
design specifications documents,
52 Test and analysis reports.
12.RECOMMENDED BOOKS/JOURNALS/WEBSITES
Text Books:
1.Adithya P.Mathur “ Foundations of Software Testing – Fundamental Algorithms and Techniques”, Pearson
Education India, 2011 (Listed topics only from Chapter 1.1 to 1.12 and 2.7)
2.MauroPezze, Michael Young, Software testing and Analysis- Process, Principles and Techniques, Wiley India,
2012 (Chapters 3,4,5,6,9,10,11,12,13,14,16,17,20,24)
Reference Books:
1.Kshirasagara Naik, Priyadarshi Tripathy: Software Testing and Quality Assurance, Wiley India 2012
2.M.G.Limaye: Software Testing-Principels, Techniques and Tools – McGrawHill, 2009
3.Brain Marick: The Craft of Software Testing, Pearson Education India, 2008
4.Ron Patton: Software Testing, 2nd Edition, Pearson Education, India, 2013
9 ASSIGNMENTS-
The students has to submit 2 assignments, one before first internal and the third one before second internal
exam
Assignment -1 : Students should work on any one testing tool.
Assignment -2 : Seminars (journal papers w.r.t software testing)
10 THEORY ASSESSMENT WRITTEN EXAMINATION
Paper Structure
No. Of Questions 8 Main Questions No. of questions to be answered 5
Exam date June 2016 Paper Duration 3 Hrs
Total Marks 100 Pass Marks 40
CONTINUOUS ASSESSMENT
Parameters Weighting (%)
Class Test(s): 5 Marks (10%)
Assignment(s): 5 Marks (10%)
Seminar(s): 5 Marks (10%)
Test(s): 30 Marks (60%)
Overall 5 Marks (10%)
Performance:
Total Marks: 50 Marks
11 QUESTION BANK
1.What is test case? what are the information it contains?
2.Differentiate verification and validation.
3.List the defect classes.
4. Name the different levels in Testing Maturity Model. Also mention the key activity in each of
the levels
5.what is meant by validation and verification?
6.define software process.
7.name the TMM Levels.
8.give an example for design defect and testing defect.
9.list the defect classes. Give an example for each of the class.
10.name the different levels in testing maturity model. Also mention the key activity in each of the
levels.
11.define the term defect.
12.write the role of process in software quality.
13.list the categories that defects fall into.
14.write the major components in a software development process.
15.write the verification activities of design phase of the software development.
16.list any 2 classification of defect.
17.distinguish between fault and failure.
18.differentiate the process of testing and debugging.
19.what is the basic objective of software testing? what is its scope?
20. Write down the limitations of random testing.
21. What is a Test case?
23.what is black box approach.
24. What is a control flow graph.
25.Write the two basic testing strategies used to design test cases.
26..State the need for code functional testing in test case design.
27.List out the people who are associated with testing
28.Give the role of process in software quality.
29.define boundary value analysis.
30.how to compute cyclomatic complexity?
31.what is meant by desk checking?
32.define code complexity testing. how it can happen?
33.identify the equivalence classes in testing the program for quadratic equation solution.
34.how is mutation testing helpful in testing the software?
35.what is random testing?
36.enumerate the black box testing methods. Also write one merit for each.
37.what is the smarter tester?
38.what is post implementation testing?
39.which testing strategy is best to uncover the defect? why?
40.what are the objectives of requirement testing?
41.Explain the concepts of equivalence class partitioning and boundary value analysis.
42. Explain the various additional white box test design approaches.
43.Explain the concept of Equivalence class partitioning and boundary value analysis with
example
44. Develop black-box test cases using equivalence class partitioning and boundary value
analysis to test a module for ATM system.
45.a. In what way black box testing and COTS can be compared? b. When to start testing process
and why? discuss
46.Explain in detail about additional white box test design approaches
47.a,Explain in detail about code coverage testing. b. Explain with neat flow chart code
complexity testing.
48. With suitable test cases explain the various white box approaches .state the cyclomatic
complexity measure used in it.
49.With suitable examples explain in detail the following test approaches. a. Boundary value
analysis b. Equivalence class partitioning
50. What is test strategy? Explain the methods for developing test strategy.
51..Explain the components of test plan.
52. a. write any four IEEE recommended test related documents in detail. b. Write the various
technical skills needed by a test specialist
53. Why is testing plan important for developing a repeatable and managed testing process. Give
example.
54. What role do user/client play in the development of test plan for a project? Should they be
present at any of the test plan reviews. Justify your answer.
55. What are the roles of three groups in test planning and policy developments? Discuss in
Detail
56.a. List out the responsibilities of test specialist with their skills. b. How to build a testing
group? explain.
57. a. Discuss testing team structure for single product companies. b. What are the skills needed
for a test specialist.
58 .a. Explain with example test people management. b. How will you build a testing group?
Explain with example.
59.With suitable examples, explain the preparation of test plan components.
60. a. Write notes on testing and debugging goals and policies. b. Write notes on the role of the
groups in test planning and policy development.
61. Differentiate between project monitoring and project controlling.
62. What is software configuration management?
63. What should be included in milestone report for testing?
64. Define test measurement process
65. Distinguish between milestone and deliverable.
66. What are the criteria for test completion?
67. What is meant by test case execution productivity?
68. Define SCM.
69. Differentiate inspections from walkthrough.
70. Differentiate the terms: error, fault and failure.
71. Define the review metrics.
72. Give the various roles in a testing group.
73. What is the purpose of critical design review?
74. Define tracing.
75. Name any two test metrics.
76. Define test measurement process.
77. List any 4 benefits of a review program.
78. What are the components of a review plans.
79. Define test automation.
80. What is the purpose of test specific status meeting?
81. a. Explain the five stop-test criteria that are based on quantitative approach. b. Narrate
about the metrics or parameters to be considered for evaluating the software quality.
82. What is the role of the tester in supporting, monitoring and controlling of testing?
83. What are the types of reviews? When do the process of review starts? Discuss about review
reports.
84. a. Explain about the components of review plans. b. In what way review helps to control
project.
85. a .Explain the design and architecture for automation. List and discuss metrics that can be used
for defect prevention and how.
86. a. List the requirements of test tool. Explain with 5 suitable examples.
b. Explain the components of review plan.
87. Discuss the significance of various measurements in the testing process.
88 Explain in detail about various components of review plan.
89. Explain in detail about the measurements for monitoring
90. Explain analysis and test reports in detail.
