Chapter 1

Question 1    A company recently purchased a commercial off-the-shelf application to automate their bill-paying process. They now plan to run an acceptance test against the package prior to putting it into production. Which of the following is their most likely reason for testing?

1. To build confidence in the application.
2. To detect bugs in the application.
3. To gather evidence for a lawsuit.
4. To train the users.

Question 2    According to the ISTQB Glossary, the word ‘bug’ is synonymous with which of the following words?

1. Incident
2. Defect
3. Mistake
4. Error

Question 3    According to the ISTQB Glossary, a risk relates to which of the following?

1. Negative feedback to the tester.
2. Negative consequences that will occur.
3. Negative consequences that could occur.
4. Negative consequences for the test object.

Question 4    Ensuring that test design starts during the requirements definition phase is important to enable which of the following test objectives?

1. Preventing defects in the system.
2. Finding defects through dynamic testing.
3. Gaining confidence in the system.
4. Finishing the project on time.

Question 5    A test team consistently finds between 90% and 95% of the defects present in the system under test. While the test manager understands that this is a good defect-detection percentage for her test team and industry, senior management and executives remain disappointed in the test group, saying that the test team misses too many bugs. Given that the users are generally happy with the system and that the failures which have occurred have generally been low impact, which of the following testing principles is most likely to help the test manager explain to these managers and executives why some defects are likely to be missed?

1. Exhaustive testing is impossible
2. Defect clustering
3. Pesticide paradox
4. Absence-of-errors fallacy

Question 6    According to the ISTQB Glossary, regression testing is required for what purpose?

1. To verify the success of corrective actions.
2. To prevent a task from being incorrectly considered completed.
3. To ensure that defects have not been introduced by a modification.
4. To motivate better unit testing by the programmers.

Question 7    Which of the following is most important to promote and maintain good relation-

ships between testers and developers?

1. Understanding what managers value about testing.
2. Explaining test results in a neutral fashion.
3. Identifying potential customer workarounds for bugs.
4. Promoting better quality software whenever possible.

Question 8    Which of the statements below is the best assessment of how the test principles apply across the test life cycle?

1. Test principles only affect the preparation for testing.
2. Test principles only affect test execution activities.
3. Test principles affect the early test activities such as review.
4. Test principles affect activities throughout the test life cycle.

Chapter 2

Question 1    What are good practices for testing within the development life cycle?

1. Early test analysis and design.
2. Different test levels are defined with specific objectives.
3. Testers will start to get involved as soon as coding is done.
4. A and B above.

Question 2   Which option best describes objectives for test levels with a life cycle model?

1. Objectives should be generic for any test level.
2. Objectives are the same for each test level.
3. The objectives of a test level don’t need to be defined in advance.
4. Each level has objectives specific to that level.

Question 3    Which of the following is a test type?

1. Component testing
2. Functional testing
3. System testing
4. Acceptance testing

Question 4   Which of the following is a non-functional quality characteristic?

1. Feasibility
2. Usability
3. Maintenance
4. Regression

Question 5   Which of these is a functional test?

1. Measuring response time on an on-line booking system.
2. Checking the effect of high volumes of traffic in a call-center system.
3. Checking the on-line bookings screen information and the database contents against the information on the letter to the customers.
4. Checking how easy the system is to use.

Question 6   Which of the following is a true statement regarding the process of fixing emergency changes?

1. There is no time to test the change before it goes live, so only the best developers should do this work and should not involve testers as they slow down the process.
2. Just run the retest of the defect actually fixed.
3. Always run a full regression test of the whole system in case other parts of the system have been adversely affected.
4. Retest the changed area and then use risk assessment to decide on a reasonable subset of the whole regression test to run in case other parts of the system have been adversely affected.

Question 7   A regression test:

1. Is only run once.
2. Will always be automated.
3. Will check unchanged areas of the software to see if they have been affected.
4. Will check changed areas of the software to see if they have been affected.

Question 8   Non-functional testing includes:

1. Testing to see where the system does not function correctly.
2. Testing the quality attributes of the system including reliability and usability.
3. Gaining user approval for the system.
4. Testing a system feature using only the software required for that function.

Question 9   Beta testing is:

1. Performed by customers at their own site.
2. Performed by customers at the software developer’s site.
3. Performed by an independent test team.
4. Useful to test software developed for a specific customer or user.

Chapter 3

