Sample Questions ISTQB Foundation Answers

Similar documents
Sample Exam. Certified Tester Foundation Level

1 Visible deviation from the specification or expected behavior for end-user is called: a) an error b) a fault c) a failure d) a defect e) a mistake

Test design techniques

Examination Questions Time allowed: 1 hour 15 minutes

Sample Exam Syllabus

Standard Glossary of Terms used in Software Testing. Version 3.2. Foundation Extension - Usability Terms

Sample Exam. Advanced Test Automation Engineer

Certified Tester Foundation Level(CTFL)

Test Design Techniques ISTQB (International Software Testing Qualifications Board)

ASTQB Advance Test Analyst Sample Exam Answer Key and Rationale

ISTQB-ISEB Certified Tester Foundation Level

Certified Automotive Software Tester Sample Exam Paper Syllabus Version 2.0

Software Design Models, Tools & Processes. Lecture 6: Transition Phase Cecilia Mascolo

SOFTWARE TESTING FOUNDATION COURSE CURRICULUM

Software Testing Interview Question and Answer

Sample Exam ISTQB Advanced Test Analyst Answer Rationale. Prepared By

Expert Test Manager: Operational Module Course Outline

INTRODUCTION TO SOFTWARE ENGINEERING

Assignments. Assignment 2 is due TODAY, 11:59pm! Submit one per pair on Blackboard.

Software Engineering 2 A practical course in software engineering. Ekkart Kindler

Testing is the process of evaluating a system or its component(s) with the intent to find whether it satisfies the specified requirements or not.

Foundation Level Syllabus Usability Tester Sample Exam Answers

PASS4TEST. IT Certification Guaranteed, The Easy Way! We offer free update service for one year

Foundation Level Syllabus Usability Tester Sample Exam

Business Requirements Document (BRD) Template

Struggling to Integrate Selenium into Your Ice Age Test Management Tools?

Introduction to Software Testing

Shree.Datta Polytechnic College,Dattanagar, Shirol. Class Test- I

TESTING SOFTWARE QUALITY CHARACTERISTICS

ISTQB Advanced Level (CTAL)

Certified Tester. Foundation Level. Overview

2016 / 2017 Model-based Testing User Survey: Results

Usability Testing CS 4501 / 6501 Software Testing

Computer Science and Software Engineering University of Wisconsin - Platteville 9-Software Testing, Verification and Validation

Agile Testing: Your Key to Better Software

Software Quality Assurance. David Janzen

Software Testing Fundamentals. Software Testing Techniques. Information Flow in Testing. Testing Objectives

The Analysis and Proposed Modifications to ISO/IEC Software Engineering Software Quality Requirements and Evaluation Quality Requirements

Standard Glossary of Terms used in Software Testing. Version 3.2. Advanced Test Automation - Engineer Terms

Agile Tester Foundation E-learning Course Outline

Standard Glossary of Terms used in Software Testing. Version 3.2. Beta - Foundation Terms

People tell me that testing is

Advanced Tester Certification Test Manager

Agile Accessibility. Presenters: Ensuring accessibility throughout the Agile development process

Chapter 8. Achmad Benny Mutiara

Standard Glossary of Terms Used in Software Testing. Version 3.01

COURSE BROCHURE. ITIL - Intermediate Service Transition. Training & Certification

Quality Assurance = Testing? SOFTWARE QUALITY ASSURANCE. Meaning of Quality. How would you define software quality? Common Measures.

Software Requirements Specification. <Project> for. Version 1.0 approved. Prepared by <author(s)> <Organization> <Date created>

Software Testing. Software Testing

CSE 403: Software Engineering, Fall courses.cs.washington.edu/courses/cse403/16au/ Unit Testing. Emina Torlak

Basic Concepts of Reliability

Chapter 8 Software Testing. Chapter 8 Software testing

Certified Software Tester (CSTE) 123

Standard Glossary of Terms used in Software Testing. Version 3.1. Expert Test Manager Terms

Lecture 15 Software Testing

CTAL. ISTQB Advanced Level.

BECOME A LOAD TESTING ROCK STAR

Bridge Course On Software Testing

Testing Tools to Support Agile Software Delivery. The Critical Role of Automated Functional Testing in Enterprise Environments

SEGUE DISCOVERY PARTICIPATION IN DISCOVERY DISCOVERY DELIVERABLES. Discovery

CS 160: Evaluation. Outline. Outline. Iterative Design. Preparing for a User Test. User Test

Certified Tester. Expert Level. Modules Overview

Association for International PMOs. Expert. Practitioner. Foundation PMO. Learning.

Learn Well Technocraft

