ioioolooooooollllllllllllllllllllllllllllllllllllllllll

klklklklklklkl

1. UNIT-I
Introduction to Software Testing
Class: B.E.
Ms. Pooja Tambe
DepartmentofComputerEngg.,DYPCOE,Pune

2. 410245 (D): Software Testing and Quality Assurance
Teaching Scheme:
TH:03 Hours/Week
Credit:03
Examination Scheme:
•In-Sem(Paper):30 Marks
•End-Sem(Paper):70 Marks
Prerequisite Courses:
•Software Engineering (210253)
•Software Project Management (310245(D))
Companion Course:Lab Practice IV

3. Course Objectives:
1.Introducebasicconceptsofsoftwaretesting.
2.Understandthebestwaytoincreasetheeffectiveness,testcoverage,and
executionspeedinsoftwaretesting.
3.Understandwhitebox,blockbox,objectoriented,webbasedandcloud
testing.
4.Understandtheimportanceofsoftwarequalityandassurancesoftware
systemsdevelopment.
5.Knowindetailsautomationtestingandtoolsusedforautomationtesting.
6.Tolearnandunderstandthecombinationofpracticesandtoolsthatare
designedtohelpQAprofessionalstestmoreefficiently.

4. Course Outcomes:
Oncompletionofthecourse,studentwillbeableto–
CO1:Describefundamentalconceptsinsoftwaretestingsuchasmanual
testing,automationtestingandsoftwarequalityassurance.
CO2:DesignandDevelopprojecttestplan,designtestcases,testdata,and
conducttestoperations.
CO3:Applyrecentautomationtoolforvarioussoftwaretestingfortesting
software.
CO4:Applydifferentapproachesofqualitymanagement,assurance,and
qualitystandardtosoftwaresystem.
CO5:ApplyandanalyzeeffectivenessSoftwareQualityTools.
CO6:Applytoolsnecessaryforefficienttestingframework.

5. UnitI:IntroductiontoSoftwareTesting(07Hours)
UnitII:TestPlanningandQualityManagement(07Hours)
UnitIII:TestCaseDesignTechniques(07Hours)
UnitIV:SoftwareQualityAssuranceandQualityControl(07Hours)
UnitV:AutomationTestingTools/PerformanceTestingTools
(07Hours)
UnitVI:TestingFramework(07Hours)

7. Historical Perspective:
•Theconceptofqualityinsoftwaredevelopmenthasevolvedfrom
traditionalmanufacturingpractices.Initially,qualityassurancewas
focusedsolelyonproducttesting.Overtime,methodologieslikeTotal
QualityManagement(TQM)andStatisticalProcessControl(SPC)
wereadaptedtosoftwareengineeringtoensurequalityacrossall
stagesofdevelopment.

8. Software Testing:
•SoftwaretestingisanimportantprocessintheSoftware
Development Lifecycle(SDLC). It
involvesverifyingandvalidatingthataSoftwareApplicationisfree
ofbugs,meetsthetechnicalrequirementssetby
itsDesignandDevelopment,andsatisfiesuserrequirements
efficientlyandeffectively.
•SoftwareTestingisaprocessofverifyingandvalidatingwhether
theSoftwareProductorApplicationisworkingasexpectedornot.
Thecompletetestingincludesidentifyingerrorsandbugsthatcause
futureproblemsfortheperformanceofanapplication.

9. SoftwareTestingCanbeDividedintoTwoSteps:
•Softwaretestingmainlydividesintothetwoparts,whichisusedin
theSoftwareDevelopmentProcess:
1.Verification:Thisstepinvolvescheckingifthesoftwareisdoing
whatissupposedtodo.Itslikeasking,"Arewebuildingthe
producttherightway?“
2.Validation:Thisstepverifiesthatthesoftwareactuallymeetsthe
customer'sneedsandrequirements.Itslikeasking,"Arewebuilding
therightproduct?"

10. Software Testing Types

11. Types of Testing:
1.ManualTesting
ManualTestingisatechniquetotestthesoftwarethatiscarriedout
usingthefunctionsandfeaturesofanapplication.Whichmeansmanual
testingwillcheckthedefectmanuallywithtryingonebyonefunctionis
workingasexpected.
2.AutomationTesting
AutomationTestingItisatechniquewheretheTesterwritesscripts
independentlyandusessuitableSoftwareorAutomationToolstotest
thesoftware.ItisanAutomationProcessofaManualProcess.Itallows
forexecutingrepetitivetaskswithouttheuseofaManualTester.

