4 - Acceptance Testing_physics_teacher_azerbaijan_baku_telman_askeraliyev.pptx

Physics teacher Azerbaijan, Baku, Telman Askeraliyev

#physicstutor #fizika #physicsteacher #azerbaycan #baku #physics #phy #internationalschool #ada #tutor #avropaazerbaycanmektebi #adamektebi #ibdp #ibmyp #tehsil #english #physicsinenglish #physicswallah #fyi #kazakhstan🇰🇿 #almaty #astana #fizika #tisa #fizikamüəllimi #dünya #math #bakuoxfordschool #mechanics #electronics #ia #ibia #bos #bakumodernschool #muellim #igcse #gcse #physicswallah #baki #moskva #astana #nursultan #fizika

1. PHYSICS TEACHER AZERBAIJAN

2. TEST ACCEPTANCE Instructor: M. Sci. Telman Askeraliyev ( Politecnico di Torino, Italy ) Azerbaijan – Baku – ADNSU - 2017 https://www.linkedin.com/in/physics-teacher-azerbaijan/ https://www.instagram.com/physics_teacher_azerbaijan/ [phone]

3. DEFINITION https://www.linkedin.com/in/physics-teacher-azerbaijan/ https://www.instagram.com/physics_teacher_azerbaijan/ [phone] #gcse #tutor #digitalsat #physicsteacher #azerbaijan #physics #muellim #teacher #xaricdetehsil #baghdad #iraq #kuwait #georgia #digitalsat #satmath #maths #mathteacher #ada #ibdp #igcse #satmath #english #adaschool #gcse #internationalschool #physicsteacher #azerbaijan #physics #kazakhstan #azerbaijan #physics #physicsteacher #tutor #school #science #moscow #almaty #kazakhstan #tutor #fizika #muellim #teacher #xaricdetehsil #baghdad #iraq #kuwait #georgia #digitalsat #satmath #maths #mathteacher #ada #ibdp #igcse #satmath #english #adaschool #gcse #internationalschool #physicsteacher #azerbaijan #physics #physicsteacher #azerbaijan #physics #exams #revision #bakuoxfordschool #bakumodernschool #zirveliseyi #idrakliseyi#kaspiliseyi#zengiliseyi #muasirtehsilkompleksi #avropaazerbaycanmektebi #sabisinternationalschool #physicstutor #physics #physicsteacher #fyi #almaty #astana

4. QUALITY ENGINEERING ACCEPTANCE TESTING

5. TESTING What is the overall goal of testing? What claims can we make when testing "passes" or "fails" ?

6. TESTING testing : systematic attempt to reveal the presence of errors (to "falsify" system) accomplished by exercising defects in the system and revealing problems failed test: an error was demonstrated passed test: no error was found, so far

7. RELIABILITY reliability : how closely the system conforms to expected behavior

8. FAULTS What is the difference between a fault and an error? What are some kinds of faults?

9. FAULTS error : incorrect behavior example: message box text said "Welcome null." fault : mechanical or algorithmic cause of error a fault is not an error, but it can lead to them need requirements to specify desired behavior, and need to see system deviate from that behavior, to have a failure

10. SOME TYPES OF FAULTS algorithmic faults design produces a poor algorithm fail to implement the software to match the specifications subsystems don't communicate properly mechanical faults earthquake virtual machine failure (why is this a "mechanical" fault?)

11. SOME TYPES OF FAULTS algorithmic faults design produces a poor algorithm fail to implement the software to match the spec subsystems don't communicate properly mechanical faults earthquake virtual machine failure (why is this a "mechanical" fault?)

12. More on faults and errors Faults in the Interface specification Mismatch between what the client needs and what the server offers Mismatch between requirements and implementation Algorithmic Faults Missing initialization Branching errors (too soon, too late) Missing test for nil Mechanical Faults (very hard to find) Documentation does not match actual conditions or operating procedures Errors Stress or overload errors Capacity or boundary errors Timing errors Throughput or performance errors

13. FAULT AVOIDANCE TECHNIQUES development methodologies: use requirements and design to minimize introduction of faults get clear requirements minimize coupling configuration management: don't allow changes to subsystem interfaces verification: find faults in system execution problems: not mature yet, assumes requirements are correct, assumes pre/ postconditions are adequate review: manual inspection of system walkthrough inspection

14. FAULT DETECTION TECHNIQUES fault detection: find existing faults without recovering from the errors debugging: move through steps to reach erroneous state testing: tries to expose errors in planned way (we are here) a good test model has test cases and test data that identify errors ideally, every possible input to a system should be tested this is prohibitively time-consuming

15. TYPES OF TESTING unit testing : looks for errors in objects or subsystems integration testing : find errors with connecting subsystems together system structure testing: integration testing all parts of system together system testing : test entire system behavior as a whole, with respect to scenarios and requirements functional testing: test whether system meets requirements performance testing: nonfunctional requirements, design goals acceptance / installation testing: done by client

16. TESTING CONCEPTS failure : particular instance of a general error, which is caused by a fault test case : set of inputs and outputs to cause failures

17. TEST PLANNING A Test Plan: covers all types and phases of testing guides the entire testing process who, why, when, what developed as requirements, functional specification, and high-level design are developed should be done before implementation starts A test plan includes: test objectives schedule and logistics test strategies test cases procedure data expected result procedures for handling problems

18. TESTING CONCEPTS Testing often viewed as dirty work. To develop an effective test, one must have: Detailed understanding of the system Knowledge of the testing techniques Skill to apply these techniques in an effective and efficient manner Testing is done best by independent testers We often develop a certain mental attitude that the program should in a certain way when in fact it does not. Programmer often stick to the data set that makes the program work "Don’t mess up my code!" A program often does not work when tried by somebody else.

19. Thank you! Thank you!