ISTQB Sample Exam chương I: Fundamentals of Testing (K2)
Forum rules
Chuyên mục này chỉ được post các bài viết, câu hỏi liên quan đến chứng chỉ ISTQB.
Để có kết quả nhanh chóng, bạn nên search trước khi post bài mới.
Chuyên mục này chỉ được post các bài viết, câu hỏi liên quan đến chứng chỉ ISTQB.
Để có kết quả nhanh chóng, bạn nên search trước khi post bài mới.
-
- Admin
- Posts: 4900
- Joined: Tue 10 Aug, 2010 10:11 am
- Location: HCM
- Contact:
ISTQB Sample Exam chương I: Fundamentals of Testing (K2)
Bài tập chương I: Fundamentals of Testing (K2)
1. We split testing into distinct stages primarily because:
a) Each test stage has a different purpose.
b) It is easier to manage testing in stages.
c) We can run different tests in different environments.
d) The more stages we have, the better the testing.
2. Which of the following is false?
a) Incidents should always be fixed.
b) An incident occurs when expected and actual results differ.
c) Incidents can be analyzed to assist in test process improvement.
d) An incident can be raised against documentation.
3. Enough testing has been performed when:
a) time runs out.
b) the required level of confidence has been achieved.
c) no more faults are found.
d) the users won’t find any serious faults.
4. Which of the following is NOT true of incidents?
a) Incident resolution is the responsibility of the author of the software under test.
b) Incidents may be raised against user requirements.
c) Incidents require investigation and/or correction.
d) Incidents are raised when expected and actual results differ.
5. Which of the following is false?
a) In a system two different failures may have different severities.
b) A system is necessarily more reliable after debugging for the removal of a fault.
c) A fault need not affect the reliability of a system.
d) Undetected errors may lead to faults and eventually to incorrect behavior.
6. In prioritizing what to test, the most important objective is to:
a) find as many faults as possible.
b) test high risk areas.
c) obtain good test coverage.
d) test whatever is easiest to test.
7. Which of the following characterizes the cost of faults?
a) They are cheapest to find in the early development phases and the most expensive to fix in the latest test phases.
b) They are easiest to find during system testing but the most expensive to fix then.
c) Faults are cheapest to find in the early development phases but the most expensive to fix then.
d) Although faults are most expensive to find during early development phases, they are cheapest to fix then.
8. Which of the following should NOT normally be an objective for a test?
a) To find faults in the software.
b) To assess whether the software is ready for release.
c) To demonstrate that the software doesn’t work.
d) To prove that the software is correct.
9. A failure is:
a) found in the software; the result of an error.
b) departure from specified behavior.
c) an incorrect step, process or data definition in a computer program.
d) a human action that produces an incorrect result.
10. Data flow analysis studies:
a) possible communications bottlenecks in a program.
b) the rate of change of data values as a program executes.
c) the use of data on paths through the code.
d) the intrinsic complexity of the code.
1. We split testing into distinct stages primarily because:
a) Each test stage has a different purpose.
b) It is easier to manage testing in stages.
c) We can run different tests in different environments.
d) The more stages we have, the better the testing.
2. Which of the following is false?
a) Incidents should always be fixed.
b) An incident occurs when expected and actual results differ.
c) Incidents can be analyzed to assist in test process improvement.
d) An incident can be raised against documentation.
3. Enough testing has been performed when:
a) time runs out.
b) the required level of confidence has been achieved.
c) no more faults are found.
d) the users won’t find any serious faults.
4. Which of the following is NOT true of incidents?
a) Incident resolution is the responsibility of the author of the software under test.
b) Incidents may be raised against user requirements.
c) Incidents require investigation and/or correction.
d) Incidents are raised when expected and actual results differ.
5. Which of the following is false?
a) In a system two different failures may have different severities.
b) A system is necessarily more reliable after debugging for the removal of a fault.
c) A fault need not affect the reliability of a system.
d) Undetected errors may lead to faults and eventually to incorrect behavior.
6. In prioritizing what to test, the most important objective is to:
a) find as many faults as possible.
b) test high risk areas.
c) obtain good test coverage.
d) test whatever is easiest to test.
7. Which of the following characterizes the cost of faults?
a) They are cheapest to find in the early development phases and the most expensive to fix in the latest test phases.
b) They are easiest to find during system testing but the most expensive to fix then.
c) Faults are cheapest to find in the early development phases but the most expensive to fix then.
d) Although faults are most expensive to find during early development phases, they are cheapest to fix then.
8. Which of the following should NOT normally be an objective for a test?
a) To find faults in the software.
b) To assess whether the software is ready for release.
c) To demonstrate that the software doesn’t work.
d) To prove that the software is correct.
9. A failure is:
a) found in the software; the result of an error.
b) departure from specified behavior.
c) an incorrect step, process or data definition in a computer program.
d) a human action that produces an incorrect result.
10. Data flow analysis studies:
a) possible communications bottlenecks in a program.
b) the rate of change of data values as a program executes.
c) the use of data on paths through the code.
d) the intrinsic complexity of the code.
-
- Admin
- Posts: 4900
- Joined: Tue 10 Aug, 2010 10:11 am
- Location: HCM
- Contact:
Re: ISTQB Sample Exam chương I: Fundamentals of Testing (K2)
Thêm nữa...
11. IEEE 829 test plan documentation standard contains all of the following except
a) test items
b) test deliverables
c) test tasks
d) test specifications
12. Incidents would not be raised against:
a) requirements
b) documentation
c) test cases
d) improvements suggested by users
13. Expected results are:
a) only important in system testing
b) only used in component testing
c) most useful when specified in advance
d) derived from the code
14. Which of the following is NOT a reasonable test objective:
a) to find faults in the software
b) to prove that the software has no faults
c) to give confidence in the software
d) to find performance problems
15. Which statement about expected outcomes is FALSE?
a) expected outcomes are defined by the software's behavior
b) expected outcomes are derived from a specification, not from the code
c) expected outcomes should be predicted before a test is run
d) expected outcomes may include timing constraints such as response times
16. The standard that gives definitions of testing terms is:
a) ISO/IEC 12207
b) BS 7925-1
c) ANSI/IEEE 829
d) ANSI/IEEE 729
17. Which of the following is NOT included in the Test Plan document of the Test Documentation Standard?
a) what is not to be tested
b) test environment properties
c) quality plans
d) schedules and deadlines
18. The cost of fixing a fault:
a) is not important
b) increases the later a fault is found
c) decreases the later a fault is found
d) can never be determined
19. Which of the following statements about component testing is FALSE?
a) black box test design techniques all have an associated test measurement technique
b) white box test design techniques all have an associated test measurement technique
c) cyclomatic complexity is not a test measurement technique
d) black box test measurement techniques all have an associated test design technique
20. Consider the following statements:
i. an incident may be closed without being fixed.
ii. incidents may not be raised against documentation.
iii. the final stage of incident tracking is fixing.
iv. the incident record does not include information on test environments.
a) ii is true, i, iii and iv are false
b) i is true, ii, iii and iv are false
c) i and iv are true, ii and iii are false
d) i and ii are true, iii and iv are false
21. A deviation from the specified or expected behavior that is visible to endusers is called:
a) an error
b) a fault
c) a failure
d) a defect
11. IEEE 829 test plan documentation standard contains all of the following except
a) test items
b) test deliverables
c) test tasks
d) test specifications
12. Incidents would not be raised against:
a) requirements
b) documentation
c) test cases
d) improvements suggested by users
13. Expected results are:
a) only important in system testing
b) only used in component testing
c) most useful when specified in advance
d) derived from the code
14. Which of the following is NOT a reasonable test objective:
a) to find faults in the software
b) to prove that the software has no faults
c) to give confidence in the software
d) to find performance problems
15. Which statement about expected outcomes is FALSE?
a) expected outcomes are defined by the software's behavior
b) expected outcomes are derived from a specification, not from the code
c) expected outcomes should be predicted before a test is run
d) expected outcomes may include timing constraints such as response times
16. The standard that gives definitions of testing terms is:
a) ISO/IEC 12207
b) BS 7925-1
c) ANSI/IEEE 829
d) ANSI/IEEE 729
17. Which of the following is NOT included in the Test Plan document of the Test Documentation Standard?
a) what is not to be tested
b) test environment properties
c) quality plans
d) schedules and deadlines
18. The cost of fixing a fault:
a) is not important
b) increases the later a fault is found
c) decreases the later a fault is found
d) can never be determined
19. Which of the following statements about component testing is FALSE?
a) black box test design techniques all have an associated test measurement technique
b) white box test design techniques all have an associated test measurement technique
c) cyclomatic complexity is not a test measurement technique
d) black box test measurement techniques all have an associated test design technique
20. Consider the following statements:
i. an incident may be closed without being fixed.
ii. incidents may not be raised against documentation.
iii. the final stage of incident tracking is fixing.
iv. the incident record does not include information on test environments.
a) ii is true, i, iii and iv are false
b) i is true, ii, iii and iv are false
c) i and iv are true, ii and iii are false
d) i and ii are true, iii and iv are false
21. A deviation from the specified or expected behavior that is visible to endusers is called:
a) an error
b) a fault
c) a failure
d) a defect
-
- Hoc Tester
- Posts: 3
- Joined: Sun 03 Apr, 2011 1:53 am
- Contact:
Re: ISTQB Sample Exam chương I: Fundamentals of Testing (K2)
Xin hoi co ai co bai giai nay ko cho minh xin voi
-
- Admin
- Posts: 4900
- Joined: Tue 10 Aug, 2010 10:11 am
- Location: HCM
- Contact:
Re: ISTQB Sample Exam chương I: Fundamentals of Testing (K2)
Hi bạn,
Những câu hỏi này mình tập hợp từ những bài test đã post, vì vậy nếu bạn down phần 500 ISTQB Sample Papers 2010-2011 thì bạn có thể gặp tất cả 21 câu trên.
File đính kèm là đáp án của các câu này.
Xin lỗi các bạn, trong file lần trước mình gõ nhầm, câu 1 là E, mình đã sửa lại câu 1 là A và đã up lên lại file mới
Những câu hỏi này mình tập hợp từ những bài test đã post, vì vậy nếu bạn down phần 500 ISTQB Sample Papers 2010-2011 thì bạn có thể gặp tất cả 21 câu trên.
File đính kèm là đáp án của các câu này.
Xin lỗi các bạn, trong file lần trước mình gõ nhầm, câu 1 là E, mình đã sửa lại câu 1 là A và đã up lên lại file mới
You do not have the required permissions to view the files attached to this post.
-
- Fresher Tester
- Posts: 11
- Joined: Mon 26 Sep, 2011 4:09 pm
- Contact:
Re: ISTQB Sample Exam chương I: Fundamentals of Testing (K2)
Bạn post tiếp bài tập cũng như đáp án của chương 1 và các chương tiếp theo được ko? Làm bài tập theo từng chương sẽ tốt hơn. Thanks
-
- Admin
- Posts: 4900
- Joined: Tue 10 Aug, 2010 10:11 am
- Location: HCM
- Contact:
Re: ISTQB Sample Exam chương I: Fundamentals of Testing (K2)
Gửi các bạn các câu hỏi tiếp theo của chương I
23. Regression testing should be performed:
Nội dung đầy đủ các câu hỏi chương I, bao gồm đáp án.
23. Regression testing should be performed:
- v) Every week
w) After the software has changed
x) As often as possible
y) When the environment has changed
z) When the project manager says
a) v & w are true, x – z are false
b) w, x & y are true, v & z are false
c) w & y are true, v, x & z are false
d) w is true, v, x y and z are false
- a) all the planned tests have been run
b) time has run out
c) all faults have been fixed correctly
d) it depends on the risks for the system being tested
- i. early test design can prevent fault multiplication
ii. faults found during early test design are more expensive to fix
iii. early test design can find faults
iv. early test design can cause changes to the requirements
v. early test design takes more effort
a) i, iii & iv are true. Ii & v are false
b) iii is true, I, ii, iv & v are false
c) iii & iv are true. i, ii & v are false
d) i, iii, iv & v are true, ii us false
- a) finding faults in the system
b) ensuring that the system is acceptable to all users
c) testing the system with other systems
d) testing for a business perspective
- a) re-testing is running a test again; regression testing looks for unexpected side effects
b) re-testing looks for unexpected side effects; regression testing is repeating those tests
c) re-testing is done after faults are fixed; regression testing is done earlier
d) re-testing is done by developers, regression testing is done by independent testers
- a) only important in system testing
b) only used in component testing
c) never specified in advance
d) most useful when specified in advance
- a) Is not important
b) Increases as we move the product towards live use
c) Decreases as we move the product towards live use
d) Is more expensive if found in requirements than functional design
- a. Error condition hiding another error condition
b. creating a test case which does not reveal a fault
c. masking a fault by developer
d. masking a fault by a tester
- a. Lack of technical documentation
b. Lack of test tools on the market for developers
c. Lack of training
d. Lack of Objectivity
- a) Time runs out.
b) The required level of confidence has been achieved.
c) No more faults are found.
d) The users won’t find any serious faults.
- a) In a system two different failures may have different severities.
b) A system is necessarily more reliable after debugging for the removal of a fault.
c) A fault need not affect the reliability of a system.
d) Undetected errors may lead to faults and eventually to incorrect behavior.
- a) They are cheapest to find in the early development phases and the less expensive to fix.
b) They are easiest to find during system testing but the most expensive to fix then.
c) Faults are cheapest to find in the early development phases but the most expensive to fix then.
d) Although faults are most expensive to find during early development phases, they are cheapest to fix then.
- a) Negative feedback to the tester.
b) Negative consequences that will occur.
c) Negative consequences that could occur.
d) Negative consequences for the test object.
- a) Preventing defects in the system.
b) Finding defects through dynamic testing.
c) Gaining confidence in the system.
d) Finishing the project on time.
- a) Found in the software; the result of an error.
b) Departure from specified behavior.
c) An incorrect step, process or data definition in a computer program.
d) A human action that produces an incorrect result.
- a. Poor quality software
b. Poor software and poor testing
c. bad luck
d. insufficient time for testing
- a. Faults in program specifications are the most expensive to fix.
b. Faults in code are the most expensive to fix.
c. Faults in requirements are the most expensive to fix
d. Faults in designs are the most expensive to fix.
- a. Commercial off the shelf software
b. Compliance of the software
c. Change control of the software
d. Capable off the shelf software
- a. Finding defects
b. Gaining confidence about the level of quality and providing information
c. Preventing defects.
d. Debugging defects
- a) Impractical but possible
b) Practically possible
c) Impractical and impossible
d) Always possible
- a) Understanding what Managers value about testing.
b) Explaining test results in a neutral fashion.
c) Identifying potential customer work-around for bugs.
d) Promoting better quality software whenever possible.
- a) Failure
b) Defect
c) Mistake
d) Bug
- a) Find as many faults as possible.
b) Test high risk areas.
c) Obtain good test coverage.
d) Test whatever is easiest to test.
- a) Requirements
b) Documentation
c) Test cases
d) Improvements suggested by users
- a) Test Implementation and execution
b) Test Analysis and Design
c) Evaluating the Exit Criteria and reporting
d) Test Closure Activities
- a) Creating test suites from the test cases
b) Executing test cases either manually or by using test execution tools
c) Comparing actual results
d) Designing the Tests
- a. Test Harness
b. Test Suite
c. Test Cycle
d. Test Driver
- 1) Testing fault
2) Software fault
3) Design fault
4) Environment Fault
5) Documentation Fault
a. 2 is a valid reason; 1,3,4 & 5 are not
b. 1,2,3,4 are valid reasons; 5 is not
c. 1,2,3 are valid reasons; 4 & 5 are not
d. All of them are valid reasons for failure
- a) Test Analysis and Design
b) Test Planning and control
c) Test Closure Activities
d) Evaluating exit criteria and reporting
- a) All combination of input values and preconditions.
b) All combination of input values and output values.
c) All pairs of input values and preconditions.
d) All states and state transitions.
- a) Unit Testing.
b) System Testing.
c) Independent Testing.
d) Destructive Testing.
- I Analysis and Design
II Test Closure activities
III Evaluating exit criteria and reporting
IV Planning and Control
V Implementation and execution
Which of the following places these in their logical sequence?
a) I, II, III, IV and V
b) IV, I, V, III and II
c) IV, I, V, II and III
d) I, IV, V, III and II
- a) Is part of the fundamental test process.
b) Includes the repair of the cause of a failure
c) Involves intentionally adding known defects
d) Follows the steps of a test procedure
- a) Insufficient funds were available to pay the interest rate calculated.
b) Insufficient calculations of compound interest were included.
c) Insufficient training was given to the developers concerning compound interest calculation rules.
d) Incorrect calculators were used to calculate the expected results.
- a) When the time for testing has run out
b) When all planned tests have been run
c) When the test completion criteria have been met
d) When no faults have been found by the tests run
- a) Only records defects
b) is of limited value
c) is a valuable source of project information during testing if it contains all incidents
d) Should be used only by the test team
- a) Exploratory testing
b) Regression testing
c) Exhaustive testing
d) Re- testing
- i. an incident may be closed without being fixed.
ii. Incidents may not be raised against documentation.
iii. The final stage of incident tracking is fixing.
iv. The incident record does not include information on test environments.
a) ii is true, i, iii and iv are false
b) i is true, ii, iii and iv are false
c) i and iv are true, ii and iii are false
d) i and ii are true, iii and iv are false
- a) Software is developed or engineered; it is not manufactured in the classic sense
b) Software doesn’t “wear out” with the time
c) The traditional industry is moving toward component based assembly, whereas most software continues to be custom built and the concept of component based assembly is still taking shape
d) Software does not require maintenance
- a) We cannot run the test
b) It may be difficult to repeat the test
c) It may be difficult to determine if the test has passed or failed
d) We cannot automate the user inputs
- a) is unlikely to be completed on schedule
b) is unlikely to cause a failure
c) is likely to be fault free
d) is likely to be liked by the users
- a) To determine when writing a test case is complete
b) To determine when to stop the testing
c) To ensure the test specification is complete
d) To determine when to stop writing the test plan
- a) Re-Testing ensures the original fault has been removed
b) Re-Testing prevents future faults
c) Re-Testing looks for unexpected side effects
d) Re-Testing ensures the original fault is still present
- a) Discussions with the end users
b) Discussions with the developers
c) Metrics from Previous projects
d) none of the above
- a) An Error
b) A Fault
c) A Failure
d) An Action
- a) Only test high risk areas
b) Only test simple areas
c) Only test low risk areas
d) Only test complicated areas
- a) All faults have been reviewed
b) All faults have been found
c) All faults have been raised
d) All faults have been rectified
- a) Quality is job one
b) Zero defects
c) Conformance to requirements
d) Work as designed
- a) To show the system will work after release
b) To decide when software is of sufficient quality to release
c) To find as many of bugs as possible before release
d) To give information for a risk based decision about release
- a) The domain of possible inputs is too large to test.
b) Limited financial resources.
c) There are too many possible paths through the program to test.
d) The user interface issues (and thus the design issues) are too complex to completely test.
Nội dung đầy đủ các câu hỏi chương I, bao gồm đáp án.
You do not have the required permissions to view the files attached to this post.
-
- Fresher Tester
- Posts: 11
- Joined: Mon 26 Sep, 2011 4:09 pm
- Contact:
-
- Hoc Tester
- Posts: 3
- Joined: Wed 28 Sep, 2011 12:30 pm
- Contact:
Re: ISTQB Sample Exam chương I: Fundamentals of Testing (K2)
Thanks Bạn,nhưng mấy cái summary lý thuyết về chapter I,I,III.... Admin lại delete thread. mình nghĩ đọc cái đó rất có ích mà ta.
Admin re-open thread viewtopic.php?f=21&t=568 lai dc ko vậy ?
Admin re-open thread viewtopic.php?f=21&t=568 lai dc ko vậy ?
-
- Admin
- Posts: 4900
- Joined: Tue 10 Aug, 2010 10:11 am
- Location: HCM
- Contact:
Re: ISTQB Sample Exam chương I: Fundamentals of Testing (K2)
Chào mọi người,
Không phải là do admin xóa đâu, mà do forum của mình bị hacked nên restore lại DB tháng 6 nên mất khá nhiều bài.
Admin đang nỗ lực up lên lại đây hix
Mời các bạn xem thông báo Thông báo về việc mất môt số thông tin thành viên và bài viết
Mọi người thông cảm chờ nhé.
thanks
Không phải là do admin xóa đâu, mà do forum của mình bị hacked nên restore lại DB tháng 6 nên mất khá nhiều bài.
Admin đang nỗ lực up lên lại đây hix
Mời các bạn xem thông báo Thông báo về việc mất môt số thông tin thành viên và bài viết
Mọi người thông cảm chờ nhé.
thanks
-
- Hoc Tester
- Posts: 3
- Joined: Wed 28 Sep, 2011 12:30 pm
- Contact:
Re: ISTQB Sample Exam chương I: Fundamentals of Testing (K2)
Trời.Page hay vậy mà ai hack chi ta.
Admin cố gắng làm lại nhé. Với lai mình nghĩ có ai đã thi và chuẩn bị thi thì cũng nên vào đây chia sẽ kinh nghiệm làm bài trong năm 2011 này dc ko.
Nice days.
Admin cố gắng làm lại nhé. Với lai mình nghĩ có ai đã thi và chuẩn bị thi thì cũng nên vào đây chia sẽ kinh nghiệm làm bài trong năm 2011 này dc ko.
Nice days.