ISO-IEEE29119overviewshort-Hagar

中国软件测试认证委员会ChineseSoftwareTestingQualificationsBoard2Copyright2014JonHagarGrandSoftwareTestingGSTIntroducingtheNewSoftwareTestingStandard:ISO/IEEE/[e-mail](GST),LLC303-903-55363©2014CSTQBFamiliarizeattendeeswithISO29119BeabletodefinebasetestingconceptsandtermsExplainandstartapplyingISO29119process(es)OutlinetheconceptsofeachPartofISO29119RecognizetherearemanytesttechniquesAssistintailoringofthestandardtoalocalcontextUnderstandthebasicsofTestapproachesObjectivesRisk-basedtestingOthertestbases4©2014CSTQB–Standardsareafactoflifeformanyindustryprofessionals--notjusttesters–Standardsformpartofthebusinessformanycompanies,customers,andcountries–Manyofusendupinamixedrelationshipwithstandards–Standardscanbeabasisforresearchandchange–IndustryhasnothadacomprehensivesoftwaretestingstandarduntilISO291195©2014CSTQB–Guidelinedocuments—notcompulsoryunlessmandated–Agreementsbecausetheyoftenreflectacertainlevelofconsensuswithinacommunity“Guidelinedocumentationthatreflectsagreementsonproducts,practices,oroperationsbynationallyorinternationallyrecognizedindustrial,professional,tradeassociationsorgovernmentalbodies”-ISO6©2014CSTQB“help?”•Standardsareabasisfor:–Communication–commonterminology–Professionalismandcriticism–Conformance/complianceschemes–Benchmarkof‘industrypractice’(notbest,maynotbegoodforall,etc.)–Contractsandregulations–Interoperabilityandconsistency...Standardsdescribeacurrent‘bodyofknowledge’thatprovidesthebasisforaprofessionaldiscipline7©2014CSTQB•Anysoftwarestandardisbasedonlimitedhistoryanddevelopedbasedonconsensusofmanyvoices–Yetstillmayrepresentonlysomeofviewpointsofindustry–Butdoesnotrepresentallstatesoftheart•Standardsneedtobeinclusiveandethical–StandarddoesNOTrepresent“best”–Notclaimedtobeperfect–Mostprojectsandprofessionalswilluse“tailoring”(forcontext)8©2014CSTQB©2014CSTQB•Conflictsindefinitions,processesandprocedures–“Oneringtorulethemall”—standardstobereplacedbyone•e.g.,IEEE829,IEEE1008,BS7925-1/-2,IEEE1028–Usersdonotknowwhichstandardtofollow•Lackingincurrentstandardsorincomplete:–Organizationalareas•e.g.,TestPolicyandOrganizationalTestStrategy–ProjectTestManagement–BS7925onlycoversunittesting–Generalprocesses–Commonfunctionaltechniquesmissing–Coverageofnon-functionaltesting10©2014CSTQB–StructureandFlowBS7925-1BS7925-2IEEE829Concepts&VocabularyPart1ProcessAssessmentTestingTechniquesPart4DocumentationPart3Part2ProcessesKeyword-DrivenTestingPart5ISO/IEC33063ISO12207ISO15288DirectivesIEEE100811©2014CSTQB•Standardssupportcommoncommunicationwithinthetopic–Commonreferencepoints–Startingpointforresearch,usage(proandcon),critics•Maturityisanissuebutabaselineservesasasoundingboardandcommonreferencepointfor“Scientific”methods–Aninternationalbenchmark–Thinkersandresearcherscanprove/disprovebenchmark(s)•Partofbeinginaprofession(butonlypart)•Standardshavedangers12©2014CSTQB–PotentialDangers•Noteverybook,school,paper,idealwillberepresented•Theremustbeavetting,upgrade,andmaintenanceeffort•Willnotmakeeveryonehappy,soinmanycasesISO29119mustbetailoredbyanyoneusingthem•Willbesubjectto“misuse”byvariousgroups–Unthinkingaudits/reviews–Maystopsomepeoplefromthinkingforthemselves–Claimsofcomplianceformarketingandnotimprovement•Will(always)beimperfect,butrepresentsastartingpointforcritics13©2014CSTQB–Metrics,Examples,BibliographyDEFINITIONSTest:Approach,Basis,Methods-RiskBasedTesting14©2014CSTQBThe“primarygoalsoftesting:provideinformationaboutthequalityofthetestitemandanyresidualriskinrelationtohowmuchthetestitemhasbeentested;tofinddefectsinthetestitempriortoitsreleaseforuse;andtomitigatetheriskstothestakeholdersofpoorproductquality”toimprovethetestitembyhavingthedefectsremoved(butyoucan’t“testqualitiesin”)toimprovestakeholderdecisionsbyprovidinginformationonqualitiesbutcanweshipwithbugs?toimprovetheprocessesintheorganization15©2014CSTQB•Scope-Part1coversdefinitionsandfundamentalkeyconceptstestteamsshouldunderstand–Setsstageforallotherparts•TermsandDefinitions•ProvidesaBasicframeworkandsetofconcepts16©2014CSTQB–“Whycan’twetestcompletely?”Amanagement/customerfrustration:“Wedidallofthesetestsstillmissthebugs”WHY?Complexity–exampleofhowmanytestsneededtotesteverythingSize–Smartphone10-20millionlinesofcodeSoftwareisarguablyoneofthemostcomplexproductshumanscreateThereforetestingbecomessamplingMethods,types,approaches,techniques,toolsallhelpinsampling,