Release Testing - Requirements-Based and Scenario Testing

Release Testing vs. Development Testing

1 pts

volume_mute

Release testing is a form of system testing but differs from development system testing. What is the key difference?

Release testing only checks performance, not functionality

Release testing uses only automated tests, never manual ones

Release testing is performed by the same developers who wrote the code

Release testing is performed by a separate team without involvement from the development team

note_alt Add notes

flag Flag

Correct Answer

Explanation

Primary Goal of Release Testing

1 pts

volume_mute

The primary goal of release testing is to convince the system supplier that the system is good enough for release. What must a successful release test demonstrate? Select all that apply.

The system is sufficiently dependable for deployment

The system has zero defects remaining after testing

The system delivers its specified functionality

The system performs acceptably with normal workloads

The system does not fail in ways that make it unusable

note_alt Add notes

flag Flag

Correct Answer

Explanation

Release Testing as Black-Box Testing

1 pts

volume_mute

Release testing is primarily a black-box or functional testing process. What does this mean?

Tests are derived from examining the internal source code structure

Tests are derived from the system specification, without reference to the internal implementation

Tests focus exclusively on the visual appearance of the user interface

Tests are conducted in a darkened room to simulate poor operating conditions

note_alt Add notes

flag Flag

Correct Answer

Explanation

Requirements-Based Testing Principle

1 pts

volume_mute

What is the fundamental principle of requirements-based testing?

Generate test cases automatically from the requirements specification using tools

Write one comprehensive test that covers all requirements simultaneously

For each requirement, derive tests that check whether or not the requirement has been implemented correctly

Test only the most critical requirements defined by the project manager

note_alt Add notes

flag Flag

Correct Answer

Explanation

Mentcare Allergy Requirements

1 pts

volume_mute

A medical record system has the following drug allergy requirements:

How many separate tests are needed to comprehensively test these two requirements?

No tests needed because these requirements are self-explanatory

Exactly 1 comprehensive test that covers both requirements at once

At least 5 tests - multiple tests per requirement to cover all scenarios

Exactly 2 tests - one per requirement

note_alt Add notes

flag Flag

Correct Answer

Explanation

Mentcare Allergy Test Cases

1 pts

Five test cases were derived to check the drug allergy requirements for a medical record system. Match each test case to what it verifies.

To complete the line match

Click on an item in the first group
Click on the match in the second group

To delete a match, double click on a line

Test Case

Prescriber ignores allergy warning and overrules it

Patient with a known allergy is prescribed the drug they are allergic to

Patient with no known allergies is prescribed a drug

Patient allergic to two drugs is prescribed both drugs separately

Verifies

System requires the prescriber to provide a reason

Warning is issued when the allergic drug is prescribed

Correct warning issued for each drug separately

No warning is issued when no allergy exists

note_alt Add notes

flag Flag

Correct Answer

Explanation

Traceability in Requirements-Based Testing

1 pts

volume_mute

When conducting requirements-based testing, what records should be maintained?

Records of how long each test took to execute

Records of which programming language was used to implement each requirement

Records of which developers wrote each test case

Traceability records that link each test to the specific requirement it was designed to test

note_alt Add notes

flag Flag

Correct Answer

Explanation

Scenario Testing Definition

1 pts

volume_mute

Which of the following best describes scenario testing?

Generating random inputs to test the system under unpredictable conditions

Testing with a fixed set of input partitions derived from the specification

Testing individual requirements in isolation from all other requirements

Devising typical realistic usage scenarios and using these to develop test cases

note_alt Add notes

flag Flag

Correct Answer

Explanation

Characteristics of a Good Test Scenario

1 pts

volume_mute

According to Kaner, a good scenario test should have certain characteristics. Which of the following are required? Select all that apply.

The scenario should be fairly complex

It should be important that the system passes the scenario test

It should be easy for the testing team to evaluate whether the system has passed or failed

The scenario should be a credible narrative story

The scenario must be executed within 5 minutes

The scenario should be written in formal mathematical notation

note_alt Add notes

flag Flag

Correct Answer

Explanation

The Mentcare Home Visit Scenario

1 pts

volume_mute

George is a nurse who specializes in mental health care and visits patients at home. He uses a medical record system during his visits.

When a scenario-based tester plays the role of George and deliberately enters the wrong key phrase to decrypt a record, what is this testing?

The home visit scheduling functionality

The system's response to user errors and its error handling behavior

Performance testing of the decryption algorithm speed

The database connection between the laptop and the clinic server

note_alt Add notes

flag Flag

Correct Answer

Explanation

Scenario Testing Advantage - Multiple Requirements

1 pts

volume_mute

What key advantage does scenario testing have over testing each requirement in isolation?

Scenario testing is cheaper and requires fewer test cases than requirements-based testing

Scenario testing only requires testing the happy path, not error conditions

Scenario testing also checks that combinations of requirements do not cause problems

Scenario testing automatically generates test data without human input

note_alt Add notes

flag Flag

Correct Answer

Explanation

Classify Release Testing Approaches

1 pts

Classify each testing activity into the correct release testing approach.

drag and drop the selected option to the right place

note_alt Add notes

flag Flag

Release Testing vs. Development Testing

Correct Answer

Explanation

Primary Goal of Release Testing

Correct Answer

Explanation

Release Testing as Black-Box Testing

Correct Answer

Explanation

Requirements-Based Testing Principle

Correct Answer

Explanation

Mentcare Allergy Requirements

Correct Answer

Explanation

Mentcare Allergy Test Cases

Test Case

Verifies

Correct Answer

Explanation

Traceability in Requirements-Based Testing

Correct Answer

Explanation

Scenario Testing Definition

Correct Answer

Explanation

Characteristics of a Good Test Scenario

Correct Answer

Explanation

The Mentcare Home Visit Scenario

Correct Answer

Explanation

Scenario Testing Advantage - Multiple Requirements

Correct Answer

Explanation

Classify Release Testing Approaches

drag and drop the selected option to the right place

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: