{"id":313,"date":"2023-09-10T09:13:13","date_gmt":"2023-09-10T09:13:13","guid":{"rendered":"https:\/\/softwaretestingstuff.com\/?p=313"},"modified":"2023-09-10T10:05:32","modified_gmt":"2023-09-10T10:05:32","slug":"iseb-foundation-certificate-in-software-testing-practice-exam-1","status":"publish","type":"post","link":"https:\/\/www.softwaretestingstuff.com\/2008\/05\/iseb-foundation-certificate-in-software.html","title":{"rendered":"ISEB Foundation Certificate in Software Testing Practice Exam – 1"},"content":{"rendered":"\n
Q1. We split testing into distinct stages primarily because:<\/strong><\/p>\n\n\n\n a) Each test stage has a different purpose. Q2. Which of the following is likely to benefit most from the use of test tools providing test capture and replay <\/strong><\/p>\n\n\n\n facilities? Q3. Which of the following statements is NOT correct?<\/strong><\/p>\n\n\n\n a) A minimal test set that achieves 100% LCSAJ coverage will also achieve 100% branch coverage. Q4. Which of the following requirements is testable?<\/strong><\/p>\n\n\n\n a) The system shall be user friendly. Q5. Analyse the following highly simplified procedure:<\/strong><\/p>\n\n\n\n Ask: \u201cWhat type of ticket do you require, single or return?\u201d Q6. Error guessing:<\/strong><\/p>\n\n\n\n a) supplements formal test design techniques. Q7. Which of the following is NOT true of test coverage criteria?<\/strong><\/p>\n\n\n\n a) Test coverage criteria can be measured in terms of items exercised by a test suite. Q8. In prioritising what to test, the most important objective is to:<\/strong><\/p>\n\n\n\n a) find as many faults as possible. Q9. Given the following sets of test management terms (v-z), and activity descriptions (1-5), which one of the following best pairs the two sets?<\/strong><\/p>\n\n\n\n v \u2013 test control 1 – calculation of required test resources a) v-3,w-2,x-1,y-5,z-4 Q10. Which one of the following statements about system testing is NOT true?<\/strong><\/p>\n\n\n\n a) System tests are often performed by independent teams. Q11. Which of the following is false?<\/strong><\/p>\n\n\n\n a) Incidents should always be fixed. Q12. Enough testing has been performed when:<\/strong><\/p>\n\n\n\n a) time runs out. Q13. Which of the following is NOT true of incidents?<\/strong><\/p>\n\n\n\n a) Incident resolution is the responsibility of the author of the software under test. Q14. Which of the following is not described in a unit test standard?<\/strong><\/p>\n\n\n\n a) syntax testing Q15. Which of the following is false?<\/strong><\/p>\n\n\n\n a) In a system two different failures may have different severities. Q16. Which one of the following statements, about capture-replay tools, is NOT correct?<\/strong><\/p>\n\n\n\n a) They are used to support multi-user testing. Q17. How would you estimate the amount of re-testing likely to be required?<\/strong><\/p>\n\n\n\n a) Metrics from previous similar projects Q18. Which of the following is true of the V-model?<\/strong><\/p>\n\n\n\n a) It states that modules are tested against user requirements. Q19. The oracle assumption:<\/strong><\/p>\n\n\n\n a) is that there is some existing system against which test output may be checked. Q20. Which of the following characterises the cost of faults?<\/strong><\/p>\n\n\n\n a) They are cheapest to find in the early development phases and the most expensive to fix in the latest test phases. Q21. Which of the following should NOT normally be an objective for a test?<\/strong><\/p>\n\n\n\n a) To find faults in the software. Q22. Which of the following is a form of functional testing?<\/strong><\/p>\n\n\n\n a) Boundary value analysis Q23. Which of the following would NOT normally form part of a test plan?<\/strong><\/p>\n\n\n\n a) Features to be tested Q24. Which of these activities provides the biggest potential cost saving from the use of CAST?<\/strong><\/p>\n\n\n\n a) Test management Q25. Which of the following is NOT a white box technique?<\/strong><\/p>\n\n\n\n a) Statement testing Q26. Data flow analysis studies:<\/strong><\/p>\n\n\n\n a) possible communications bottlenecks in a program. Q27. In a system designed to work out the tax to be paid:An employee has \u00a34000 of salary tax free. The next \u00a31500 is taxed at 10%The next \u00a328000 is taxed at 22%Any further amount is taxed at 40%To the nearest whole pound, which of these is a valid Boundary Value Analysis test case?<\/strong><\/p>\n\n\n\n a) \u00a31500 Q28. An important benefit of code inspections is that they:<\/strong><\/p>\n\n\n\n a) enable the code to be tested before the execution environment is ready. Q29. Which of the following is the best source of Expected Outcomes for User Acceptance Test scripts?<\/strong><\/p>\n\n\n\n a) Actual results Q30. What is the main difference between a walkthrough and an inspection?<\/strong><\/p>\n\n\n\n a) An inspection is lead by the author, whilst a walkthrough is lead by a trained moderator. Q31. Which one of the following describes the major benefit of verification early in the life cycle?<\/strong><\/p>\n\n\n\n a) It allows the identification of changes in user requirements. Q32. Integration testing in the small:<\/strong><\/p>\n\n\n\n a) tests the individual components that have been developed. Q33. Static analysis is best described as:<\/strong><\/p>\n\n\n\n a) the analysis of batch programs. Q34. Alpha testing is:<\/strong><\/p>\n\n\n\n a) post-release testing by end user representatives at the developer\u2019s site. Q35. A failure is:<\/strong><\/p>\n\n\n\n a) found in the software; the result of an error. Q36. In a system designed to work out the tax to be paid:An employee has \u00a34000 of salary tax free. The next \u00a31500 is taxed at 10%The next \u00a328000 is taxed at 22%Any further amount is taxed at 40%Which of these groups of numbers would fall into the same equivalence class?<\/strong><\/p>\n\n\n\n a) \u00a34800; \u00a314000; \u00a328000 Q37. The most important thing about early test design is that it:<\/strong><\/p>\n\n\n\n a) makes test preparation easier. Q38. Which of the following statements about reviews is true?<\/strong><\/p>\n\n\n\n a) Reviews cannot be performed on user requirements specifications. Q39. Test cases are designed during:<\/strong><\/p>\n\n\n\n a) test recording. Q40. A configuration management system would NOT normally provide:<\/strong><\/p>\n\n\n\n a) linkage of customer requirements to version numbers. Also See:<\/strong> Below are the answers of the questions in this post:<\/p>\n\n\n\n 1 – A Q1. 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. Q2. Which of the following is likely to benefit most from the use of test […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[14],"tags":[],"table_tags":[],"class_list":["post-313","post","type-post","status-publish","format-standard","hentry","category-software-testing-certification"],"yoast_head":"\n
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.<\/p>\n\n\n\n
a) Regression testing
b) Integration testing
c) System testing
d) User acceptance testing<\/p>\n\n\n\n
b) A minimal test set that achieves 100% path coverage will also achieve 100% statement coverage.
c) A minimal test set that achieves 100% path coverage will generally detect more faults than one that achieves 100% statement coverage.
d) A minimal test set that achieves 100% statement coverage will generally detect more faults than one that achieves 100% branch coverage.<\/p>\n\n\n\n
b) The safety-critical parts of the system shall contain 0 faults.
c) The response time shall be less than one second for the specified design load.
d) The system shall be built to be portable.<\/p>\n\n\n\n
IF the customer wants \u2018return\u2019
Ask: \u201cWhat rate, Standard or Cheap-day?\u201d
IF the customer replies \u2018Cheap-day\u2019
Say: \u201cThat will be \u00a311:20\u201d
ELSE
Say: \u201cThat will be \u00a319:50\u201d
ENDIF
ELSE
Say: \u201cThat will be \u00a39:75\u201d
ENDIF
Now decide the minimum number of tests that are needed to ensure that all the questions have been asked, all combinations have occurred and all replies given.
a) 3
b) 4
c) 5
d) 6<\/p>\n\n\n\n
b) can only be used in component, integration and system testing.
c) is only performed in user acceptance testing.
d) is not repeatable and should not be used.<\/p>\n\n\n\n
b) A measure of test coverage criteria is the percentage of user requirements covered.
c) A measure of test coverage criteria is the percentage of faults found.
d) Test coverage criteria are often used when specifying test completion criteria.<\/p>\n\n\n\n
b) test high risk areas.
c) obtain good test coverage.
d) test whatever is easiest to test.<\/p>\n\n\n\n
w \u2013 test monitoring
x – test estimation
y – incident management
z – configuration control<\/p>\n\n\n\n
2 – maintenance of record of test results
3 – re-allocation of resources when tests overrun
4 – report on deviation from test plan
5 – tracking of anomalous test results<\/p>\n\n\n\n
b) v-2,w-5,x-1,y-4,z-3
c) v-3,w-4,x-1,y-5,z-2 v-2,
d) w-1,x-4,y-3,z-5<\/p>\n\n\n\n
b) Functional testing is used more than structural testing.
c) Faults found during system tests can be very expensive to fix.
d) End-users should be involved in system tests.<\/p>\n\n\n\n
b) An incident occurs when expected and actual results differ.
c) Incidents can be analysed to assist in test process improvement.
d) An incident can be raised against documentation.<\/p>\n\n\n\n
b) the required level of confidence has been achieved.
c) no more faults are found.
d) the users won\u2019t find any serious faults.<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
b) equivalence partitioning
c) stress testing
d) modified condition\/decision coverage<\/p>\n\n\n\n
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 behaviour.<\/p>\n\n\n\n
b) They are used to capture and animate user requirements.
c) They are the most frequently purchased types of CAST tool.
d) They capture aspects of user behavior.<\/p>\n\n\n\n
b) Discussions with the development team
c) Time allocated for regression testing
d) a & b<\/p>\n\n\n\n
b) It only models the testing phase.
c) It specifies the test techniques to be used.
d) It includes the verification of designs.<\/p>\n\n\n\n
b) is that the tester can routinely identify the correct outcome of a test.
c) is that the tester knows everything about the software under test.
d) is that the tests are reviewed by experienced testers.<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
b) To assess whether the software is ready for release.
c) To demonstrate that the software doesn\u2019t work.
d) To prove that the software is correct.<\/p>\n\n\n\n
b) Usability testing
c) Performance testing
d) Security testing<\/p>\n\n\n\n
b) Incident reports
c) Risks
d) Schedule<\/p>\n\n\n\n
b) Test design
c) Test execution
d) Test planning<\/p>\n\n\n\n
b) Path testing
c) Data flow testing
d) State transition testing<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
b) \u00a332001
c) \u00a333501
d) \u00a328000<\/p>\n\n\n\n
b) can be performed by the person who wrote the code.
c) can be performed by inexperienced staff.
d) are cheap to perform.<\/p>\n\n\n\n
b) Program specification
c) User requirements
d) System specification<\/p>\n\n\n\n
b) An inspection has a trained leader, whilst a walkthrough has no leader.
c) Authors are not present during inspections, whilst they are during walkthroughs.
d) A walkthrough is lead by the author, whilst an inspection is lead by a trained moderator<\/p>\n\n\n\n
b) It facilitates timely set up of the test environment.
c) It reduces defect multiplication.
d) It allows testers to become involved early in the project.<\/p>\n\n\n\n
b) tests interactions between modules or subsystems.
c) only uses components that form part of the live system.
d) tests interfaces to other systems<\/p>\n\n\n\n
b) the reviewing of test plans.
c) the analysis of program code.
d) the use of black box testing<\/p>\n\n\n\n
b) the first testing that is performed.
c) pre-release testing by end user representatives at the developer\u2019s site.
d) pre-release testing by end user representatives at their sites.<\/p>\n\n\n\n
b) departure from specified behaviour.
c) an incorrect step, process or data definition in a computer program.
d) a human action that produces an incorrect result.<\/p>\n\n\n\n
b) \u00a35200; \u00a35500; \u00a328000
c) \u00a328001; \u00a332000; \u00a335000
d) \u00a35800; \u00a328000; \u00a332000<\/p>\n\n\n\n
b) means inspections are not required.
c) can prevent fault multiplication.
d) will find all faults.<\/p>\n\n\n\n
b) Reviews are the least effective way of testing code.
c) Reviews are unlikely to find faults in test plans.
d) Reviews should be performed on specifications, code, and test plans.<\/p>\n\n\n\n
b) test planning.
c) test configuration.
d) test specification.<\/p>\n\n\n\n
b) facilities to compare test results with expected results.
c) the precise differences in versions of software component source code.
d) restricted access to the source code library.<\/p>\n\n\n\n
ISEB Paper – 2<\/strong><\/a>
ISEB Paper – 3<\/strong><\/a>
CSTE Paper – 1<\/strong><\/a>
<\/strong>CSTE Paper – 2<\/strong><\/a>
<\/strong>CSTE Paper – 3<\/strong><\/a>
ISTQB Paper – 1<\/strong><\/a>
ISTQB Paper – 2<\/strong><\/a>
ISTQB Paper – 3<\/strong><\/a>
ISTQB Paper – 4<\/strong><\/a>
ISTQB Paper – 5<\/strong><\/a>
ISTQB Paper – 6<\/strong><\/a>
ISTQB Paper – 7<\/strong><\/a>
ISTQB paper – 8<\/strong><\/a>
ISTQB Paper – 9<\/strong><\/a><\/p>\n\n\n\n
2 – A
3 – D
4 – C
5 – A
6 – A
7 – C
8 – B
9 – C
10 – D
11 – A
12 – B
13 – A
14 – C
15 – B
16 – B
17 – D
18 – D
19 – B
20 – A
21 – D
22 – A
23 – B
24 – C
25 – D
26 – C
27 – C
28 – A
29 – C
30 – D
31 – C
32 – B
33 – C
34 – C
35 – B
36 – D
37 – C
38 – D
39 – D
40 – B<\/p>\n","protected":false},"excerpt":{"rendered":"