{"id":332,"date":"2023-09-09T12:07:37","date_gmt":"2023-09-09T12:07:37","guid":{"rendered":"https:\/\/softwaretestingstuff.com\/?p=332"},"modified":"2023-09-10T10:13:08","modified_gmt":"2023-09-10T10:13:08","slug":"istqb-sample-question-paper-8","status":"publish","type":"post","link":"https:\/\/www.softwaretestingstuff.com\/2008\/11\/istqb-sample-question-paper-8.html","title":{"rendered":"ISTQB Sample Question Paper – 8"},"content":{"rendered":"\n
Q1. Software testing activities should start<\/strong><\/p>\n\n\n\n a. as soon as the code is written Q2.Faults found by users are due to:<\/strong><\/p>\n\n\n\n a. Poor quality software Q3. What is the main reason for testing software before releasing it?<\/strong><\/p>\n\n\n\n a. to show that system will work after release Q4. which of the following statements is not true<\/strong><\/p>\n\n\n\n a. performance testing can be done during unit testing as well as during the testing of whole system Q5. When reporting faults found to developers, testers should be:<\/strong><\/p>\n\n\n\n a. as polite, constructive and helpful as possible Q6.In which order should tests be run?<\/strong><\/p>\n\n\n\n a. the most important tests first Q7. The later in the development life cycle a fault is discovered, the more expensive it is to fix. why?<\/strong><\/p>\n\n\n\n a. the documentation is poor, so it takes longer to find out what the software is doing. Q8. Which is not true-The black box tester<\/strong><\/p>\n\n\n\n a. should be able to understand a functional specification or requirements document Q9. A test design technique is<\/strong><\/p>\n\n\n\n a. a process for selecting test cases Q10. Testware (test cases, test dataset)<\/strong><\/p>\n\n\n\n a. needs configuration management just like requirements, design and code Q11. An incident logging system<\/strong><\/p>\n\n\n\n a. only records defects Q12. Increasing the quality of the software, by better development methods, will affect the time needed for testing (the test phases) by:<\/strong><\/p>\n\n\n\n a. reducing test time Q13. Coverage measurement<\/strong><\/p>\n\n\n\n a. is nothing to do with testing Q14. When should you stop testing?<\/strong><\/p>\n\n\n\n a. when time for testing has run out. Q15. Which of the following is true?<\/strong><\/p>\n\n\n\n a. Component testing should be black box, system testing should be white box. Q16. What is the important criterion in deciding what testing technique to use?<\/strong><\/p>\n\n\n\n a. how well you know a particular technique Q17. If the pseudocode below were a programming language, how many tests are required to achieve 100% statement coverage?<\/strong><\/p>\n\n\n\n 1. If x=3 then<\/strong> a. 1 Q18. Using the same code example as question 17,how many tests are required to achieve 100% branch \/ decision coverage?<\/strong><\/p>\n\n\n\n a. 1 Q19. Which of the following is NOT a type of non-functional test?<\/strong><\/p>\n\n\n\n a. State-Transition Q20. Which of the following tools would you use to detect a memory leak?<\/strong><\/p>\n\n\n\n a. State analysis Q21. Which of the following is NOT a standard related to testing?<\/strong><\/p>\n\n\n\n a. IEEE829 Q22.which of the following is the component test standard?<\/strong><\/p>\n\n\n\n a. IEEE 829 Q23. which of the following statements are true?<\/strong><\/p>\n\n\n\n a. Faults in program specifications are the most expensive to fix. Q24. Which of the following is not the integration strategy?<\/strong><\/p>\n\n\n\n a. Design based Q25. Which of the following is a black box design technique?<\/strong><\/p>\n\n\n\n a. statement testing Q26. A program with high cyclometic complexity is almost likely to be:<\/strong><\/p>\n\n\n\n a. Large Q27. Which of the following is a static test?<\/strong><\/p>\n\n\n\n a. code inspection Q28. Which of the following is the odd one out?<\/strong><\/p>\n\n\n\n a. white box Q29. A program validates a numeric field as follows:<\/strong><\/p>\n\n\n\n – values less than 10 are rejected which of the following input values cover all of the equivalence partitions?<\/strong><\/p>\n\n\n\n a. 10,11,21 Q30. Using the same specifications as question 29, which of the following covers the MOST boundary values?<\/strong><\/p>\n\n\n\n a. 9,10,11,22 Answers:<\/strong><\/p>\n\n\n\n 1 – D, 2 – B, 3 – D, 4 – C, 5 – D, 6 – A, 7 – C, 8 – B, 9 – A, 10 – A, Also See:<\/strong><\/p>\n\n\n\n Q1. Software testing activities should start a. as soon as the code is writtenb. during the design stagec. when the requirements have been formally documentedd. as soon as possible in the development life cycle Q2.Faults found by users are due to: a. Poor quality softwareb. Poor software and poor testingc. bad luckd. insufficient time for […]<\/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":[16],"tags":[],"table_tags":[],"class_list":["post-332","post","type-post","status-publish","format-standard","hentry","category-interview-questions"],"yoast_head":"\n
b. during the design stage
c. when the requirements have been formally documented
d. as soon as possible in the development life cycle<\/p>\n\n\n\n
b. Poor software and poor testing
c. bad luck
d. insufficient time for testing<\/p>\n\n\n\n
b. to decide when the software is of sufficient quality to release
c. to find as many bugs as possible before release
d. to give information for a risk based decision about release<\/p>\n\n\n\n
b. The acceptance test does not necessarily include a regression test
c. Verification activities should not involve testers
d. Test environments should be as similar to production environments as possible<\/p>\n\n\n\n
b. firm about insisting that a bug is not a \u201cfeature\u201d if it should be fixed
c. diplomatic, sensitive to the way they may react to criticism
d. All of the above<\/p>\n\n\n\n
b. the most difficult tests first
c. the easiest tests first
d. the order they are thought of<\/p>\n\n\n\n
b. wages are rising
c. the fault has been built into more documentation,code,tests, etc
d. none of the above<\/p>\n\n\n\n
b. should be able to understand the source code.
c. is highly motivated to find faults
d. is creative to find the system\u2019s weaknesses<\/p>\n\n\n\n
b. a process for determining expected outputs
c. a way to measure the quality of software
d. a way to measure in a test plan what has to be done<\/p>\n\n\n\n
b. should be newly constructed for each new version of the software
c. is needed only until the software is released into production or use
d. does not need to be documented and commented, as it does not form part of the releasedsoftware system<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
b. no change
c. increasing test time
d. can\u2019t say<\/p>\n\n\n\n
b. is a partial measure of test thoroughness
c. branch coverage should be mandatory for all software
d. can only be applied at unit or module testing, not at system testing<\/p>\n\n\n\n
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<\/p>\n\n\n\n
b. if u find a lot of bugs in testing, you should not be very confident about the quality of software
c. the fewer bugs you find,the better your testing was
d. the more tests you run, the more bugs you will find.<\/p>\n\n\n\n
b. the objective of the test
c. how appropriate the technique is for testing the application
d. whether there is a tool to support the technique<\/p>\n\n\n\n
2. Display_messageX;<\/strong>
3. If y=2 then<\/strong>
4. Display_messageY;<\/strong>
5. Else<\/strong>
6. Display_messageZ;<\/strong>
7. Else<\/strong>
8. Display_messageZ;<\/strong><\/p>\n\n\n\n
b. 2
c. 3
d. 4<\/p>\n\n\n\n
b. 2
c. 3
d. 4<\/p>\n\n\n\n
b. Usability
c. Performance
d. Security<\/p>\n\n\n\n
b. Coverage analysis
c. Dynamic analysis
d. Memory analysis<\/p>\n\n\n\n
b. IEEE610
c. BS7925-1
d. BS7925-2<\/p>\n\n\n\n
b. IEEE 610
c. BS7925-1
d. BS7925-2<\/p>\n\n\n\n
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.<\/p>\n\n\n\n
b. Big-bang
c. Bottom-up
d. Top-down<\/p>\n\n\n\n
b. equivalence partitioning
c. error- guessing
d. usability testing<\/p>\n\n\n\n
b. Small
c. Difficult to write
d. Difficult to test<\/p>\n\n\n\n
b. coverage analysis
c. usability assessment
d. installation test<\/p>\n\n\n\n
b. glass box
c. structural
d. functional<\/p>\n\n\n\n
– values between 10 and 21 are accepted
– values greater than or equal to 22 are rejected<\/p>\n\n\n\n
b. 3,20,21
c. 3,10,22
d. 10,21,22<\/p>\n\n\n\n
b. 9,10,21,22
c. 10,11,21,22
d. 10,11,20,21<\/p>\n\n\n\n
11 – C, 12 – A, 13 – B, 14 – C, 15 – B, 16 – B, 17 – C, 18 – C, 19 – A, 20 – C,
21 – B, 22 – D, 23 – C, 24 – A, 25 – B, 26 – D, 27 – A, 28 – D, 29 – C, 30 – B<\/p>\n\n\n\n\n