Chapter one Chapter one.
Software that doesn't work correctly might lead to many problems including injury or death. True False.
Software testing increases the software quality. True False.
Software testing is a set of activities to discover defects and evaluate the quality of software artifacts. True False.
Test objects are the items that under testing process. True False.
Software Testing is all about executing tests without any other activities. True False.
Verification is: Building the right product Building the product right.
validation is: Checking whether the system meets specified requirements Checking whether the system meets users and stakeholders needs in it's operational environment.
Static Testing: Involves the execution of the software Uses the different types of test techniques and approaches to derive test cases It is a testing that we enter inputs in and wait for outputs All of the above None of the above.
It is a testing that doesn't involve execution of the software and it includes reviews and a type of analysis. Dynamic testing Static testing.
Black-box and White-Box techniques are types of: Dynamic testing Static testing.
Testing is only a technical activity. True False.
Testing needs to be properly: Planned and managed Estimated Monitored and controlled All of the above.
Testing is : Technical activity Intellectual activity Requires the tester to have specialized knowledge and analytical skills Requires the tester to apply critical thinking and system thinking All of the above.
It is a holistic approach to analysis that focuses on the way that a system's constituent parts interrelate and how systems work over time and within the context of larger systems. System thinking Design thinking.
A test level that focuses on determining whether to accept the system. Acceptance criteria Acceptance testing Acceptance test -driven development.
Confirmation by examination that a work product matches a stakeholder's needs. Verification Validation Actual results.
Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled. Verification Validation Actual results.
Defines the who, what and why of a product feature. Use case Test case Test suit User story.
Increasing the level of risk of inadequate software quality is one of the Test Objectives. True False.
Providing information to stakeholders to allow them to make informed decisions is one of the Test Objectives. True False.
Which of these are from the typical test objectives: Building confidence in the quality of the test object Validation whether the test object is complete and works as expected by the stakeholders Verifying that a test object compiles with contractual, legal and regulatory requirements All of the above.
Debugging can trigger failures that are caused by defects in the software (dynamic testing) or can directly find defects in the test object (static testing). True False.
Testing is concerned with finding causes of this failure (defects), analyzing these causes, and eliminating them. True False.
A type of testing that checks whether the fixes resolved the problem and it is preferably done by the same person who performed the initial test. Regression testing Confirmation testing Static testing.
A type of testing that is performed to check whether the fixes are causing failures in other parts of the test object. Regression testing Confirmation testing.
Any stakeholder can use their testing skills to help bringing the project closer to success. True False.
Testing’s contribution to success should be restricted to the test team activities. True False.
Testing ........ contributes to higher quality test objects. Directly Indirectly.
Testing provides a ......... means of detecting defects. Quality effective Cost effective Time effective.
Debugging is a: Testing activity Non-Testing activity.
Testing provides a means of ........ evaluating the quality of a test object at various stages in the SDLC. Directly In deirectly.
Testing provides users with ........ representation on the development project. Directly In deirectly.
Testing is a form of: Quality assurance (QA) Quality Control (QC).
It is a product-oriented, corrective approach that focuses on those activities supporting the achievement of appropriate levels of quality. Quality assurance (QA) Quality Control (QC).
Quality Assurance is: a product oriented corrective approach that focuses on those activities supporting the achievement of the appropriate levels of quality a process oriented preventive approach that focuses on the implementation and improvement of processes.
It is a preventive approach: Quality assurance (QA) Quality Control (QC).
Test results are used by Quality control to: Fix defects Provide feedback on how well the development and test processes are performing.
Human beings make errors (mistakes), which produce defects (faults, bugs), which in turn must result in failures. True False.
Defects can be found in: Documentations Source code Supporting artifact All of the above None of the above.
Some defects will always result in a failure if executed, while others will only result in a failure in specific circumstances, and some may never result in a failure. True False.
The causes of failures include: Errors Defects Environmental conditions A & B All of the above.
It is a fundamental reason for the occurrence of a problem. Error Failure Bug Root cause.
Testing can show that defects are present in the test object and also can prove that there are no defects. True False.
Testing reduces the probability of defects remaining undiscovered in the test object. True False.
If no defects are found, testing can prove test object correctness. True False.
Testing everything is not feasible even in trivial cases. True False.
Defects that are removed early in the process will cause subsequent defects in derived work products. True False.
To find defects early, ........... should be started as early as possible. Static testing Dynamic testing Answer is A & B.
Dynamic testing can be started as early as: Writing requirments After the first code has been written.
Pareto principle illustrates that: A small number of system components usually contain most of the defects discovered or are responsible for most of the operational failures 20% of system components usually contain little of the defects discovered 80% of system components usually contain most of the defects discovered.
............ observed during testing or in operation, are an important input for risk-based testing. Predicted defect clusters Actual defect cluster All of the above.
If the same tests are repeated many times, they become increasingly effective in detecting new defects. True False.
In some cases, repeating the same tests can have a beneficial outcome. an example of that is: Exhaustive testing Automated regression testing None of the above All of the above.
Testing is Context Dependent means that: There is no single universally applicable approach to testing. Testing is done differently in different contexts True False.
Software verification only will ensure the success of a system. True False.
To ensure the success of a system we have to perform: Verfication Validation All of the above.
There are common sets of test activities without which testing is less likely to achieve test objectives. These sets of test activities form a .............. Test planning Test process Test monitoring and control.
It ensures that all requirements are covered by test cases, and that all test cases are traceable back to the requirements. Test control Test analysis Traceability between the test basis and test work products.
Test Activities and Tasks are often implemented: Iteratively In parallel Answer A & B.
A test process usually consists of the main groups of activities described below, except: Test planning and monitoring and control Test analysis and test design Exhaustive testing & risk based testing Test implementation, test execution & test completion.
Test planning is usually a responsibility of: Tester Test analyst Test manager None of the above.
Test planning: Involves taking the actions necessary to meet the objectives of testing Consists of defining the test object and then selecting an approach that best achieves the objectives Includes elaborating the test conditions into test cases.
Involves the ongoing checking of all test activities and the comparison of actual progress against the plan. Test monitoring Test control.
Test control involves taking the actions necessary to meet the objectives of testing. True False.
Test analysis: Analyze the test basis to identify testable features Prioritize associated test conditions together with the related risks All of the above.
Test analysis is often supported by the use of: Test design Test techniques Project constraints.
Test analysis answers the question of: How to test What to test Why to test.
Which of these activities can be supported by using Test techniques ? Test design Test analysis Answer is A & B.
Test design answers the question of : How to test What to test Why to test.
Test implementation includes creating or acquiring the testware necessary for ............. Test completion Test execution Test design.
Test cases can be organized into test suites and are often assembled into test procedures. True False.
Test procedures are prioritized and arranged within a ................... for efficient test execution. Test implementation schedule Test execution schedule Test analysis schedule.
Test execution must be started manually then it can be automated. True False.
Continuous testing & Pair testing sessions are forms of: Test planning Test design Test execution.
Test completion activities usually occur at ........... for any unresolved defects. Release End of iteration Test level completion All of the above.
A report that is created after test completion. Test report Summary Test completion report None of the above.
Testing final goal is to help fulfill the stakeholders’ business needs. True False.
The way the testing is carried out depends on a number of contextual factors including: Stakeholders needs and expectations Team members skills and knowledge Organizational structure and existing policies All of the above.
It is created as output work products from the test activities. Test development Testware Test principles.
Test planning work products include: Test procedures, automated test scripts, test suits, test data, test execution schedule and test environment elements Test plan, test schedule, risk register and enty & exit criteria Test logs and defect reports.
In Agile: It is the definition of done. Entry criteria Exit criteria.
Unit testing exit criteria can be used as ......... for integration testing Entry criteria Exit criteria.
Test monitoring and control work products include: Test charters Test progress report Test logs.
Risk information and test environment elements are test monitoring and control work products. True False.
Test analysis work products include: Acceptance criteria Defect reports regarding defects in the test basis (if not fixed directly) All of the above.
Test design work products include: Prioritized test cases, test charters, coverage items, test data requirements and test environment requirements Test plan, test schedule, risk register and enty & exit criteria.
Test schedule is a work product of: Test design Test execution Test planning.
Test procedures are example of ...............work products. Test implementation Test analysis Test planning.
Test environment elements include: Stubs Drivers Simulators and virtualizations All of the above.
acts as a small piece of code that replaces another component during testing. Stubs Drivers Simulators.
All of them are test implementation work products except. Automated test scripts Test suits Test data Test progress report.
Test logs and defect reports are: Test completion work products Test execution work products Test monitoring and control work products.
Test completion report is : Test completion work products Test execution work products Test monitoring and control work products.
In order to implement effective test monitoring and control, it is important to establish
and maintain ......... throughout the test process between the test basis elements, testware associated with these elements, test results and detected defects. Accessability Traceability Productivity.
Traceability of test cases to requirements can: be used to evaluate the level of residual risk in a test object verify that requirements are covered by test cases.
A role that takes overall responsibility for the test process, test team and leadership of the test activities. The testing role The test management role.
The test management role is mainly focused on the activities of test analysis, test design, test implementation and test execution. True False.
It is possible for one person to take on the roles of testing and test management at the same time. True False.
The following skills are particularly relevant for testers: Testing knowledge Thoroughness, carefulness, curiosity and attention detatils Technical knowledge All of the above.
Domain knowledge isn't a skill that particularly relevant for testers. True False.
Communicating test results may be perceived as criticism of the product and of its author. True False.
In the whole-team approach any team member with the necessary knowledge and skills can perform any task, and everyone is responsible for quality. True False.
Which of these are true about the whole team approach. Improves team dynamics Enhance communication and collaboration within the team creates synergy by allowing the various skill set with the team to be leveraged for benefit of the project All of the above.
Give a reason: certain degree of independence makes the tester more effective at finding defects. Similarities between the author's and the tester's cognitive biases Differences between the author's and the tester's cognitive biases.
Work products can be tested by Their author (No independence) By the author's peers from the same team (Some independence) By testers from outside the author's team but within the organization (high independence) Testers from outside the organization (Very high independence) All of the above.
For most projects, it is usually not the best to carry out testing with multiple levels of independence. True False.
Independent testers may be isolated from the development team, which may lead to a lack of collaboration and communication problems. True False.
Chapter Two Chapter Two.
Examples of sequential development models: Spiral model & prototyping model Unified process Waterfall & V model.
It is an abstract, high-level representation of the software development process. Testing process Software development life cycle Software development process.
The SDLC model defines how different development phases and types of activities performed within this process relate to each other, both logically but not chronologically. True False.
Examples of iterative development models: Spiral model & prototyping model Unified process Incremental development models.
Waterfall is a sequential model that applies early testing. True False.
In V-model testing is not included in the development process. True False.
In V-model, if we have the requirements we can start planning, design, analysis and execute tests. True False.
V- model is: An iterative development model A sequential development model .
Spiral model is an: Iterative model Incremental model.
It's diagrammatic representation with many loops. The exact number of loops is unknown and can vary from project to project. V model Spiral model Waterfall model.
An example of Incremental development models. Unified process Prototyping model Waterfall model.
Test cases for each functionality are created and tested first and if the test fails then the new code is written in order to pass the test and making code simple and bug-free. Feature driven development (FDD) Test driven development (TDD) Domain driven development (DDD).
Scenario: User forgets their password
Given the user is on a page with the login fields
And the user has entered the username “test1”
When he clicks the “Forgot password” link
Then the user is taken to the reset password page
This is a: Behavior driven development (BDD) Acceptance test driven development (ATDD) Domain driven development (DDD).
Involves team members with different perspectives (customer, development, testing) collaborating to write acceptance tests in advance of implementing the corresponding functionality. Feature driven development (FDD) Test driven development (TDD) Acceptance test driven development (ATDD).
a model that encapsulate complex business logic, closing the gap between business reality and code. Kanban Feature driven development (FDD) Domain driven development (DDD).
a way to get work done as a team in small pieces (sprints) at a time. Kanban Scrum Lean it.
The choice of the SDLC impacts on the: Scope and timing of test activities Level of detail of test documentation Extent of test automation All of the above.
Dynamic testing can't be performed early in the SDLC. True False.
In some iterative and incremental development models, both static and dynamic testing may be performed at all test levels. True False.
For every software development activity, there is a corresponding test activity. True False.
The reason that test analysis and design for a given test level begins during the corresponding development phase of the SDLC is: So that all development activities are subject to quality control So that testing can adhere to the principle of early testing Allows for testing to be appropriately comprehensive while avoiding redundancy.
Tests are written first, then the code is written to satisfy the tests, and then the tests and code are refactored Behavior driven development (BDD) Test driven development (TDD) Acceptance test driven development (ATDD).
Derives tests from acceptance criteria as part of the system design process. Behavior driven development (BDD) Test driven development (TDD) Acceptance test driven development (ATDD).
Usually using the Given/When/Then format. Behavior driven development (BDD) Test driven development (TDD) Acceptance test driven development (ATDD).
It is an organizational approach aiming to create synergy by getting development and operations to work together to achieve a set of common goals. Quality control Quality assuerance DevOps.
DevOps promotes: Continuous integration (CI) Continuous delivery (CD) All of the above.
DevOps risks and challenges include: Test automation requires additional resources and may be difficult to establish and maintain Increases the view on non functional quality characteristics The risk in regression is minimized.
The principle of early testing is sometimes referred to as shift-left. True False.
Shift-left normally suggests that testing later in the SDLC should be neglected. True False.
A shift-left approach might result in extra training, effort and/or costs earlier in the process. True False.
Retrospectives are often held at the end of a project but not at the end of an iteration. True False.
Retrospective benefits for testing include: Increased test effectiveness / efficiency Increased quality of testware Improve quality of the test basis All of the above.
They are groups of test activities that are organized and managed together. Test suties Test cases Test levels Test types.
In some iterative, models the test levels are often defined such that the exit criteria of one level are part of the entry criteria for the next level. True False.
They are groups of test activities related to specific quality characteristics and most of those test activities can be performed at every test level. Test suties Test cases Test levels Test types.
unit testing is also known as: Component integration testing System testing Component testing.
a test level that focuses on testing the interfaces and interactions between components. Component integration testing System testing Component testing Answer is A & B.
a test level that focuses on testing the interfaces and interactions between components. Component integration testing System integration testing Acceptance testing.
System testing. Focuses on the overall behavior and capabilities of an entire system or product Often including functional testing end to end tasks Often including non functional testing of quality characteristics All of the above.
System testing can't be performed by an independent test team, and is related to specifications for the system. True False.
a test level that focuses on testing the interfaces of the system under test and other systems and external services . Functional testing System integration testing Acceptance testing.
System integration testing doesn't require suitable test environments similar to the operational environment. True False.
a test level that focuses on validation and on demonstrating readiness for deployment. White box testing System integration testing Acceptance testing.
which of these is not one of the main forms of acceptance testing: Alpha testing & beta testing Contractual and regulatory acceptance testing Operational acceptance testing User acceptance testing (UAT) Non of the above.
They are “what” the test object should do. Usability Functions Debugging.
Functional testing is the testing of “how well the system behaves”. True False.
• Performance efficiency • Compatibility • Usability • Reliability • Security • Maintainability • Portability • are:
Functional software quality characteristics Non functional software quality characteristics All of the above Non of the above.
The main objective of functional testing is checking the functional completeness, functional correctness but not functional appropriateness. True False.
It is specification-based test type. Black box testing White box testing Functional testing.
White-box testing is: Structure based testing Derives tests from the system's implementation or internal structure Derives tests from documentations external to the test object Answer is A & B Answer is A & C.
The main objective of black-box testing: is to cover the underlying structure by the tests to the acceptable level is checking the system's behavior against it's specifications is checking the functional completeness, functional correctness and functional appropriateness is checking the non functional software quality characteristics .
Confirmation testing: Confirms that no adverse consequences have been caused by a change Confirms that an original defect has been successfully fixed.
Regression testing confirms that no adverse consequences have been caused by a change, this doesn't include a fix that has already been confirmation tested. True False.
Regression testing is restricted to the test object itself and it can't be related to the environment. True False.
It is advisable first to perform an impact analysis to optimize the extent of the regression testing. Before regression testing After regression testing.
Regression testing is a strong candidate for automation. True False.
Maintenance is always corrective it can't be adaptive or to improve performance. True False.
What is (hot fixes)? Unplanned releases / deployments Planned releases / deployments.
The scope of maintenance testing typically depends on: The degree of risk of the change The size of the existing system The size of the change All of the above None of the above.
Retirement, such as when an application reaches the end of its life is a trigger for maintenance and maintenance testing. True False.
Chapter Three Chapter Three.
Static testing can be applied for verification but not validation. True False.
Spelling checkers and readability tools are examples of static analysis tools. True False.
Almost any work product can be examined using static testing. True False.
Work products that are not appropriate for static testing includes: Product backlog item Project documentation 3rd party executable code due to legal ressons Work products those that are difficult to interpret by human begins and that should not be analyzed by a tool Answer C & D.
Static testing can fulfill the principle of early testing. True False.
Static testing can identify defects which cannot be detected by dynamic testing. True False.
Defects in non-executable work products can be identified by: Static testing Dynamic testing.
It is recommended to involve a wide variety of stakeholders in static testing. True False.
Code defects can be detected using dynamic analysis more efficiently than in stating testing. True False.
There are some defect types that can only be found by static testing. True False.
Dynamic testing finds defects directly, while Static testing causes failures from which the associated defects are determined through subsequent analysis True False.
Dynamic testing can be applied to non-executable work products. True False.
Maintainability can be measured by: Static testing Dynamic testing.
Buffer overflows are easier and/or cheaper to be found through static testing. True False.
If there is little stakeholder involvement during the SDLC, the product being developed will meet the stakeholder’s vision every time. True False.
In this review process activity, the goal is to make sure that everyone and everything involved is prepared to start the review. Planning Individual review Review initiation.
Every reviewer performs an individual review to: Access the quality of the work product Identify anomalies Identify recommendations and questions All of the above.
checklist-based reviewing & scenario-based reviewing are: Review techniquies Review standards Reporting techniques.
The person who creates and fixes the work product under review: Reviewer Manager Author.
The person who takes overall responsibility for the review such as deciding who will be involved, and organizing when and where the review will take place Review leader Manager Moderator.
The person who ensures the effective running of review meetings, including mediation, time management, and a safe review environment in which everyone can speak freely: Review leader Facilitator Scribe.
a review type that do not follow a defined process and do not require a formal documented output. The main objective is detecting anomalies. Walkthrough Inspection Informal review.
It the most formal type of review, it follows the complete generic process. The main objective is to find the maximum number of anomalies. Walkthrough Inspection Technical review.
Reviews should be conducted on large chunks. True False.
Chapter Four Chapter Four.
Test analysis summarizes: How to test What to test Why to test.
Test techniques support the tester in: Test analysis Test design Identify test coverage All of the above.
Test techniques that also known as specification-based techniques: Experience based test techniques Black box test techniques White box test techniques.
The test cases in this technique are independent of how the software is implemented. Experience based test techniques Black box test techniques White box test techniques.
White-box test techniques are: Test cases are dependent on how the software is designed Test cases can only be created after the design or implementation of the test object Also known as structure based techniques All of the above.
Experience-based test techniques can detect defects that may be missed using the black box and white-box test techniques. True False.
which of these is not a black-box test techniques: Equivalence partitioning Boundary value analysis State transition testing Decision chart testing.
Equivalence partitions can be identified for which of these data element ? Inputs and outputs Internal values & time related values Interfaces prameters All of the above.
The partitions must overlap and must be empty sets. True False.
Coverage is measured as the total number of identified partitions divided by the number of partitions exercised by at least one test case. True False.
The simplest coverage criterion in the case of multiple sets of partitions is called: Simple choice coverage Each choice coverage Single choice coverage.
Each Choice coverage does not take into account combinations of partitions. True False.
BVA can only be used for ordered partitions. True False.
In 2-value BVA, Coverage is measured as the total number of identified boundary values divided by the number of boundary values that were exercised. True False.
In 3-value BVA for each boundary value there are two or three coverage items. True False.
3-value BVA is more rigorous than 2-value BVA. True False.
When creating decision tables, conditions and the resulting actions of the system form the ….. of the table. Rows Columns.
When creating decision tables, each column corresponds to a ..... that defines a unique combination of conditions, along with the associated actions. Decision rule Discrete values Boolean values.
The notation for conditions “–” means that: Condition is satisfied Condition is not satisfied Condition is irrelevant for the action outcome.
In limited-entry decision tables all the values of the conditions and actions are shown as …. Ranges of numbers Discrete values Boolean values.
The notation for conditions …. means that the action should not occur. "N-A" "X" "Blank".
In decision table testing, the coverage items are the columns containing ....... combinations of conditions. Infeasible Feasible Infinite.
Coverage is measured as the number of exercised columns, divided by the total number of columns. True False.
A state transition diagram models the behavior of a system by showing its .......... states transitions. Possible valid Impossible & invalid.
A transition is initiated by an: Decision table Code Event.
Guard conditions and actions can't be omitted under any condition. True False.
In state table mode rows represent ....... , and its columns represent ......... . Table entries (cells) represent ......... . Events, transitions and states States, events and transition, Transition, events and states.
All State Transition coverage is measured as: The number of visited states divided by total number of states The number of exercised valid transitions divided by the total number of valid transitions The number of valid and invalid transitions exercised or attempted to be covered by executed test cases, divided by the total number of valid and invalid transitions.
Valid transitions coverage is weaker than all states coverage. True False.
It also called 0-switch coverage: All state coverage All transitions coverage Valid transition coverage.
Valid transitions coverage is the most widely used coverage criterion. True False.
Statement testing & Branch testing are codeless-related white-box test techniques. True False.
In statement testing, the coverage items are non-executable statements. True False.
Statement Coverage is measured as : The total number of executable statements in the code divided by the number of statements exercised by the test cases The number of statements exercised by the test cases divided by the total number of executable statements in the code The number of statements exercised by the test cases divided by the total number of non-executable statements in the code.
Exercising a statement with a test case will detect defects in all cases, even defects that are data dependent. True False.
100% statement coverage always exercises all the branches in the code. True False.
A ........ is a transfer of control between two nodes in the control flow graph. Coverage Statement Branch.
In branch testing each transfer of control can be either Unconditional or conditional Straight line code or a decision outcome All of the above.
In branch testing the coverage items are branches. True False.
Conditional branches typically correspond to: A true or false outcome from an "if … then" decision An outcome from a switch case statement A decision to exit or continue in a loop All of the above.
Any set of test cases achieving 100% branch coverage also achieves 100% statement coverage and vice versa. True False.
White-box techniques can't be used in static testing at all. True False.
White-box coverage measures provide an objective measurement of coverage. True False.
It is a technique used to anticipate the occurrence of errors, defects, and failures, based on the tester’s knowledge. Exploratory testing Error guessing Checklist-based testing.
Parameter mismatch is an error related to: Input data Interfaces.
They are a methodical approach to the implementation of error guessing. Exploratory testing Fault attacks Tester experience.
In exploratory testing, tests are …. designed, executed, and evaluated while the tester learns about the test object. Separatly Simultaneously.
Exploratory Testing is used for: Learn more about the test object Explore test object more deeply with focused tests Create tests for untested areas All of the above.
Exploratory testing is sometimes conducted using ............. to structure the testing. Equivalence partitioning Session based testing Checklist based testing.
Exploratory testing is useful in: When there are few or inadequate specifications or there is significant time pressure on the testing To complement other formal test techniques Answer is A & B.
Checklists should contain items that can be checked automatically. True False.
Checklists can be created to support functional testing only. True False.
User stories have three critical aspects called together the ......... 3 S's 3 C's 3 K's.
“3 C’s” are: Card, Conversation & confirmation Card, Conversation & collaboration.
The acceptance criteria in “3 C’s”: Card Conversation Confirmation.
Good user stories should be: Independent, negotiable, valuable, estimable, small and testable (INVEST) Independent, negotiable, viable, estimable, small and testable (INVEST) Independent, normal, valuable, estimable, small and testable (INVEST).
An implementation of the user story must meet to be accepted by stakeholders. Acceptance criteria Quality assuerance Quality control.
Acceptance criteria are usually a result of the: Card Conversation Confirmation.
Acceptance criteria describes both positive and negative scenarios. True False.
Given/When/Then is a ............ format to write acceptance criteria for a user story. Scenario oriented Rule oriented.
In Acceptance Test-driven Development (ATDD) test cases are created after implementing the user story. True False.
In Acceptance Test-Driven Development (ATDD) The test cases are created by: Customers Testers Developers Answer is B&D All of the above.
In Acceptance Test-driven Development (ATDD), test cases can be executed manually or automated. True False.
Chapter Five Chapter Five.
A test plan helps to ensure that the performed test activities will meet the established criteria. True False.
Test levels, test types, test techniques, test deliverables, entry criteria and exit criteria are ........ examples . Context of testing Test approach.
Testers involved in release planning by participating in project and quality risk analyses. True False.
Iteration planning looks ahead to the end of a single iteration and is concerned with the iteration backlog. True False.
Testers involved in iteration planning participate in project and quality risk analyses. True False.
Define the preconditions for undertaking a given activity. Entry criteria Exit criteria.
Define what must be achieved in order to declare an activity completed. Entry criteria Exit criteria.
Entry criteria and exit criteria will differ based on the test level. True False.
Which of these is not included in entry criteria: Test basis Initial quality level of a test object Defect density.
Definition of Done in agile development. Entry criteria Exit criteria.
Estimation for small tasks is usually less accurate than for the large ones. True False.
In which of the following estimation techniques figures are collected from previous projects within the organization. Metrics-based technique Expert-based technique.
Estimation based on ratios is a : Metrics-based technique Expert-based technique.
In Estimation based on ratios the best source to use in the estimation process is: By applying a mathematical model Historical data.
Extrapolation is an expert-based technique in which the effort required for the remaining work can be approximated by extrapolating the data of the current project. True False.
The most suitable technique for iterative SDLCs is: Estimation based on ratios Extrapolation Expert based techniques.
Wideband Delphi is an iterative metric-based technique True False.
Wideband Delphi can't be repeated until a consensus is reached. True False.
In ......... estimates are usually made using cards with numbers that represent the effort size. Three point estimation Planning poker Extrapolation.
Three-point Estimation is a metric-based technique. True False.
In Three-point estimation, three estimations are made: The most optimistic estimation, the most unlikely estimation and the most pessimistic estimation The most optimistic estimation, the most likely estimation and the most pessimistic estimation.
The abbreviation of the most likely estimation is: a m b.
If the estimates (in person-hours) are:
The most optimistic estimation=12
The most likely estimation=18
the most pessimistic estimation=36
Then the final estimation is: 14+or- 4 36+or- 2 20+or- 4.
If a test case with a higher priority is dependent on a test case with a lower priority, the higher priority test case must be executed first. True False.
It is a model showing that different tests may have different granularity. Test pyramid Service tests UI tests.
The test pyramid model supports the team in: Test automation Test effort allocation All of the above.
The pyramid layers represent groups of tests. The higher the layer, the higher the test granularity, test isolation and test execution time. True False.
Tests in the bottom layer of the test pyramid are small, isolated, slow, and check a large piece of functionality. True False.
Quadrant Q1 Technology facing, support the team Business facing, support the team Technology facing, Business facing Business facing, Business facing.
This quadrant contains exploratory testing, usability testing, user acceptance testing. Quadrant Q1 Quadrant Q2 Quadrant Q3 Quadrant Q4.
This quadrant contains smoke tests and non-functional tests (except usability tests). Quadrant Q1 Quadrant Q2 Quadrant Q3 Quadrant Q4.
Consisting of risk identification and risk assessment. Risk analysis Risk control.
The test approach, in which test activities are selected, prioritized, and managed based on risk analysis and risk control is called: Risk analysis Risk control Risk based control.
The probability of the risk occurrence is called: Risk likelihood Risk impact.
Poor tool support is considered: Project risk Product risk.
Delays in work products deliveries is Considered: Project risk Product risk.
Security vulnerabilities are considered: Project risk Product risk.
Product risk when they occur may result in injuries or even death. True False.
Ideally, product risk analysis begins early in the SDLC. True False.
Product risk analysis consists of: Risk identification Risk assessment All of the above.
It is about generating a comprehensive list of risks: Risk identification Risk assessment.
It involves categorization of identified risks, determining their risk likelihood, risk impact and level, prioritizing, and proposing ways to handle them. Risk identification Risk assessment.
Product risk control consists of: Risk mitigation and risk monitoring Risk identification and risk assessment.
Risk mitigation involves: Implementing the actions proposed in risk assessment to reduce the risk level Ensuring that mitigation actions are effective.
Test control is concerned with gathering information about testing. True False.
Test completion activities occur at project milestones. True False.
Test metrics are gathered to show : Progress against the planned schedule and budget The effectiveness of the test activities with respect to the objectives or an iteration goals Answer is A & B.
mean time to failure is considered : Test progress metrics Product quality metrics Project progress metrics.
Task completion is an example of: Coverage metrics Test progress metrics Project progress metrics.
Test execution time is an example of: Defect metrics Test progress metrics Project progress metrics.
Test Reports include test metrics. True False.
A test completion report is prepared: During test completion When test entry & exit criteria has been met All of the above.
Communicating the Status of Testing should be tailored accordingly. True False.
Which of these work products are considered as configuration items. Test plans, test strategies, and conditions Test cases, test scripts, and test results Test logs, and test report All of the above.
Is an example of a complex configuration item: Test environment Test conditions.
Anomalies may be reported during any phase of the SDLC. True False.
open, deferred, duplicate, waiting to be fixed, awaiting confirmation testing, re-opened, closed, rejected
These are examples of: Severity of the defect Status of the defect Priority to fix.
Chapter Six Chapter Six.
Tools that support the tester in performing reviews and static analysis. Non functional testing tools Static testing tools Collaboration tools.
Tools that facilitate generation of test cases, test data and test procedures. Management tools Test execution and coverage tools Test design and implementation tools.
Which of these are not potential risks of using test automation: Using a test tool when manual testing is more appropriate Easier access to information about testing to support test management and test reporting Unrealistic expectations about benefits of a tool.
|