Question 1   Which of the following artifacts can be examined by using review techniques?

1. Software code
2. Requirements specification
3. Test designs
4. All of the above

Question 2   Which statement about the function of a static analysis tool is true?

1. Gives quality information about the code without executing it.
2. Checks expected results against actual results.
3. Can detect memory leaks.
4. Gives information about what code has and has not been exercised.

Question 3   Which is not a type of review?

1. Walkthrough
2. Inspection
3. Informal review
4. Management approval

Question 4   What statement about reviews is true?

1. Inspections are led by a trained moderator, whereas technical reviews are not necessarily.
2. Technical reviews are led by a trained leader, inspections are not.
3. In a walkthrough, the author does not attend.
4. Participants for a walkthrough always need to be thoroughly trained.

Question 5   What is the main difference between a walkthrough and an inspection?

1. An inspection is led by the authors, whilst a walk through is led by a trained moderator.
2. An inspection has a trained leader, whilst a walk through has no leader.
3. Authors are not present during inspections, whilst they are during walkthroughs.
4. A walkthrough is led by the author, whilst an inspection is led by a trained moderator.

Question 6   Which of the following characteristics and types of review processes belong together?

1. Led by the author
2. Undocumented
3. No management participation
4. Led by a trained moderator or leader
5. Uses entry and exit criteria
6. Inspection
7. Technical review
8. Informal review
9. Walkthrough
10. s = 4, t = 3, u = 2 and 5, v = 1
11. s = 4 and 5, t = 3, u = 2, v = 1
12. s = 1 and 5, t = 3, u = 2, v = 4
13. s = 5, t = 4, u = 3, v = 1 and 2

Question 7   What statement about static analysis is true?

1. With static analysis, defects can be found that are difficult to find with dynamic testing.
2. Compiling is not a form of static analysis.
3. When properly performed, static analysis makes functional testing redundant.
4. Static analysis finds all faults.

Question 8   Which of the following statements about early test design are true and which are false?

1. Defects found during early test design are more expensive to fix.
2. Early test design can find defects.
3. Early test design can cause changes to the requirements.
4. Early test design takes more effort.
5. 1 and 3 are true. 2 and 4 are false.
6. 2 is true. 1, 3 and 4 are false.
7. 2 and 3 are true. 1 and 4 are false.
8. 2, 3 and 4 are true. 1 is false.

Question 9   Static code analysis typically identifies all but one of the following problems. Which is it?

1. Unreachable code
2. Undeclared variables
3. Faults in the requirements
4. Too few comments

 

Chapter 4

Question 1    In which document described in IEEE 829 would you find instructions for the steps to be taken for a test including set-up, logging, environment and measurement?

1. Test plan
2. Test design specification
3. Test case specification
4. Test procedure specification

Question 2    With a highly experienced tester with a good business background, which approach to defining test procedures would be effective and most efficient for a project under severe time pressure?

1. A high-level outline of the test conditions and general steps to take.
2. Every step in the test spelled out in detail.
3. A high-level outline of the test conditions with the steps to take discussed in detail with another experienced tester.
4. Detailed documentation of all test cases and careful records of each step taken in the testing.

Question 3    Put the test cases that implement the following test conditions into the best order for the test execution schedule, for a test that is checking modifications of customers on a database.

1  Print modified customer record.

2  Change customer address: house number and street name.

3  Capture and print the on-screen error message.

4  Change customer address: postal code.

5  Confirm existing customer is on the database by opening that record.

6  Close the customer record and close the database.

7  Try to add a new customer with no details at all.

1. 5,4, 2,1, 3, 7, 6
2. 4,2,5,1,6,7,3
3. 5,4,2,1,7,3,6
4. 5,1, 2, 3,4, 7, 6

Question 4   Why are both specification-based and structure-based testing techniques useful?

1. They find different types of defect.
2. Using more techniques is always better.
3. Both find the same types of defect.
4. Because specifications tend to be unstructured.

Question 5   What is a key characteristic of structure-based testing techniques?

1. They are mainly used to assess the structure of a specification.
2. They are used both to measure coverage and to design tests to increase coverage.
3. They are based on the skills and experience of the tester.
4. They use a formal or informal model of the software or component.

Question 6   Which of the following would be an example of decision-table testing for a financial application applied at the system-test level?