12. TypesofManualTesting:
Manualtestingwillbedividedintofurthertypeswhichisfollowing:
1.WhiteBoxTesting
WhiteBoxTestingisasoftwaretestingtechniquethatinvolvestesting
theinternalstructureandworkingsofasoftwareapplication.Thetester
hasaccesstothesourcecodeandusesthisknowledgetodesigntest
casesthatcanverifythecorrectnessofthesoftwareatthecodelevel.
2.BlackBoxTesting
Black-BoxTestingisatypeofsoftwaretestinginwhichthetesterisnot
concernedwiththeinternalknowledgeorimplementationdetailsofthe
softwarebutratherfocusesonvalidatingthefunctionalitybasedonthe
providedspecificationsorrequirements.

13. •SoftwareQualityManagement(SQM)isasystematicapproachthat
ensuressoftwareproductsmeetpredefinedqualitystandardsand
customerexpectations.Itinvolvesallactivitiesrelatedtotheprocess
ofensuringsoftwarequality—planning,assurance,control,and
improvement.
CoreComponents:
•QualityPlanning–settingqualitygoalsandselectingappropriate
processes.
•QualityAssurance–systematicactivitiestoensurequality
requirementsarebeingmet.
•QualityControl–techniquesandactivitiesformonitoringoutputs.
•QualityImprovement–ongoingeffortstoenhanceprocessesand
outcomes.

14. •Customers,Suppliers,andProcess:
Insoftwaredevelopment,customersareend-usersorclients;suppliers
aredevelopersandvendors;andtheprocessincludesallactivitiesfrom
requirementgatheringtomaintenance.Eachhasaroleininfluencingthe
finalqualityoftheproduct.

15. Testing and Quality Concepts
Objectives of Testing:
•Detect defects
•Ensure product meets requirements
•Validate performance and usability
•Improve product reliability
Testing vs. Debugging:
•Testingfinds the presence of defects.
•Debugginginvolves diagnosing and fixing those defects.
•Need for Testing:
Testing is crucial because software errors can lead to system failures, data loss, and financial or
reputational damage.

16. Quality Assurance and Testing:
Quality assurance is process-focused, aiming to prevent defects, while
testing is product-focused, aiming to find defects.
Why Software Has Errors:
•Human mistakes in coding and design
•Incomplete or unclear requirements
•Complex system interactions
•Time and budget pressures
Defects and Failures:
•Defects: flaws in code/design
•Failures: incorrect software behavior caused by defects

17. Quality Frameworks and Methodologies
•Total Quality Management (TQM):
TQM is a customer-focused approach where all members of an
organization participate in improving processes, products, and culture.
•Quality Practices in TQM:
•Customer focus
•Employee involvement
•Continuous improvement (Kaizen)
•Fact-based decision making

18. Quality Management Through:
•Statistical Process Control (SPC):Uses data to monitor processes
•Cultural Changes:Promotes a quality-first mindset
•Continual Improvement Cycle (PDCA):Plan → Do → Check → Act
•Benchmarking:Comparing practices with industry leaders
•Metrics:Quantitative data to track performance
Problem Solving Techniques and Tools:
•Root Cause Analysis
•Fishbone Diagrams
•Pareto Charts
•Check Sheets
•Control Charts

19. Software Quality and Process Models
Software Quality Constraints:
•Budget limitations
•Time constraints
•Technological limitations
•Regulatory requirements
Quality and Productivity Relationship:
Higher quality often leads to better productivity through reduced rework and maintenance.
Requirements of Product:
Functional and non-functional requirements must be clearly defined and verified for quality.
Software Development Process:
Consists of requirement analysis, design, implementation, testing, deployment, and maintenance.
Types of Products:
•System software
•Application software
•Embedded software
•Web-based software

20. Software Development Lifecycle Models:
•Waterfall Model
•V-Model
•Incremental Model
•Agile Model
•Spiral Model

21. Quality Management System (QMS)
Software Quality Management Processes:
•Project quality management
•Process quality management
•Product quality assurance
Structure of a QMS:
•Defined policies
•Standard procedures
•Roles and responsibilities
•Documentation and reporting systems

22. Pillars of Quality Management System:
•Customer Focus
•Leadership
•Engagement of People
•Process Approach
•Continuous Improvement
•Evidence-based Decision Making
•Relationship Management
•Important Aspects of Quality Management:
•Meeting customer expectations
•Compliance with standards (ISO, CMMI)
•Risk management
•Efficient process control