Fundamentals of Testing 2
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

Fundamentals of Testing 2

  • 3,314 views
Uploaded on

Fundamentals of Testing

Fundamentals of Testing

More in: Technology , Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
3,314
On Slideshare
3,282
From Embeds
32
Number of Embeds
4

Actions

Shares
Downloads
87
Comments
0
Likes
0

Embeds 32

http://startnewday85.blogspot.com 26
http://www.scoop.it 4
http://startnewday85.blogspot.in 1
http://webcache.googleusercontent.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. FUNDAMENTALS OF TESTING Hoang V. Nguyen startnewday85@gmail.com startnewday85.blogspot.com Dept. of Computer Science – FIT - HUATester Training Course
  • 2. Tester Training Course 2011
  • 3. Tester Training Course 2011
  • 4. Tester Training Course 2011
  • 5. Tester Training Course 2011
  • 6. Tester Training Course 2011
  • 7. Monitoring and control Planning Implementation Analysis Design Closure Execution Evaluating exit criteria Reporting test resultTester Training Course 2011
  • 8. Tester Training Course 2011
  • 9. Company Level Project Level Test stage LevelTester Training Course 2011
  • 10.  Run a test, it fails, fault reported  New version of software with fault “fixed”  Re-run the same test (i.e. re-test) • must be exactly repeatable • same environment, versions (except for the software which has been intentionally changed!) • same inputs and preconditions  If test now passes, fault has been fixed correctly - or has it?Tester Training Course 2011
  • 11. Tester Training Course 2011
  • 12.  To eliminate unexpected-side effects, but can still exist  Are performed: • after software changed, including faults fixed • when environment changes, even if application functionality not change • for emergency fixes(possibly a subset)  Regression test suites • evolve over time • are run often • may become rather largeTester Training Course 2011
  • 13. Question The five parts of the fundamental test process have a broad chronological order. Which of the options gives three different parts in the correct order? Impl. & exe., planning & control, analysis & design Analysis & design, eval. exit criteria & reporting, test closure activities; Eval. exit criteria & reporting, impl. And exe., analysis and design. Eval. exit criteria & reporting, test closure activities, analysis and design.Tester Training Course 2011
  • 14. Question Which option is part of the ’implementation and execution’ area of the fundamental test process?Developing the tests;Comparing actual and expected results;Writing a test summary;Analysing lessons learnt for future releases. Tester Training Course 2011
  • 15. Question As part of which test process do you determine the exit criteria? Test planning; Test closure; Evaluating exit criteria and reporting; Test control.Tester Training Course 2011
  • 16. Question Which of the following is a Major task of test implementation and execution?Measuring and anslyzing results;Reporting discrepancies as incidents;Identifying test conditions or test requirements;Assessing if more tests are needed. Tester Training Course 2011
  • 17. Question Which activity in the fundamental test process creates test suites for efficent test execution? Implementatin and execution; Planning and control; Analysis and design; Test closure.Tester Training Course 2011
  • 18. Question What is the purpose of exit criteria?To define when a test level is complete;To determine when a test has completed;To identify when a software system should beretired;To determine whether a test has passed.
  • 19. Question Which activities form part of test planning i. Developing test cases ii. Defining the overall approach to testing iii. Assigning resources iv. Building the test environment v. Writing test conditions i, ii & iv are true; iii & v are false ii & iii are true; iv & v are false iv & v are true; ii & iii are false i, ii & iii are true; iv & v are falseTester Training Course 2011
  • 20. Question When a defect is detected and fixed then the software should be retested to confirm that the original defect has been successfully removed. This called?Regression testing;Maintenance testing;Confirmation testing;None of the above. Tester Training Course 2011
  • 21. Question Which of the following are chracteristic of regression testing i. Regression testing is run Oly one ii. Regression testing is used after fixes have been made iii. Regression testing is often automated iv. Regression testing need not be maintained ii & iv ii & iii i, iii & iv iiiTester Training Course 2011
  • 22. Question Which of the following is true?Confirmation testing is testing fixes to a set ofdefects and regression testing is testing to establishwhether any defects have been introduced as aresult of changes;Confirmation testing is testing to establish whetherany defects have been introduced as a result ofchanges and regression testing s testing fixes to aset of defects;Confirmation testing and regression testing areboth testing to establish whether any defects havebeen introduced as a result of changes;Confirmation testing and regression testing areboth testing fixes to a set of defects. Tester Training Course 2011
  • 23. Question The different between re-testing and regression testing is Re-testing is running a test again; regression testing looks for unexpected side effects Re-testing looks for unexpected side effects; regression testing is repeating those tests Re-testing is done after faults are fixed; regression testing is done earlier Re-testing uses different environments; regression testing uses the same environment Re-testing is done by developer; regression testing is done by independent testersTester Training Course 2011
  • 24. Tester Training Course 2011
  • 25. Tester Training Course 2011
  • 26. Tester Training Course 2011
  • 27. Tester Training Course 2011
  • 28. Tester Training Course 2011
  • 29. Tester Training Course 2011
  • 30. Tester Training Course 2011
  • 31. Demonstrate conformance to requirements Find faults Prove that the software is correct Build confidence Assess the software qualityTester Training Course 2011
  • 32.  Goal: show that the system works correctly  Show that the system: • does what it should • doesn’t do what it shouldn’t  Success: the system work correctlyTester Training Course 2011
  • 33.  Goal: show that the system fails  Show that the system: • does what it shouldn’t • doesn’t do what it should  Success: the system failsTester Training Course 2011
  • 34. Tester Training Course 2011
  • 35. Tester Training Course 2011
  • 36. Test your own work  Is inefficient(30%-50% faults)  Because: • same assumptions and thought processes • see what you meant or want to see, not what is there • actively want not find faultsTester Training Course 2011
  • 37. Independence  Levels of dependence • None: tests designed by the person who wrote the software • Tests designed by a different person • Tests designed by someone from a different department or team (e.g. test team) • Tests designed by someone from a different organisation (e.g. Agency)Tester Training Course 2011
  • 38. • The fundamental test process • Psychology of testingTester Training Course 2011