Black-box Testing Techniques

User Centered Design (UCD)

Introduction to Domain Testing

SERVICE TRANSITION ITIL INTERMEDIATE TRAINING & CERTIFICATION

Testware Architecture

Sample Question Paper. Software Testing (ETIT 414)

ASTQB TA12. ISTQB-BCS Certified Tester Advanced Level - Test Analyst.

UNIT-4 Black Box & White Box Testing

Verification and Validation. Assuring that a software system meets a user s needs. Verification vs Validation. The V & V Process

MTAT : Software Testing

Certified Software Quality Engineer Preparation On Demand, Web-Based Course Offered by The Westfall Team

UNIT-4 Black Box & White Box Testing

Microsoft Partner FAQ

UX Research in the Product Lifecycle

Lecture 20: SW Testing Presented by: Mohammad El-Ramly, PhD

How to develop a website content evaluation plan

10. Software Testing Fundamental Concepts

Software Quality Assurance & Testing

TMap Suite Test Engineer

CS 160: Evaluation. Professor John Canny Spring /15/2006 1

Software Development Methodologies

Association for International PMOs. Expert. Practitioner. Foundation PMO. Learning.

How to choose the right Data Governance resources. by First San Francisco Partners

COURSE BROCHURE. ITIL - Expert Managing Across Lifecycle Training & Certification

Standard Glossary of Terms Used in Software Testing. Version 3.01

Utilizing Fast Testing to Transform Java Development into an Agile, Quick Release, Low Risk Process

Introduction To Software Testing. Brian Nielsen. Center of Embedded Software Systems Aalborg University, Denmark CSS

Software Engineering (CSC 4350/6350) Rao Casturi

Software Testing. Software Testing. in the textbook. Chapter 8. Verification and Validation. Verification and Validation: Goals

Software Testing. Massimo Felici IF

Data and the Environment: Impacts on Cost and Success

Test Oracles. Test Oracle

CTFL -Automotive Software Tester Sample Exam Paper Syllabus Version 2.0

TEL2813/IS2820 Security Management

Concepts of Usability. Usability Testing. Usability concept ISO/IS What is context? What is context? What is usability? How to measure it?

Transcription:

Sample Questions ISTQB Foundation Answers Questions Prepared By Released January 2017

1 C C is correct. This is a defect that directly causes harm to the environment. A is not correct because the unhappy user is not actually harmed by the defect. B is not correct because the slow response time is not resulting in direct harm. D may be annoying but it s not causing harm. See also section 5.5.2. 2 C C is correct. Lessons learned from other projects, when used to improve processes, improves system quality future projects. A is not correct because rotations may be useful for other issues but minimally effective in preventing defects. B is not correct because the environmental conditions would either have to be fixed or the code would have to be fixed to handle the environment issues in order to reduce reoccurrence the same problems. D is not correct because a higher priority may get them fixed faster, but it won t help prevent their occurrence in the first place. See also section 1.1.4. 3 D D is correct. The goal acceptance testing is to build confidence that the stware meets the needs the stakeholders. Finding defects during this level testing is not a goal and should not happen if the previous levels testing have been completed successfully. See also section 2.2.4. 4 A A is correct. Identifying failures during testing can be perceived as criticism so the approach must be presented in a constructive manner. B is not correct because cooperation and a more democratic approach is usually needed. The tester is rarely in a position to make the final decision without input. C and D are not correct because these traits are irrelevant. 5 C C is correct. System integration testing is done when systems stware need to work together. System testing should be completed on each the systems prior to integrating them together and conducting system integration testing. 6 C C is correct. This occurs as the code is being developed. A is not correct because this is a technique that validates stware working with particular hardware and is usually performed by testers. B is not correct as this is performed by users that represent the business. D is not correct because this tests data conversion from one system to another and is usually performed by testers. 7 D D is correct. Maintainability testing is conducted to determine if the stware can be maintained by the FL-1.1.1 1 FL-1.1.2 1 FL-1.2.2 1 FL-1.5.2 1 FL-2.1.2 1 FL-2.2.1 1 FL-2.3.3 2 2

