Sofie Pesing couse Coe: 22518, Program Name: Computer Engineering Program Group Program Code : CO/CM/ICW Semester : Fifth Course Title : Software Testing Course Code 222518 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 COMPETENCY The aim of this course is to help the student to attain the following industry identified competency through various teaching learning experiences: + Apply types, levels and methods of software testing on applications. 3. COURSE OUTCOMES (COs) ‘The theory, practical experiences and relevant soft skills associated with this course are to be taught and implemented, so that the student demonstrates the following industry oriented COs associated with the above mentioned competency: Apply various software testing methods. Prepare test cases for different types and levels of testing, Prepare test plan for an application, Identify bugs to create defect report of given application. ‘Test software for performance measures using automated testing tools. pees 4. TEACHING AND EXAMINATION SCHEME = Examination Scheme Credit ‘Theory Practical, wir fe eee ESE PA. Toial__|__FSE___[__PA Tor tir [ion [in [wax tin | Max [stn] Max | in | atx | ain | Max | Min 3 5 | 3 | 7 [28 [30 | o0 | 100 | 40 | 2s@ | 10 | 25 | 10 | so | 20 (*): Under the theory PA; Out of 30 marks, 10 marks of theory PA are for micro-project assessment to facilitate integration of COs and the remaining 20 marks is the average of 2 tests to be taken during the semester for the assessment of the UOs required for the attainment of the COs. Legends: L-Lecture; T ~ Tutorial/Teacher Guided Theory Practice; P- Practical; C-- Credit, ESE - End Semester Examination; PA - Progressive Assessment. 5. COURSE MAP (with sample COs, PrOs, UOs, ADOs and topics) This course map illustrates an overview of the flow and linkages of the topics at vario) of outcomes (details in subsequent sections) to be attained by the student by th course, in all domains of learning in terms of the industry/employer identifie depicted at the centre of this map. MSBTE — Final Copy Dt. 29.03.2019 Page 1 of 7Software 1 Course Cade: 22518 oo ep sobmatanag Bieelnie 710 Basti, ] Gea wont 8 i i pe Ee + i Vi i ee fob Nee Gawe) } exit 1 pee torch iam“ | . Ge NEE ee SSE. Sim a: rr ‘DROP TRUNCATE, DESC exe Le hempmneas ) gM AF ae . —- ne Cae wie) Figure 1 - Course Map 6. SUGGESTED PRACTICALS/ EXERCIS| The practicals in this section are PrOs (i.e. sub-components of the COs) to be developed and assessed in the student for the attainment of the competency. Practical Outcomes (PrOs) Identify system specification & design test cases for purchase order Management. _ Identify system specification & design test cases for Inventory management qT 2 3__| Design test cases for simple calculator application.(BB Testing) ~4 | Design test cases for railway reservation form 5 6 7 Design test cases for e-commerce (Flipkart, Amazon) login form Design test eases for Web Pages Testing any Web § Write program and design test cases for the following Control and E— Final Copy Dt. 29.03.2019 Page 2 of 7Software Testing Course Code 22518 Unit | APPFOX- Practical Outcomes (PrOs) N Hrs. 0. . Required decision making statement. ] 1) For... Loop 2) Switch...case_3) Do... While 4) If..else | Prepare test plan for an identified Mobile application. ml | 02 Design test plan and test cases for Notepad (MS Window based) Mm 02 Application. Prepare defect report after executing test cases for library WV 02 management system Prepare defect report after executing test cases for Withdrawn of W 02 amount from A'TM Machine. Prepare defect report after executing test cases for any login form. wv 02 Design and run test cases for WordPad (MS Windows based). Using | V 02 | an Automated tool Design and run test eases for MS Word application using an Vv 2 Automation Tool. _ Project Assignment 04 Total 32 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. A judicial mix of minimum 12 or more practical need to be performed, out of which, the practicals marked as **’ are compulsory, so that the student reaches the ‘Precision Level’ of Dave’s ‘Psychomotor Domain Taxonomy’ as generally required by the industry. ji. The ‘Process’ and ‘Product’ related skills associated with each PrO is to be assessed according 10 a suggested sample given below: Performance Indi Weightage in % 1 Preparation of system sps 50 MS Excel. | | 2 _| Preparation of defect report 10 3 Execution of test cases using automation tool. 20 4 Answer to sample questions } 10 5 Submit report in time io | Total 100 The above P1Os 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. Work as a leader/a team member. d. Follow ethical practices. 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 ing below: * ‘Valuing Level’ in I year MSBTE ~ Final Copy Dt. 29.03.2019 Page 3 of 7Sofware Testing Course Coe: 22518 * ‘Organising Level’ in 2™ year and © ‘Characterising Level’ in 3" year. 7, MAJOR EQUIPMENT/ INSTRUMENTS REQUIRED The major equipment with broad specification mentioned here will usher in uniformity in conduct of experiments, as well as aid to procure equipment by authorities concerned. Ne Equipment Name with Broad Specifications rr 1.1 | Computer system (Any computer system with basic configuration) All 1.2 [Selenium v [13 | Mantis Bug Tracker Vv [1.4 [IBM Rational Functional Tester Vv 15 | Spreadsheet Package — - (LHL 1.6 | Bugzila - a 8. UNDERPINNING THEORY COMPONENTS The following topics arc to be taught and assessed in order to develop the sample UOs given below for achieving the COs to attain the ider Unit Unit Outcomes (UOs) Topics and Sub-topics _ | {in cognitive domain) Unit—1 Ja. Identify errors and bugs in the 1.1 Software Testing, Objectives of Testing. Basics of given program. 1.2 Failure, Error, Fault, Defect, Bug, Software | 1b.Prepare test case for the given Terminology. ‘Testing application. 1.3 Test Case, When to Start and Stop and 1e, Describe the Fntry and Fxit Testing of Software (Entry and E: ‘Testing Criteria for the given test Criteria). | Methods application. 1.4 Verification and Validation (V Model), 1d, Validate the given application Quality Assurance, Quality Control. using V model in relation with 1.5 Methods of Testing: Static and dynamic quality assurance. Testing Je. Describe features of the given 1.6 The box approach: White Box Testing: testing method. Inspections, Walkthroughs, Technical Reviews, Functional Testing, Code Coverage Testing,Code Complexity Testing. 1.7 Black Box Testing: Requirement Based ‘Testing, Boundary Value Analysis, Equivalence Partitioning, | jed testing level for | Init-1 | 2a Apply spe 2.1 Levels of testing ‘ypes and | the given web based application. | 2.1 Unit Testing: Driver, Stub Levels of | 2b Apply Acceptance testing for | 2.2 Integration Testing: Top-Down Testing given web based application Integration, Bottom-Up Integration, | 2c Apply the given performance Bi-Directional Integration, | testing for the specitied 2.3. Testing on Web Application: application. Performance Testing:l.o4 2d. Generate test cases for the given Stress ‘Testing, Sec} application using regression and Client-Server Te: GUI testing 24 Acceptance Test 4 | MSBTE — Final Copy Dt. 29.03.2019 Page 4 of 7Sontware Testing Unit Unit Outcomes (UOs) (in cognitive domain) Course Cae: 22518 ‘Topies and Sub-topies Defect ent Testin, Tools and Measurem ents Managem ent Unit-1V iV Managem ig 3a, Prepare test plan for the given application. 3b. Identify the resource requirement of the given application, Prepare test cases for the given application. Prepare test report of executed test cases for given application. 3c. 3d. 4a. estimated impact. Prepare defect template on the given application. Apply defect management process on the given application. Write procedure to find defect using the given technique. 4b. 4e. 4d. 5a, Improve testing efficiency using automated tool for given application. Identify different testing tools to test the given application. Describe Metries and Measurement for the given application . Explain Object oriented metrics used in the given testing application Sb. Se, Sd. Classify defects on the basis 31 32 33 34 41 42. 43 [5.1 Manual Te 52 53 5a 55 Beta Testing, Special Tests: Regression Testing, GUI Testing, Tes Planning : Preparing a Test Plan, Deciding Test Approach, Setting Up Criteria for Testing, Identifying Responsibilities, Staffing, Resource Requirements, Test Deliverables, Testing Tasks ‘Test Management: Test Infrastructure Management, Test People Management Test Process: Base Lining a Test Plan, Test Case Specification. ‘Test Reporting: Executing Test Cases, Preparing Test Summary Report. Defect Classification, Defect Management Process. Defect Life Cycle, Defect Template Estimate Expected Impact of a Defect, Techniques for Finding Defects, Reporting a Defect. sting and Need for ‘Automated Testing Tools Advantages and Disadvantages of Using Tools Selecting a Testing Tool When to Use Automated Test Tools, Testing Using Automated Tools. Metrics and Measurement: Types of Metrics, Produet Metrics and Process Metrics, Object oriented metries in testing Note: To attain the COs and competency, above listed UOs need to be undertaken to achieve the ‘Application Level’ of Bloom’s ‘Cognitive Domain Taxonomy’: 9, SUGGESTED SPECIFICATION TABLE FOR QUESTION PAPER DESIGN Unit Unit Title ‘Teaching | Distribution of Theory Marks _| No. Hours: R U Total ft Level_| Level | Level | Marks T_ | Basies of Software Testing and i4 os | 04 Testing Method _ IL_| Types and Levels of Testing Lie | 04 06 MSBTE ~ Final Copy Dt. 29.03.2019 Page 5 of 7Conse Code: 22518 | Unit | Unit Title [Teaching |_ Distribution of Theory Marks No. Hours R U A Total Level_| Level | Level | Marks I1_| Test Management | 2 04 04 06 14 IV_| Defect Management 10 02 o2_| 06 | 10 | v Testing Tools and Measurements 12 04 04 06 14 total 64 18 20 32 70 Legends: R=Remember, U=Understand, A~Apply 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 STUDENT ACTIVITI 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: Students should conduct following activities in group and prepare reports of about 5 pages for each also collect/record physical evidences for their (student's) portfolio which will be useful for their placement interviews a) Prepare journals based on practical performed in laboratory. b) Give seminar on relevant topic. ©) Undertake micro-projects. 11. | SUGGESTED SPECIAL INSTRUCTIONAL STRATEGIES (if any) ‘These are sample strategies, which the teacher can use to accelerate the attainment of the various learning outcomes in this course: a) Massive open online courses (MOOCs) may be used to teach va us topies/sub ” in item No. 4 does not mean only the traditional lecture method, but different types of teaching methods and media that are to be employed to develop the outcomes. ©) About 15-20% of the topics/sub-topics which is relatively simpler or descriptive in nature is to be given to the students for self-directed learning and assess the development of the COs through classroom presentations (see implementation guideline for details). d) With respect to item No.10, teachers need to ensure to create opportunities provisions for co-curricular activities. ©) Guide student(s) in undertaking miero-proj. £) Demonstrate students thoroughly before they start doing the practice. g) Encourage students to refer different websites to have deeper understanding of the subject, h) Observe continuously and monitor the performance of students in Lab and 12. 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 the first four semesters, the micro-project are group-based. However, in the fifth and sixth semesters, it should be preferably be individually undertaken to build up the skill and confidence in every student to become problem solver so that s/he contributes to the projects of the industry. In special situations where gr lave to be formed for micro-projects, the number of students in the group should not gust MSBTE — Final Copy Dt. 29.03.2019 Page 6 of 7Software Tasting Course Code: 22518 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 PrOs, 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 are given here. Similar micro-projects could be added by the concemed faculty: a) Library Management: book issue /book stock system. b) Any other micro-projects suggested by subject faculty on similar line. 13, SUGGESTED LEARNING RESOURCES : No. Title of Book Publication 1_ | Software Testing: PEARSON Publisher: Pearson India Principles and Practices _| Gopalaswamy Ramesh _ | 2005, ISBN: 9788177581218, Software Testing: Tata McGraw Hill Education, New 2 | Principles, Techniques | Limaye M. G. Delhi., 2007 ISBN and Tools 13: 9780070139909 3 | Soflware Testing: Oxford University Press Noida — Principles and Practices _| “hsuhan Naresh ‘Cambridge University Press, B: || Software Testing Singh Yogesh Bangluru. ISBN 978-1-107-65278-1 Devraj Publications, Mumbai ISBN 978-81-933551-6-9 5. | Software Testing Dr. Rajendra Kawale ‘Note: Other available testing tools can be used at institute level. 14. SOFTWARE/LEARNING WEBSITES http://www.selenium.com hutp://en.wikipedia.org/wiki/Test_automation hutp://en.wikipedia.org/wiki/Software_testing#Testing tools http://www. softwaretestingsoftware.com www.toolsqa.com peers MSBTE ~ Final Copy Dt. 29.03.2019 Page 7 of 7