b) a fault
c) a failure
d) a defect
w) after the software has changed
x) as often as possible
y) when the environment has changed
z) when the project manager says
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 & z are false
b) test deliverables
c) test tasks
d) test specifications
b) when time has run out
c) when all faults have been fixed correctly
d) it depends on the risks for the system being tested
b) 9999, 50000, 100000
c) 10000, 50000, 99999
d) 10000, 99999, 100000
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 normally takes more effort
b) iii & iv are true; i, ii & v are false
c) i, iii, iv & v are true; ii is false
d) i & ii are true; iii, iv & v are false
b) testing quality attributes of the system including performance and usability
c) testing a system function using only the software required for that function
d) testing for functions that should not exist
b) status accounting of configuration items
c) identification of test versions
d) controlled library access
b) to ensure that the system interfaces to other systems and networks
c) to specify which modules to combine when, and how many at once
d) to specify how the software should be divided into modules
b) to ensure that the test case specification is complete
c) to set the criteria used in generating test inputs
d) to determine when to stop testing
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.
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
Read q
IF p+q > 100 THEN
Print “Large”
ENDIF
IF p > 50 THEN
Print “p Large”
ENDIF
b) 1 test for statement coverage, 2 for branch coverage
c) 1 test for statement coverage, 1 for branch coverage
d) 2 tests for statement coverage, 2 for branch coverage
ii. 100% branch coverage guarantees 100% statement coverage.
iii. 100% branch coverage guarantees 100% decision coverage.
iv. 100% decision coverage guarantees 100% branch coverage.
v. 100% statement coverage guarantees 100% decision coverage.
b) i & v are True; ii, iii & iv are False
c) ii & iii are True; i, iv & v are False
d) ii, iii & iv are True; i & v are False
b) testing that the components that comprise the system function together
c) testing the end to end functionality of the system as a whole
d) testing the system performs functions within specified response times
b) documentation
c) test cases
d) improvements suggested by users
b) test documentation
c) live data
d) user requirement documents
b) testing a released system that has been changed
c) testing by users to ensure that the system meets a business need
d) testing to maintain business advantage
b) unreachable (“dead”) code
c) memory leaks
d) array bound violations
b) LCSAJ
c) syntax testing
d) boundary value analysis
b) performed by customers at the software developer’s site
c) performed by an Independent Test Team
d) performed as early as possible in the lifecycle
ii. performance testing
iii. test management
iv. dynamic analysis
b) developers would typically use i and iii; test team ii and iv
c) developers would typically use ii and iv; test team i and iii
d) developers would typically use i, iii and iv; test team ii
b) ensuring that the system is acceptable to all users
c) testing the system with other systems
d) testing from a business perspective
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
b) inspections should be led by a trained leader
c) managers can perform inspections on management documents
d) inspection is appropriate even when there are no written documents
b) comparison of expected outcomes with actual outcomes
c) recording test inputs
d) reading test values from a data file
b) re-testing looks for unexpected side-effects; regression testing ensures the original fault has been removed
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
b) only used in component testing
c) most useful when specified in advance
d) derived from the code
b) inspection
c) management review
d) post project review
b) non-functional system testing
c) user acceptance testing
d) maintenance testing
b) analyzing metrics and improving processes
c) writing the documents to be inspected
d) time spent on the document outside the meeting
b) to prove that the software has no faults
c) to give confidence in the software
d) to find performance problems
2. undocumented
3. no management participation
4. led by a moderator or leader
5. uses entry and exit criteria
t) peer review
u) informal review
v) walkthrough
b) s = 4, t = 3, u = 2 and 5, v = 1
c) s = 1 and 5, t = 3, u = 2, v = 4
d) s = 4 and 5, t = 1, u= 2, v = 3
b) performance, load and stress testing
c) usability testing
d) top-down integration testing
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
b) BS 7925-1
c) ANSI/IEEE 829
d) ANSI/IEEE 729
b) increases the later a fault is found
c) decreases the later a fault is found
d) can never be determined
b) test environment properties
c) quality plans
d) schedules and deadlines
b) no, because they are normally applied before testing
c) yes, because both help detect faults and improve quality
d) yes, because testing includes all non-constructive activities
b) recovery testing
c) simulating many users
d) generating many transactions
b) as the first approach to deriving test cases
c) by inexperienced testers
d) after the system has gone live
1 C
2 C
3 D
4 D
5 C
6 A
7 B
8 A
9 C
10 D
11 B
12 B
13 D
14 C
15 D
16 C
17 B
18 C
19 B
20 A
21 A
22 D
23 A
24 D
25 A
26 A
27 C
28 B
29 D
30 C
31 B
32 A
33 D
34 A
35 B
36 B
37 C
38 C
39 B
40 A
6:24 AM
GAReddy
ISTQB Foundation Level Exam Sample Paper - II
ISTQB Foundation level exam Sample paper - II
Q1 A deviation from the specified or expected behavior that is visible to end-users is called:
a) an error
Q2 Regression testing should be performed:
v) every week
a) v & w are true, x, y & z are false
Q3 IEEE 829 test plan documentation standard contains all of the following except
a) test items
Q4 When should testing be stopped?
a) when all the planned tests have been run
Q5 Order numbers on a stock control system can range between 10000 and 99999 inclusive. Which of the following inputs might be a result of designing tests for only valid equivalence classes and valid boundaries?
a) 1000, 50000, 99999
Q6 Consider the following statements about early test design:
i. early test design can prevent fault multiplication
a) i, iii & iv are true; ii & v are false
Q7 Non-functional system testing includes:
a) testing to see where the system does not function correctly
Q8 Which of the following is NOT part of configuration management?
a) auditing conformance to ISO 9000
Q9 Which of the following is the main purpose of the integration strategy for integration testing in the small?
a) to ensure that all of the small modules are tested adequately
Q10 What is the purpose of a test completion criterion?
a) to know when a specific test has finished its execution
Q11 Consider the following statements:
i. an incident may be closed without being fixed.
a) ii is true, i, iii and iv are false
Q12 Given the following code, which statement is true about the minimum number of test cases required for full statement and branch coverage?
Read p
a) 1 test for statement coverage, 3 for branch coverage
Q13 Consider the following statements:
i. 100% statement coverage guarantees 100% branch coverage.
a) ii is True; i, iii, iv & v are False
Q14 Functional system testing is:
a) testing that the system functions with other systems
Q15 Incidents would not be raised against:
a) requirements
Q16 Which of the following items would not come under Configuration Management?
a) operating systems
Q17 Maintenance testing is:
a) updating tests when the software has changed
Q18 What can static analysis NOT find?
a) the use of a variable before it has been defined
Q19 Which of the following techniques is NOT a black box technique?
a) state transition testing
Q20 Beta testing is:
a) performed by customers at their own site
Q21 Given the following types of tool, which tools would typically be used by developers, and which by an independent system test team?
i. static analysis
a) developers would typically use i and iv; test team ii and iii
Q22 The main focus of acceptance testing is:
a) finding faults in the system
Q23 Which of the following statements about component testing is FALSE?
a) black box test design techniques all have an associated test measurement technique
Q24 Which of the following statements is NOT true?
a) inspection is the most formal review process
Q25 A typical commercial test execution tool would be able to perform all of the following, EXCEPT:
a) calculating expected outputs
Q26 The difference between re-testing and regression testing is:
a) re-testing ensures the original fault has been removed; regression testing looks for unexpected side-effects
Q27 Expected results are:
a) only important in system testing
Q28 What type of review requires formal entry and exit criteria, including metrics:
a) walkthrough
Q29 Which of the following uses Impact Analysis most?
a) component testing
Q30 What is NOT included in typical costs for an inspection process?
a) setting up forms and databases
Q31 Which of the following is NOT a reasonable test objective:
a) to find faults in the software
Q32 Which expression best matches the following characteristics of the review processes:
1. led by the author
s) inspection
a) s = 4 and 5, t = 3, u = 2, v = 1
Q33 Which of the following is NOT part of system testing?
a) business process-based testing
Q34 Which statement about expected outcomes is FALSE?
a) expected outcomes are defined by the software’s behaviour
Q35 The standard that gives definitions of testing terms is:
a) ISO/IEC 12207
Q36 The cost of fixing a fault:
a) is not important
Q37 Which of the following is NOT included in the Test Plan document of the Test Documentation Standard?
a) what is not to be tested
Q38 Could reviews or inspections be considered part of testing?
a) no, because they apply to development documentation
Q39 Which of the following is not part of performance testing?
a) measuring response times
Q40 Error guessing is best used:
a) after more formal techniques have been applied
Answers to all above questions:
Question Answer
GAReddy @ OneTestingCenter @ All Articles
- Ad-hoc Testing
- Automation Framework
- Basics of QTP
- Core Testing FAQs
- Download QTP - Preseenations
- Framework Guide
- Introduction to Testing
- ISTQB Foundation Level Exam Papers
- ISTQB Foundation Level Exam Sample Paper - I
- ISTQB Foundation Level Exam Sample Paper - II
- ISTQB Foundation Level Exam Sample Paper - III
- Keyword Driven Framework
- Keyword Driven Framework Complete Guide
- Keyword Framework Complete Guide
- Load
- Load Runner - Components
- Load Runner - Load Testing Process
- Load Testing - LoadRunner Correlation
- Load Testing Process
- Monkey Testing and Exploratory Testing
- Most Relevant Features and Benefits
- OneTestingCenter - Manual Testing - Learning Table
- Performance
- Performance Test - Short Notes
- Practical Guide to Keyword Driven Framework
- Programming Language / Scripting language / Markup languages / Operating Systems
- QTP QTP Learning Let's Learn QTP QTP Easy Learning QTP Guide QTP Book QTP Learning PDF QTP - Fundamentals QTP - Advanced QTP - Topic by Topic QTP Lessons GAReddy - QTP
- QTP - ActionDriven Framework Demo1
- QTP - Actions
- QTP - Application Relationship - Video
- QTP - Array Library Functions
- QTP - Automation Startup - Video
- QTP - Certification Q's1
- QTP - Certification Q's2
- QTP - Certification Q's3
- QTP - Data Tables
- QTP - DataTables - Video
- QTP - Descriptive Programing - Dynamic Object Repository Creation
- QTP - Descriptive Programming
- QTP - Descriptive Programming - Any Web App - Working with all Objects
- QTP - Descriptive Programming - Any Web App - Working with Web List-boxes
- QTP - Descriptive Programming - Broken Link Checking
- QTP - Descriptive Programming - Working with Any Web App
- QTP - Dictionary Object - Creating a Dictionary Object
- QTP - Dictionary Object - Add Method
- QTP - Dictionary Object - Items
- QTP - Dictionary Object - KeyExists
- QTP - Dictionary Object - Keys
- QTP - Dictionary Object - Remove Method
- QTP - Dictionary Object - RemoveAll Method
- QTP - Dictionary Object - Using Dictionary Values As Variables
- QTP - Environment Variables
- QTP - Excel - Excel Comparison
- QTP - Excel Comparision
- QTP - Files - Files Comparison
- QTP - Files Comparision
- QTP - Files Comparison
- QTP - FSO (PART A)
- QTP - FSO (PART B)
- QTP - Getting Object Properties Dynamically
- QTP - GetTOProperties / GetTOProperty / SetTOProperty Demo
- QTP - GetTOProperties Script Demo
- QTP - GetTOProperty Script Demo
- QTP - InputBox
- QTP - Keyword Driven Automation Framework - Video
- QTP - Keyword Driven Framework - Complete Guide
- QTP - Keyword Driven Framework - Complete Guide - Video
- QTP - Keyword Driven Framework - Step by Step Guide
- QTP - Microsoft Office - Word
- QTP - MsgBox
- QTP - Objects Classifications
- QTP - Overview
- QTP - Pass ByRef and Pass ByVal
- QTP - PDFs
- QTP - Recording Modes
- QTP - Recovery Scenario Manager
- QTP - Regular Expressions - Complete Reference
- QTP - Regular Expressions - Scripts
- QTP - Reporter Utility
- QTP - Reporter Utility - Scripts
- QTP - SetTOProperty Script Demo
- QTP - Synchronization
- QTP - Synchronization - Script Demo
- QTP - Synchronization Methods
- QTP - Synchronization Script
- QTP - Test / Action Template
- QTP - VBScript - Array Sorting
- QTP - VBScript - Dictionary Object
- QTP - VBScript and Data Types
- QTP - VBScript Functions - One Reference
- QTP - Videos
- QTP - Ways to synchronize
- QTP – Descriptive Programing – Any Web App - Working with Web Check Boxes
- QTP – Descriptive Programing – Examples
- QTP – Outlook Application
- QTP – Regular Expressions
- QTP – Web Tables
- QTP 10 Supports Windows 7 and IE8
- QTP Basics
- QTP Boks
- QTP Books
- QTP Complete Learning Table
- QTP Easy Learning
- QTP for Beginners
- QTP Info
- QTP Introduction
- QTP Learning
- QTP Learning MadeEasy. QTP QTP Learning Let's Learn QTP QTP Easy Learning QTP Guide QTP Book QTP Learning PDF QTP - Fundamentals QTP - Advanced QTP - Topic by Topic QTP Lessons GAReddy - QTP
- QTP Learning Materials
- QTP Simple
- QTP Videos
- Requirements Flow
- Roles and Responsibilities of Testers
- Software Testing - Core Testing Definitions
- Software Testing - FAQs
- Software Testing - Testing Methodologies
- Software Testing - Testing Process
- Software Testing Glossary : QA - Testing All in One
- Software Testing Process
- Stress Testing Requirements
- Stress testings
- Stress Testings - Why
- Test Case - Test Case Design Techniques
- Test Case - What is Test Case
- Test Case - What should a Test Case contain
- Test Case Designing Techniques
- Testing - Daily Status Report
- Testing - Defect - Defect Documenting
- Testing - Defect - Defect Life Cycle
- Testing - Defect - What is a Bug (Defect)
- Testing - Defect – Metrics
- Testing - Defect – Priority Levels
- Testing - Defect – Severity Levels
- Testing - Important FAQs
- Testing - Load Testing - Performance Testing - Stress Testing
- Testing - Requirements Flow
- Testing - UAT - Alpha Testing and Beta Testing
- Testing - Verification and Validation
- Testing Definitions
- Testing Methodologies
- Testing Terminologies
- VB Script Features
- What is Testing?
- When does the Testing begin?
- When does the Testing end?
- Why do we need Testing?
- Why does software have bugs?
0 comments:
Post a Comment