developers for updates, changes and modifications. Analyzability is a sub-characteristic maintainability. See also ISO 9126 for the stware quality characteristics, including maintainability. 8 D D is correct. A good set regression tests should require little or no maintenance and should be reusable across multiple releases. A is not correct because while the tests may test intricate aspects the stware that are difficult to test (particularly with automated regression tests) this is not the primary focus. B is not correct because the tests should not require much maintenance between releases so the reusability is high. C is not correct because re-usability is key. See section 2.3.4. 9 C C is correct. When a component stware that is in production is changed (modified, migrated, retired), maintenance testing is required. In this case something has been removed (maybe retired or just modified) so testing is required to make sure the remaining stware is unaffected. 10 A A is correct. Either manual reviews or automated analysis occur early in the lifecycle. B, C, & D all occur later, after development code. See also section 3.3. 11 C C is correct. A walkthrough is when the author is leading the review and walking the participants through the document that is being reviewed. A and B would both be led by a moderator. D normally doesn t have a leader and is more an informal discussion. 12 B B is correct. The purpose and structure the meeting should be communicated. A is not correct because it goes opposite to the objective the review which is to find, ideally, all the defects in the document. C is incorrect as this can promote a demotivating behavior if people don t want to point out defects in their coworker s documents. D is incorrect because the review should be limited to the right people, not everyone. 13 A A is correct. The expected results should be identified as the steps the test case (test procedure) are defined. B is not correct because it will be too easy to accept the result as the expected result, even though it might not be correct. C and D are not correct because this is too early to know exactly what a particular test case will do. 14 D D is correct. The decision table contains the triggering conditions, ten combinations true and false for all input conditions, and the resulting actions for each combination conditions. A is not correct because it focuses on the relationship between states and inputs, highlighting transitions that are invalid. B is not correct because inputs are divided into equivalence classes where the behavior each member a class is FL-2.3.6 1 FL-2.4.1 1 FL-3.1.2 1 FL-3.2.2 2 FL-3.2.3 2 FL-4.1.3 1 FL-4.3.2 1 3

expected to be the same as any other member that class. C is not correct because it covers both valid and invalid values at the boundaries equivalence classes. See section 4.3.3. 15 A A is correct. Use cases describe process flows based on the expected use the stware by the users. See section 4.3.5. 16 A A is correct. This is an application experience-based test design. B and D are not correct because these are not test design techniques. C is not correct because defect-based test design uses known and expected defects to focus the testing in specific areas. 17 B B is correct. Structure-based testing should be used and that will allow you to target amounts statement or decision coverage to be attained by the testing. None the others will target the code and allow you to work to a particular level coverage. 18 C C is correct. This is a typical task for a tester in an organization. A, B, and D are not correct as they are tasks typically performed by test leaders. 19 A A is correct. Test execution should be scheduled during the test planning stage the project. It may be refined during test analysis and design and even during test implementation. Once execution has started, priorities may be adjusted and the schedule may be lengthened or shortened but the general scheduling should occur during the planning stage. 20 C C is correct. Test planning includes a broad range scheduling, including test analysis and design activities. See section 5.2.2. 21 B B is correct. The test estimate should factor in that the developers are highly skilled and experienced because it would be expected to have higher quality stware coming from these developers. See section 5.2.4. 22 D D is correct. This approach can be based on metrics from previous projects or typical values. A and B are not correct because neither are an estimation approach. C is not correct because it uses estimates made by experts the system. See section 5.2.5. 23 D D is correct. Since the defects must be accepted by the business, only system testing would be applicable. The business wouldn t care about defects open within the levels testing, only at the point when testing is complete and the stware will be moving to the acceptance levels. See section 5.2.4. 24 B B is correct. Configuration management ensures version control, change mapping, and traceability. A is not correct although version control is ten a part a good configuration management system. C is not FL-4.3.3 1 FL-4.5.2 1 FL-4.6.1 1 FL-5.1.3 1 FL-5.2.4 1 FL-5.2.6 1 FL-5.2.7 1 FL-5.2.8 1 FL-5.2.9 1 FL-5.4.1 1 4

correct because it focuses on corrective action taken in a testing project. D is not correct because it summarizes what happened during testing. 25 C C is a project risk and could threaten the overall project s ability to achieve its objectives. A, B and D are all product risks. A is a product risk (potential to cause harm) but a product risk such as this could cause a project to fail if the problem is not detected. 26 B B is correct. Employing the right test technique can reduce risk and some test techniques are more thorough than others. A and C are not correct because both are different aspects testing, independent risk. D is not correct because the cause and ultimate responsibility failures does not deviate based on level risk. See section 5.5.2. 27 C C is correct. Urgency is ten used interchangeably with priority. A and D are not correct because those terms are also used interchangeably with each other. B is not correct because this may influence the priority, but it is not the same thing. 28 D D is correct. These tools store and manage defects and other anomalies. A is not correct because it is used for version management testware. B is not correct because it stores requirements and associated detail. C is not correct as it is not a valid tool. FL-5.5.1 1 FL-5.5.5 1 FL-5.6.1 1 FL-6.1.3 1 5