Which of the following is true of the V-model….

.it includes the verification of design

..it only models the test phase

..it specifies the test techniques to be used

..it only states that testing against under requirement

Testing according to the V-model has the following fundamental principles

For every development level, there must be a corresponding test level. For every test level, early test design should be implemented.

For every development level, there must be a corresponding test level.

There must a least be the following test levels: Component testing, integration testing, system testing and acceptance testing.

The model is only useful for large critical software projects where there is one delivery only.

Integration testing has this fundamental purpose:

Testing interfaces between components, interactions between different parts of the system, as well as interfaces between systems.

Testing the new system together with the systems existing before.

Testing components together in a hierarchical, incremental way like top-down or bottom-up.

Testing the client part together with different other layers of the software (like for example, application server code, database server code etc.).

… Tests aimed at showing that a component or system does not work.

… Test aimed at showing that a component or system does work.

… Not related to the testers’ attitude

… Related to a specific test approach or test design technique.

Which of these is a functional test? …

Checking the online bookings screen information and the database contents against the information on the letter to the customers.

Measuring response time on an on-line booking system.

Checking the effect of high-volumes of traffic in a call-center system.

Checking how easy the system is to use.

Acceptance testing may occur at more than just a single test level. With the exception of:

Acceptance testing after a change has been released to the user community

Acceptance testing of the usability of a component may be done during component testing

Acceptance testing of a new functional enhancement may come before system testing

A COST software product may be acceptance tested when it is installed or integrated

Non-functional testing includes …

Testing the quality attributes of the system including reliability and usability.

Testing to see where the system does not function correctly.

Gaining user approval for the system.

Testing a system feature using only the software required for that function.

What is the fundamental difference between “static analysis” and test?

Static analysis is done without executing the test object. A test is an examination during “run time”.

Static analysis can be applied at any time during the software life cycle. Test can only be applied after implementation.

Static analysis is applied only in the early phases, test only in the late phases of the software life cycle.

Static analysis checks only documents without a formal structure. Test checks software systems.

Which are the typical roles to be filled in a formal review?

Author, Moderator, Review leader, Reviewer, Scribe

Developer, Moderator, Review leader, Reviewer, Tester

Author, Moderator, Manager, Reviewer, Developer

Author, Manager, Review leader, Reviewer, Designer

Which of the following sequences BEST shows the main activities of the work product review process?

Plan- Initiate review- individual review- Issue communication and analysis- Fix defect and report

Initiate review- Reviewer selection- Individual review- Issue communication and analysis - Rework

Planning& Preparation- Overview meeting- Individual review- FIx- Report

Preparation- Issue Detection- Issue communication and analysis- Rework- Report

… is an analysis without execution of the test object (under analysis)

… serves for creating test cases

… is the precondition for executing the dynamic analysis

… is the check of the program code for compliance with the documentation rules

Which alternative contains ONLY defects which can be discovered by static analysis …

Violations of coding standards, referencing a variable with an undefined value, unreachable (dead) code, security vulnerabilities.

Referencing a variable with an undefined value, unreachable (dead) code, security vulnerabilities, race conditions.

Referencing a variable with an undefined value, deadlocks, unreachable (dead) code, security vulnerabilities.

Referencing a variable with an undefined value, unreachable (dead) code, inconsistent interface between modules and components, race conditions.

How is “expected result” defined?

The behavior predicted by the specification, or another sources, of the test object when executed under specified conditions.

Intended output and/or state value when executing a test object with test data.

The intended behavior and output of the test object when executed under specified conditions.

The output result computed by the test object.

White Box techniques …

… take into consideration the structure of the test object

… are useful in system testing

… check the interfaces of component

… find if not initials are used

If a test of a test object achieved 100% decision coverage then it is guaranteed that …

… 100% statement coverage has been achieved

… 50% path coverage has been achieved

… 100% minimal condition coverage has been achieved

… no other coverage has been achieved

Which of the following is usually not be a coverage measure for state transition testing?

The response time for each transaction is adequate.

Every transition has been exercise

Specific sequences of transitions have been exercised.

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

They depend on an individual’s personal view rather than on a documented record of what the system should do.

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.

They depend on having older testers rather than younger testers.

They depend on a documented record of what the system should do rather than on an individual’s personal view.

Non-functional requirements …

… are often overlooked when writing specification documents, but should be checked anyway.

… are always documented in detail in the specification by the customers.

… need only to be considered in the test if they are documented in the requirements specification.

… should only be validated by the customer, because only the customer can decide if they fulfill his requirements.

Incident management deals with… <br> A. …. Management of deviations from the project plan. B. … Registration of problems, faults and failures. C. … Showing product quality through use of metrics. D. … Definition and implementation of new software requirements. E. … Development of proposals to correct faults.

B and C are true, A, D and E are false

A, B and E are true, C and D are false

A, C and D are true, B and E are false

A, B and C are true, D and E are false

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

Unrealistic expectations, expecting the tool to do too much.

Insufficient reliance on the tool, i.e. Still doing manual testing when a test execution tool has been purchased.

The tool many find defects that aren’t there.

The tool will repeat exactly the same thing it did the previous time.

Comparators belong to this category of tools …

… Tools for planning and test management

… Tools for test specification and test design

… Tools for test results analysis and test object analysis

The selection of a test tool should be done in six steps:

