Sie sind auf Seite 1von 6

Cc loi test: 1) Test cp n v (Unit testing) 2) Test cu hnh (Shakeout testing) 3) Test s lt (Smoke testing (Ad-hoc testing)) 4) Test

chc nng (Functional testing) 5) Test tch hp (Integration testing) 6) Test hi quy (Regression testing) 7) Test h thng (System testing) 8)Test ti d liu (Load testing) 9) Test ti trng (Stress testing) 10) Test hiu sut (Performance testing) 11) Test chp nhn t ngi s dng (User acceptance testing) 12) Test hp en (Black box testing) 13) Test hp trng (White box testing) 14) Test Alpha (Alpha testing) 15) Test Beta (Beta testing) 16) Test bo mt (Security Test) CH-04.1. Test Method Definition: A definitive procedure for the identification, measurement, and evaluation of a material, product, system, or service that produces a test result. (a) TRUE (b) FALSE CH-04.2. Choose valid(ng n) test types (a) Regression Testing (b) Allocation Testing (c) Smoke Testing (d) Performance Testing (e) A,B and D (f) A,C and D CH-04.3. The primary goal of Requirement-based Testing (a) Requirement Experiment (b) Bug hunting (c) Behavioral Exploratory (d) Requirement Validation CH-04.4. The primary goal of exploratory testing

(a) Find bugs on-the-fly (b) Complete Test and Verify that the AUT works correctly (c) Verify functions of AUT works as the programmer expects (d) Requirement-based Validation CH-04.5. Purposes of regression testing (a) Find new bugs (b) Prove that AUT works 100% as expected (c) Verify that the modifications have not caused any unintended effects (d) Make sure that the bugs marked as fixed by developers are really fixed (e) B and C (f) C and D CH-04.6. Smoke test is (a) Collection of all ad-hoc tests that are performed on a system (b) A collection of written tests that are performed on a system prior to being accepted for further testing, also known as build verification test. (c) A collection of test requirements to be validated on a system prior to being accepted for further testing (d) A collection of software requirements to be smoked on a system prior to being accepted for further testing CH-04.7. Example(s) of Common Type of Black Box Testing include: (a) Feature-Level Test (b) Unit Test (c) Configuration & Compatibility Test (d) Acceptance Test (e) A,B and D (f) A,C and D CH-04.8. Test Case is (a) A test that (ideally) executes a single well defined test objective (b) Steps that (ideally) are executed a to verify a number of test objectives (c) Process that (ideally) executes to meet a well defined objective (d) Procedure that (ideally) executes to single out a well defined objective CH-04.9. What are reasons or motivation for writing test case? (a) For compliance (b) Reproducibility (c) Help measure test coverage (d) Automation

(e) All of the above (f) A,C and D CH-04.10. An excellent Test Case should satisfy the following criteria: (a) Reasonable probability of catching an error (b) Makes program run better (c) Neither too simple nor too complex (d) Not redundant with other tests (e) A,B and D (f) A,C and D CH-04.11. The most important part of a test case is (a) Test Case condition (b) Bug report procedure (c) The one-line title describing the objective of the test (d) Test case status CH-04.12. Test Objective suggested syntax is (a) Operating Condition + Action + Function (b) Action + Test Requirement + Operating Condition (c) Function + Action + Operating Condition (d) Action + Function + Operating Condition CH-04.13. Test Case Design Techniques include (a) Risk-based testing (b) Equivalence Partitioning (c) State Transition/ Model-Based Testing (d) Boundary Value Analysis (e) A,B and C (f) B,C and D CH-04.14. For each equivalence class partition, what is the maximum number of test cases to execute? (see diagram below) (a) 3 (b) 9 (c) 5 (d) 7 CH-06.1. What is a software error? CH-06.2. What is the difference between failure and error? CH-06.3. What should you do if you find a bug but cannot reproduce it

again? CH-06.4. What is a Coding Error? 1. The program doesnt do what the programmer would expect it to do. 2. Its doing what the programmer intended, but a reasonable customer would be confused or unhappy with it. 3. The program is well designed and well implemented, but it wont meet one of the customers requirements. CH-06.5.What are the criteria to rank bugs? a. Reproducibility b. Severity c. Complexity d. Frequency e. Priority f. Simplicity 1. A only 2. B & C only 3. B, C, D & E 4. None of the above 5. All of the above CH-06.6. Bugs 1. You should report a bug even if it is not reproducible. 2. You should only report a bug when you can reproduce it. 3. Never report a bug unless you can reproduce it. 4. Tell your test lead about non-reproducible bugs but do not put it in the bug tracking system. CH-06.7. What are the common source of software errors? a. Coding error b. Design Issue c. Requirement Issue d. User error e. All of the above f. a ,b and c CH-06.8. Requirement Issues mean a. The program is well designed and well implemented, but it wont meet one of the customers requirements.

b. The program meets the requirements with some deferral bugs. c. Design Issues d. The user is at fault e. All of the above f. a, c and d CH-06.9. What are the main steps in a bug finding process? a. Reproduce error b. Analyze the error c. Report the error d. Regress Bug e. a, b and c f. b, c and d CH-06.10. What should we do if the bug is non-reproducible? a. Ignore it b. Report and describe your steps and observations precisely c. Dont report but call the developer d. Report using email only CH-06.11. Which are the main benefits of analyzing software error? a. Make your communication effectively b. Support the making of business decisions c. Avoid wasting the time of the programming and management staff d. Find more bugs e. All of the above f. None of the above CH-06.12.What are the common mistakes in bug report? a. Lack of information to reproduce a bug b. Simple (non compound) c. Judgmental d. Duplicate bug e. a, c and d f. a, b and c CH-06.13. The 3 main items of a bug report are a. Steps to reproduce b. Description c. Summary d. Priority

e. None of the above f. a, b and c CH-06.14. Examples of a good bug summary include a. Maximize button is still active while the dialog box is maximized b. Application crashes when clicking on the Submit button on a Win2K system c. The application crashes badly d. Severe Performance Problems e. a and d f. a and b CH-06.15. What should we have in the bug description ? a. Description of the problem b. The steps to recreate a bug c. The personal opinion d. The erroneous versus the expected behavior e. All of the above f. a, b and d