1. A table containing rules for combinations of inputs to two fields on a screen.
2. A table containing rules for interfaces between components.
3. A table containing rules for mortgage applications.
4. A table containing rules for chess.

Question 7   Which of the following could be a coverage measure for state transition testing?

V All states have been reached.

W The response time for each transaction is adequate.

X Every transition has been exercised.

Y All boundaries have been exercised.

Z Specific sequences of transitions have been exercised.

1. X,YandZ
2. V, X, Y and Z
3. W,XandY
4. V, X and Z

Question 8 Postal rates for ‘light letters’ are 25p up to l0g, 35p up to 50g plus an extra l0p for each additional 25g up to l00g.

Which test inputs (in grams) would be selected using equivalence partitioning?

1. 8,42,82,102
2. 4,15, 65, 92,159
3. 10,50,75,100
4. 5, 20, 40, 60, 80

Question 9    Which of the following could be used to assess the coverage achieved for specification-

based (black-box) test techniques?

V Decision outcomes exercised

W Partitions exercised

X Boundaries exercised

Y State transitions exercised

Z Statements exercised

1. V,W,YorZ
2. W,XorY
3. V,XorZ
4. W, X, Y or Z

Question 10 Which of the following structure-based  test  design  technique  would  be  most likely to be applied to?

1  Boundaries between mortgage interest rate bands.

2  An invalid transition between two different arrears^ statuses.

3  The business process flow for mortgage approval.

4  Control flow of the program to calculate repayments.

1. 2, 3 and 4
2. 2 and 4
3. 3 and 4
4. 1, 2 and 3

Question 11    Use case testing is useful for which of the following?

P Designing acceptance tests with users or customers.

Q Making sure that the mainstream business processes are tested.

R Finding defects in the interaction between components.

S Identifying the maximum and minimum values for every input field.

T Identifying the percentage of statements exercised by a sets of tests.

1. P, Q and R
2. Q,SandT
3. P, Qand S
4. R, S and T

Question 12   Which of the following statements about the relationship between statement coverage and decision coverage is correct?

1. 100% decision coverage is achieved if statement coverage is greater than 90%.
2. 100% statement coverage is achieved if decision coverage is greater than 90%.
3. 100% decision coverage always means 100% statement coverage.
4. 100% statement coverage always means 100% decision coverage.

Question 13   If you are flying with an economy ticket, there is a possibility that you may get upgraded to business class, especially if you hold a gold card in the airline’s frequent flier program. If you don’t hold a gold card, there is a possibility that you will get ‘bumped’ off the flight if it is full and you check in late. This is shown in Figure 4.5.

Note that each box (i.e. statement) has been numbered. Three tests have been run:

Test 1: Gold card holder who gets upgraded to business class

Test 2: Non-gold card holder who stays in economy

Test 3: A person who is bumped from the flight

What is the statement coverage of these three tests?

1. 60%
2. 70%
3. 80%
4. 90%

 

Question 14   Why are error guessing and exploratory testing good to do?

1. They can find defects missed by specification- based and structure-based techniques.
2. They don’t require any training to be as effective as formal techniques.
3. They can be used most effectively when there are good specifications.
4. They will ensure that all of the code or system is tested.

Question 15   How do experience-based techniques differ from specification-based techniques?

1. They depend on the tester’s understanding of the way the system is structured rather than on a documented record of what the system should do.
2. They depend on having older testers rather than younger testers.
3. They depend on a documented record of what the system should do rather than on an individual’s personal view.
4. They depend on an individual’s personal view rather than on a documented record of what the system should do.

Question 16    When choosing which technique to use in a given situation, which factors should be taken into account?

U previous experience of types of defects found in this or similar systems

V the existing knowledge of the testers

W regulatory standards that apply

X the type of test execution tool that will be used

Y the documentation available

Z previous experience in the development language

1. V,W,YandZ
2. U, V, W and Y
3. U,XandY
4. V, W and Y

Question 17   Given the state diagram in Figure 4.6, which test case is the minimum series of valid transitions to cover every state?

1. SS-S1-S2-S4-S1-S3-ES
2. SS-S1-S2-S3-S4-ES
3. SS-S1-S2-S4-S1-S3-S4-S1-S3-ES
4. SS-S1-S4-S2-S1-S3-ES

Chapter 5

Question 1    Why is independent testing important?