Requirement specification, Market research, Evaluation, Tool demonstration, review, Final selection of tool

Requirement specification, Evaluation, Market research, Tool demonstration, review, final selection of tool

Requirement specification, Market research, Review, Tool demonstration, Evaluation, final selection of tool

Requirement specification, Market research, Tool demonstration, Evaluation, review, final selection of tool

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

Roll out the tool to as many users as possible within the organization

Assess organization maturity, strengths and weaknesses

Evaluate the tool features against clear requirements and objective criteria

Identify internal requirements for coaching and mentoring in the use of the tool

ISTQB Foundation 2

Authored by Hiếu Bồ

Science

Professional Development

Used 24+ times

AI Actions

Add similar questions

Adjust reading levels

Convert to real-world scenario

Translate activity

More...

Content View
Student View

40 questions

Show all answers

MULTIPLE CHOICE QUESTION

15 mins • 1 pt

Which statement about testing is true?

Testing is started after the code is written so that we have a system with which to work.

Testing is started as early as possible in the life cycle.

Testing is most economically done at the end of the life cycle.

Testing can only be done by an independent test team.

MULTIPLE CHOICE QUESTION

15 mins • 1 pt

The risk of an undetected defect …

… does not influence testing in any way.

… has influence on test comprehensiveness and intensity.

… has no influence on the specification of the test cases.

… has no influence on the prioritization of the tests.

MULTIPLE CHOICE QUESTION

15 mins • 1 pt

During testing, …

… all parts of the system should be tested with the same intensity, because defects can be everywhere.

… the user interface should primarily be tested, because failures in it are most annoying for the customer.

… system parts where failures may cause great risks should be tested most intensively.

… data base access should be tested intensively, in order to prevent wrong data and inconsistencies an the database

MULTIPLE CHOICE QUESTION

15 mins • 1 pt

Accrording to ISTQB syllabus, A software error can be described as…

A mismatch between the program and its specification

A description of the relationship between two or more variables or set members in which the values of one does not influence the values of others.

The process in which developers determinate the root cause of a bug and identify possible fixes.

Any ill-advised, substandard, or temporary fix applied to an urgent problem in the ( often misguided) belief that doing so will keep a project moving forward.

MULTIPLE CHOICE QUESTION

15 mins • 1 pt

Deciding how much testing is enough should take account of followings except?

Project constrains

Level of Rick

Decision Table

Safety

MULTIPLE CHOICE QUESTION

15 mins • 1 pt

Which of following is Not “Test Analysis and design” activity in “Fundamental Test Process”?

Identify necessary test data to support the test conditions and test cases

Identifying and prioritizing test conditions based on analysis of test items, the specification, behavior and structure of the software

Creating bi-directional traceability between test basic and test case

Creating test suites from the test procedures for efficient test execution

MULTIPLE CHOICE QUESTION

15 mins • 1 pt

Which is not a goal of writing effective Problem/Bug report?

Explain how to reproduce the problem

Analyze the error so you can describe it in a minimum number of steps.

Write a report that is complete, easy to understand, and non-antagonistic

Illustrate how to fix the problem

Access all questions and much more by creating a free account

Create resources

Host any resource

Get auto-graded reports

Continue with Google

Continue with Email

Continue with Microsoft

or continue with

Facebook

Apple

Others

By signing up, you agree to our Terms of Service & Privacy Policy

Already have an account?

Similar Resources on Wayground

40 questions

Grade 4 Science Exam - Quarter 2

Quiz

•

Professional Development

38 questions

Quiz 2 Neuro

Quiz

•

Professional Development

40 questions

Quiz 1

Quiz

•

Professional Development

37 questions

The Head

Quiz

•

Professional Development

42 questions

PCC Examination

Quiz

•

Professional Development

35 questions

ecosystem

Quiz

•

Professional Development

45 questions

Solid State Components Semester Review

Quiz

•

Professional Development

40 questions

Sains Tingkatan 3 Bab 8 Radioaktif

Quiz

•

Professional Development

Popular Resources on Wayground

10 questions

How much do you know about our Portrait of an Eagle?

Quiz

•

10th Grade

10 questions

Fast Food Slogans

Quiz

•

6th - 8th Grade

21 questions

Continents and Oceans

Quiz

•

6th Grade

20 questions

Parts of Speech

Quiz

•

5th Grade

16 questions

Subject & Predicate

Quiz

•

5th Grade

25 questions

Multiplication Facts

Quiz

•

5th Grade

12 questions

Map Skills

Quiz

•

3rd Grade

22 questions

Continents and Oceans

Quiz

•

5th Grade

Discover more resources for Science

14 questions

Fall Trivia

Quiz

•

11th Grade - Professi...

ISTQB Foundation 2

Which statement about testing is true?

The risk of an undetected defect …

During testing, …

Accrording to ISTQB syllabus, A software error can be described as…

Deciding how much testing is enough should take account of followings except?

Which of following is Not “Test Analysis and design” activity in “Fundamental Test Process”?

Which is not a goal of writing effective Problem/Bug report?

Which of the following is true of the V-model….

Dynamic and----------approaches, such as exploratory testing were testing is more reactive to events than pre-planned, and where execution and evaluation are concurrent tasks..

Testing according to the V-model has the following fundamental principles

Access all questions and much more by creating a free account

Similar Resources on Wayground

Popular Resources on Wayground

Discover more resources for Science