Certified Tester International Foundation Level Syllabus 1.1 Why is Testing Necessary(K2) 20 minutes Terms Bug,defect,error,failure.fault,mistake.quality,risk 1.1.1 Software Systems Context(K1) expect e that do money.tim 1.1.2 Causes of Software Defects(K2) Ahuman beingcan make an(mistake).which produces a defect (fault,bug)in Defects occur beca ause there is time pre Failures can be caused by environmental c ence 1.1.3 Role of Testing in Software Development,Maintenance and Operations(K2) ation comrected pefore the system is released for operationl use Software testing may also be required to meet contractual or legal requirements,or industry-specific standards. 1.1.4 Testing and Quality(K2) Software Product Quality(IO9126). Testing can give confidence in the quality of the software if it finds few or no defects.A properly cnqnc,improve the oreym Page 11 of78 31-Mar-2011
Certif Founda Version 2 © Internationa 1.1 Terms Bug, def 1.1.1 Software products expected money, t 1.1.2 A human code, or (or do so result in Defects code, co Failures electroni changing 1.1.3 Operat Rigorous during o corrected Software standard 1.1.4 With the for both f usability see Cha Software Testing c designed defects, Lessons found in reoccurr quality a Testing s standard fied Teste ation Level Sy 2011 al Software Testing Q Why is fect, error, fa Software e systems ar s (e.g., cars). d. Software t time or busin Causes o n being can m in a docume omething it s failures, but occur becau omplexity of i can be caus ic fields, and g the hardwa Role of T tions (K2) s testing of s peration and d before the e testing may ds. Testing a help of testi functional an , efficiency, m apter 2; for m e Product Qu can give con d test that pa the quality o s should be le other projec ing and, as a ssurance. should be int ds, training a er yllabus Qualifications Board Testing ailure, fault, m e Systems re an integral . Most people that does not ness reputati of Softwar make an erro ent. If a defec houldn’t), ca not all defec se human be nfrastructure sed by enviro pollution ca are condition Testing in systems and d contribute to system is re y also be req and Qualit ng, it is poss nd non-functi maintainabili ore informat uality’ (ISO 9 nfidence in th asses reduce of the softwar earned from cts, processe a consequen tegrated as o nd defect an g Necess mistake, qual s Context ( l part of life, f e have had a t work correc on, and coul re Defects or (mistake), ct in code is ausing a failu cts do so. eings are fal e, changing t onmental con n cause faul s. Software documentati o the quality eleased for o quired to mee ty (K2) sible to meas ional softwar ty and portab tion on softw 126). he quality of t es the overal re system inc previous pro es can be imp nce, improve one of the qu nalysis). Page 11 of sary (K2 lity, risk (K1) from busines an experienc ctly can lead ld even caus s (K2) which produ executed, th re. Defects i lible and bec technologies nditions as w ts in firmwar Developm ion can help of the softw perational us et contractua sure the qual re requireme bility). For m are characte the software l level of risk creases whe ojects. By un proved, whic the quality o uality assura 78 2) ss applicatio ce with softwa to many pro se injury or de uces a defec he system ma n software, s cause there i , and/or man well. For exa re or influenc ment, Main to reduce th are system, se. al or legal req lity of softwa ents and char ore informat eristics see ‘S if it finds few k in a system en those defe derstanding ch in turn sho of future syst nce activities Q ns (e.g., ban are that did n oblems, inclu eath. t (fault, bug) ay fail to do w systems or d s time press ny system int mple, radiati ce the execut ntenance a he risk of pro if the defects quirements, o re in terms o racteristics (e ion on non-fu Software Eng w or no defec m. When testi ects are fixed the root cau ould prevent tems. This is s (i.e., alongs Internatio Software Te Qualifications 31-Ma 20 minut nking) to cons not work as ding loss of in the progra what it shoul documents m sure, complex teractions. ion, magnetis tion of softwa and blems occur s found are or industry-s of defects fou e.g., reliabilit unctional tes gineering – cts. A proper ng does find d. ses of defec those defect an aspect o side develop nal esting s Board ar-2011 tes sumer am ld do may x sm, are by ring pecific und, ty, sting rly d cts ts from of pment
Certified Tester International Foundation Level Syllabus 1.1.5 How Much Testing is Enough?(K2) Deciding how much testing is enough should take account of the level of risk,including technical. er,DChapieegsistks,andproectonstantssuchasimeandbudgetRisksdscused customers. Page 12 of78 31-Mar-2011
Certif Founda Version 2 © Internationa 1.1.5 Deciding safety, a further in Testing s release o custome fied Teste ation Level Sy 2011 al Software Testing Q How Muc g how much t and business n Chapter 5. should provid of the softwa ers. er yllabus Qualifications Board ch Testing testing is eno s risks, and p de sufficient are or system g is Enoug ough should project constr information t m being teste Page 12 of gh? (K2) take accoun raints such a to stakehold ed, for the ne 78 nt of the leve as time and b ers to make xt developm Q el of risk, inclu budget. Risk informed de ent step or h Internatio Software Te Qualifications 31-Ma uding technic k is discussed cisions abou handover to nal esting s Board ar-2011 cal, d ut the
Certified Tester International Foundation Level Syllabus 1.2 What is Testing?(K2) 30 minutes Terms Debugging.requirement.review,test case.testing.test objective Background A co otion of testing is that it only consists of running tests,i.e.executing the software. This is part of testing.but not all of the testing activities. TestactvtesexistbeoreandaertestexeeutiomnTmesenctnienctuneplanmwgandncortrol porting on the test cess and s nunder test.and finalizing or ) ing also includes reviewing documents development and testing processes. Testing can have the following objectives: onfidence about the level of quality Prevenm9gnieectonordecsion-makng Ctciheetpreaendacthiestnoednde signing tests early in the life cycle(verifying the s)and the identification and resolution of issues to prevent many failures as possible so that def fects in the softy re are gain confiden e that it has t the s In so ne cases then ain ohi ive of testin to ass ess t quality of the(with defec)to ges.Dur bilityo The process of testing and the testing activities are explained in Section 1.4 Page 13 of78 31-Mar-2011
Certif Founda Version 2 © Internationa 1.2 Terms Debuggi Backgr A comm This is p Test acti choosing criteria, r activities (includin Both dyn and will developm Testing c o Find o Gain o Prov o Prev The thou test basi documen defects a Different testing (e many fai acceptan gain con be to ass stakehol testing th operatio availabil Debuggi Debuggi Subsequ responsi The proc fied Teste ation Level Sy 2011 al Software Testing Q What is ng, requirem round on perceptio part of testing ivities exist b g test conditi reporting on s after a test g source cod namic testing provide infor ment and tes can have the ing defects ning confiden viding inform venting defec ught process s via test de nts (e.g., req appearing in t viewpoints e.g., compon ilures as pos nce testing, t nfidence that sess the qua ders of the r hat no new d nal testing, t ity. ng and testin ng is the dev uent re-testin ibility for thes cess of testin er yllabus Qualifications Board s Testin ment, review, on of testing i g, but not all o before and af ons, designi the testing p phase has b de) and cond g and static te rmation that c sting process e following ob nce about the ation for dec cts s and activitie sign) can he quirements) a the code. in testing tak nent, integrat ssible so that the main obje it has met th ality of the so risk of releas defects have he main obje ng are differe velopment ac ng by a teste se activities i ng and the te g? (K2) test case, te is that it only of the testing fter test exec ng and exec process and been complet ducting static esting can b can be used ses. bjectives: e level of qua cision-making es involved in elp to prevent and the ident ke different o tion and syst t defects in th ective may b he requireme oftware (with ing the syste been introdu ective may b ent. Dynamic ctivity that fin r ensures tha is usually tes esting activitie Page 13 of esting, test o y consists of g activities. cution. Thes cuting test ca system unde ted. Testing c analysis. e used as a to improve b ality g n designing t t defects from tification and objectives into tem testing), he software a be to confirm ents. In some no intention em at a given uced during d e to assess s c testing can nds, analyze at the fix doe sters test and es are expla 78 objective running tests se activities in ses, checkin er test, and fi also includes means for ac both the syst tests early in m being intro d resolution o o account. F the main ob are identified that the sys e cases the m of fixing defe n time. Maint developmen system chara show failure s and remov es indeed res d developers ined in Secti Q s, i.e., execu nclude plann ng results, ev inalizing or c s reviewing d chieving sim tem being tes the life cycle oduced into c of issues also For example, bjective may d and can be tem works a main objectiv ects), to give tenance testi t of the chan acteristics su es that are ca ves the cause solve the fail s debug. on 1.4. Internatio Software Te Qualifications 31-Ma 30 minut uting the softw ning and cont valuating exit completing cl documents milar objective sted and the e (verifying t code. Review o help to prev in developm be to cause e fixed. In s expected, ve of testing e information ing often incl nges. During uch as reliab aused by def e of the failur ure. The nal esting s Board ar-2011 tes ware. trol, t osure es, e he ws of vent ment as to may n to ludes bility or fects. re
Certified Tester International ISTQB Foundation Level Syllabus Ications 1.3 Seven Testing Principles (K2) 35 minutes Terms Exhaustive testing leve e overe past0 yearad er gn o s are 2-Exhaustive testing efforts. development cyce and shall be g activities shall be started as early as possible in the software or system obie ct cluste ing effort shall be fo oportionally to the exp release testing.or is responsible for most of the operationl faures ing pre Principle5 icd aradox t of IbngeinanynewdeiecsTOoue me this pesticide paradox iescasesnetoeegulany hesofia1eorsysiem1o9mnapoelrmceseecaeutobewrtentoexercisedferentpais Principle 6-Testing is cont ext dependent differently from an ecommerce site. conte .For example.safety-critical sofware is tested needs and expectations. Page 14 of78 31-Mar-2011
Certif Founda Version 2 © Internationa 1.3 Terms Exhaust Princip A numbe guideline Principl Testing c reduces found, it Principl Testing e cases. In efforts. Principl To find d developm Principl Testing e modules release t Principl If the sam longer fin reviewed the softw Principl Testing i differentl Principl Finding a needs an fied Teste ation Level Sy 2011 al Software Testing Q Seven ive testing ples er of testing p es common f e 1 – Testin can show tha the probabil is not a proo e 2 – Exhau everything (a nstead of exh e 3 – Early t defects early ment life cyc e 4 – Defect effort shall be s. A small nu testing, or is e 5 – Pestic me tests are nd any new d d and revised ware or syste e 6 – Testin is done differ ly from an ee 7 – Absen and fixing de nd expectatio er yllabus Qualifications Board Testing principles ha for all testing g shows pre at defects ar ity of undisco of of correctn ustive testin all combinatio haustive test testing , testing activ le, and shall t clustering e focused pr mber of mod responsible cide paradox repeated ov defects. To o d, and new a em to find po g is context rently in diffe -commerce s nce-of-errors efects does n ons. Princip ave been sug g. esence of d e present, bu overed defec ness. g is imposs ons of inputs ting, risk ana vities shall b be focused roportionally dules usually for most of t x ver and over overcome thi and different tentially mor t dependent erent context site. s fallacy not help if the Page 14 of les (K2) ggested over defects ut cannot pro cts remaining sible s and precon alysis and pri e started as on defined o to the expec y contains mo the operation again, event is “pesticide tests need to re defects. t ts. For exam e system bui 78 ) r the past 40 ove that there g in the softw nditions) is no orities should early as pos objectives. cted and late ost of the def nal failures. tually the sam paradox”, te o be written t ple, safety-c lt is unusable Q years and o e are no defe ware but, eve ot feasible ex d be used to ssible in the s r observed d fects discove me set of tes st cases nee to exercise d ritical softwa e and does n Internatio Software Te Qualifications 31-Ma 35 minut ffer general ects. Testing en if no defec xcept for trivi o focus testin software or s defect density ered during p st cases will ed to be regu different parts are is tested not fulfill the nal esting s Board ar-2011 tes g cts are ial g system y of preno ularly s of users’
Certified Tester International Foundation Level Syllabus 1.4 Fundamental Test Process(K1) 35 minutes Terms summary report.testware ackgrou part of testing is test e xecution.But to be effective and efficient,test plans should e spent on planning the tests,designing test cases,preparing for execution heosthin acivis: 1.4.1 Test Planning and Control(K1) f definin the objectives of testing and the specification of test activities progressagainst the plan.th status,inc rom the p s ta essary to m et the autnepoeTespnmghk6smoacoathee8akionnn6agmadoid ac Test planning and control tasks are defined in Chapter 5 of this syllabus 1.4.2 Test Analysis and Design(K1) The test analysis and design activity has the following maior tasks Revi wing the test ba Is (such as requ ements.so testability of the test basis and test objects eaionsemWee'askevel.nsk Designing and prioritizing high level test cases any re Creating bi-directional traceability between test basis and test cases ee to which softw ies or mu 0eyeveer yeeioiegpegetasad Version 2011 5of78 31-Mar-2011
Certif Founda Version 2 © Internationa 1.4 Terms Confirma test cove summary Backgr The mos also inclu and eval The fund o Test o Test o Test o Eval o Test Although Tailoring 1.4.1 Test plan in order Test con status, in and obje througho activities Test plan 1.4.2 Test ana tangible The test o Revi anal o Eval o Iden beha o Desi o Iden o Desi o Crea 1 The degr system cha reliability, o fied Teste ation Level Sy 2011 al Software Testing Q Fundam ation testing, erage, test da y report, test round st visible part ude time to b luating result damental tes t planning an t analysis an t implementa uating exit c t closure acti h logically se g these main Test Plan nning is the a to meet the o ntrol is the on ncluding dev ectives of the out the projec s. nning and co Test Ana alysis and de test conditio analysis and iewing the te ysis reports, uating testab tifying and p avior and stru igning and p tifying neces igning the tes ating bi-direc ree to which sof aracteristics (e.g or cost) which a er yllabus Qualifications Board mental T , re-testing, e ata, test exe tware t of testing is be spent on p ts. st process co nd control d design ation and exe criteria and re vities equential, the activities wit nning and activity of de objectives an ngoing activit iations from e project. In o ct. Test plan ontrol tasks a alysis and esign is the a ons and test c d design acti est basis (suc architecture bility of the te prioritizing tes ucture of the rioritizing hig ssary test da st environme ctional tracea ftware complies g., software com are defined to re Test Pro exit criteria, i cution, test l s test executi planning the onsists of the ecution eporting e activities in thin the cont d Control ( efining the ob nd mission. ty of compar the plan. It in order to contr ning takes in are defined in Design (K activity during cases. ivity has the ch as require e, design, inte est basis and st conditions e software gh level test c ta to support ent setup and ability betwee s or must comply mplexity, risk as eflect the importa Page 15 of ocess (K ncident, regr og, test plan ion. But to be tests, desig following ma the process ext of the sy (K1) bjectives of te ing actual pr nvolves takin rol testing, th nto account t n Chapter 5 o K1) g which gene following ma ements, softw erface specif d test objects based on an cases t the test con d identifying en test basis y with a set of s ssessment, safe ance of the soft 78 K1) ression testin , test proced e effective an ning test cas ain activities may overlap stem and the esting and th rogress again ng actions ne he testing ac he feedback of this syllab eral testing o ajor tasks: ware integrity fications) s nalysis of tes nditions and any required and test cas stakeholder-sele ety level, securit tware to its stak Q ng, test basis dure, test pol nd efficient, t ses, preparin : p or take plac e project is u he specificatio nst the plan, ecessary to m tivities shoul k from monito bus. bjectives are y level1 (risk st items, the test cases d infrastructu ses ected software a ty level, desired keholders. Internatio Software Te Qualifications 31-Ma 35 minut s, test condit icy, test suite test plans sh ng for execut ce concurren usually requir on of test ac and reportin meet the mis ld be monitor oring and con e transformed level), risk specification ure and tools and/or softwareperformance, nal esting s Board ar-2011 tes tion, e, test hould ion ntly. red. ctivities ng the ssion red ntrol d into n, -based