1. Independent testing is usually cheaper than testing your own work.
2. Independent testing is more effective at finding defects.
3. Independent testers should determine the processes and methodologies used.
4. Independent testers are dispassionate about whether the project succeeds or fails.

Question 2    Which of the following is among the typical tasks of a test leader?

1. Develop system requirements, design specifications and usage models.
2. Handle all test automation duties.
3. Keep tests and test coverage hidden from programmers.
4. Gather and report test progress metrics.

Question 3    According to the ISTQB Glossary, what do we mean when we call someone a test manager?

1. A test manager manages a collection of test leaders.
2. A test manager is the leader of a test team or teams.
3. A test manager gets paid more than a test leader.
4. A test manager reports to a test leader.

Question 4   What is the primary difference between the test plan, the test design specification, and the test procedure specification?

1. The test plan describes one or more levels of testing, the test design specification identifies the associated high-level test cases and a test procedure specification describes the actions for executing a test.
2. The test plan is for managers, the test design specification is for programmers and the test procedure specification is for testers who are automating tests.
3. The test plan is the least thorough, the test procedure specification is the most thorough and the test design specification is midway between the two.
4. The test plan is finished in the first third of the project, the test design specification is finished in the middle third of the project and the test procedure specification is finished in the last third of the project.

Question 5   Which of the following factors is an influence on the test effort involved in most projects?

1. Geographical separation of tester and programmers.
2. The departure of the test manager during the project.
3. The quality of the information used to develop the tests.
4. Unexpected long-term illness by a member of the project team.

Question 6   The ISTQB Foundation Syllabus establishes a fundamental test process where test planning occurs early in the project, while test execution occurs at the end. Which of the following elements of the test plan, while specified during test planning, is assessed during test execution?

1. Test tasks
2. Environmental needs
3. Exit criteria
4. Test team training

Question 7    Consider the following exit criteria which might be found in a test plan:

I  No known customer-critical defects.

II  All interfaces between components tested.

III 100% code coverage of all units.

IV All specified requirements satisfied.

V System functionality matches legacy system for all business rules.

Which of the following statements is true about whether these exit criteria belong in an acceptance test plan?

1. All statements belong in an acceptance test plan.
2. Only statement I belongs in an acceptance test plan.
3. Only statements I, II, and V belong in an acceptance test plan.
4. Only statements I, IV, and V belong in an acceptance test plan.

Question 8    According to the ISTQB Glossary, what is a test level?

1. A group of test activities that are organized together.
2. One or more test design specification documents.
3. A test type.
4. An ISTQB certification.

Question 9    Which of the following metrics would be most useful to monitor during test execution?

1. Percentage of test cases written.
2. Number of test environments remaining to be configured.
3. Number of defects found and fixed.
4. Percentage of requirements for which a test has been written.

Question 10    During test execution, the test manager describes the following situation to the project team: ‘90% of the test cases have been run. 20% of the test cases have identified defects. 127 defects have been found. 112 defects have been fixed and have passed confirmation testing. Of the remaining 15 defects, project management has decided that they do not need to be fixed prior to release.’ Which of the following is the most reasonable interpretation of this test status report?

1. The remaining 15 defects should be confirmation tested prior to release.
2. The remaining 10% of test cases should be run prior to release.
3. The system is now ready for release with no further testing or development effort.
4. The programmers should focus their attention on fixing the remaining known defects prior to release.

Question 11    In a test summary report, the project’s test leader makes the following statement, ‘The payment processing subsystem fails to accept payments from American Express cardholders, which is considered a must-work feature for this release.’ This statement is likely to be found in which of the following sections?

1. Evaluation
2. Summary of activities
3. Variances
4. Incident description

Question 12    During an early period of test execution, a defect is located, resolved and confirmed as resolved by re-testing, but is seen again later during subsequent test execution. Which of the following is a testing-related aspect of configuration management that is most likely to have broken down?

1. Traceability
2. Confirmation testing
3. Configuration control
4. Test documentation management

Question 13    You are working as a tester on a project to develop a point-of-sales system for grocery stores and other similar retail outlets. Which of the following is a product risk for such a project?

1. The arrival of a more-reliable competing product on the market.
2. Delivery of an incomplete test release to the first cycle of system test.
3. An excessively high number of defect fixes fail during re-testing.
4. Failure to accept allowed credit cards.

Question 14    A product risk analysis meeting is held during the project planning period. Which of the following determines the level of risk?

1. Difficulty of fixing related problems in code
2. The harm that might result to the user
3. The price for which the software is sold
4. The technical staff in the meeting

Question 15   You are writing a test plan using the IEEE 829 template and are currently completing the Risks and Contingencies section. Which of the following is most likely to be listed as a project risk?

1. Unexpected illness of a key team member
2. Excessively slow transaction-processing time
3. Data corruption under network congestion
4. Failure to handle a key use case

Question 16    You and the project stakeholders develop a list of product risks and project risks during the planning stage of a project. What else should you do with those lists of risks during test planning?

1. Determine the extent of testing required for the product risks and the mitigation and contingency actions required for the project risks.
2. Obtain the resources needed to completely cover each product risk with tests and transfer responsibility for the project risks to the project manager.
3. Execute sufficient tests for the product risks, based on the likelihood and impact of each product risk and execute mitigation actions for all project risks.
4. No further risk management action is required at the test planning stage.

Question 17    According to the ISTQB Glossary, a product risk is related to which of the following?

1. Control of the test project
2. The test object
3. A single test item
4. A potential negative outcome

Question 18    In an incident report, the tester makes the following statement, At this point, I expect to receive an error message explaining the rejection of this invalid input and asking me to enter a valid input. Instead the system accepts the input, displays an hourglass for between one and five seconds and finally terminates abnormally, giving the message, “Unexpected data type: 15. Click to continue.” ‘ This statement is likely to be found in which of the following sections of an IEEE 829 standard incident report?

1. Summary
2. Impact
3. Item pass/fail criteria
4. Incident description

Question 19    According to the ISTQB Glossary, what do we call a document that describes any event that occurred during testing which requires further investigation?

1. A bug report
2. A defect report
3. An incident report
4. A test summary report

Question 20    A product risk analysis is performed during the planning stage of the test process. During the execution stage of the test process, the test manager directs the testers to classify each defect report by the known product risk it relates to (or to ‘other’). Once a week, the test manager runs a report that shows the percentage of defects related to each known product risk and to unknown risks. What is one possible use of such a report?

1. To identify new risks to system quality.
2. To locate defect clusters in product subsystems.
3. To check risk coverage by tests.
4. To measure exploratory testing.

Chapter 6

Question 1    Which tools help to support static testing?

1. Static analysis tools and test execution tools.
2. Review process support tools, static analysis tools and coverage measurement tools.
3. Dynamic analysis tools and modeling tools.
4. Review process support tools, static analysis tools and modeling tools.

Question 2    Which test activities are supported by test harness or unit test framework tools?

1. Test management and control.
2. Test specification and design.
3. Test execution and logging.
4. Performance and monitoring.

Question 3   What are the potential benefits from using tools in general to support testing?

1. Greater quality of code, reduction in the number of testers needed, better objectives for testing.
2. Greater repeatability of tests, reduction in repetitive work, objective assessment.
3. Greater responsiveness of users, reduction of tests run, objectives not necessary.
4. Greater quality of code, reduction in paperwork, fewer objections to the tests.

Question 4    What is a potential risk in using tools to support testing?

1. Unrealistic expectations, expecting the tool to do too much.
2. Insufficient reliance on the tool, i.e. still doing manual testing when a test execution tool has been purchased.
3. The tool may find defects that aren’t there.
4. The tool will repeat exactly the same thing it did the previous time.

Question 5    Which of the following are advanced scripting techniques for test execution tools?

1. Data-driven and keyword-driven
2. Data-driven and capture-driven
3. Capture-driven and keyhole-driven
4. Playback-driven and keyword-driven

Question 6    Which of the following would NOT be done as part of selecting a tool for an organization?

1. Assess organizational maturity, strengths and weaknesses.
2. Roll out the tool to as many users as possible within the organization.
3. Evaluate the tool features against clear requirements and objective criteria.
4. Identify internal requirements for coaching and mentoring in the use of the tool.

Question 7    Which of the following is a goal for a proof-of-concept or pilot phase for tool evaluation?

1. Decide which tool to acquire.
2. Decide on the main objectives and requirements for this type of tool.
3. Evaluate the tool vendor including training, support and commercial aspects.
4. Decide on standard ways of using, managing, storing and maintaining the tool and the test assets.

Ngoài ra bạn có thể download nhiều tài liệu hay khác về testing theo link sau: http://bit.ly/2r3szBD