Software Testing - Full Review

Fundamental Limit of Testing

1 pts

volume_mute

Which statement most accurately captures the fundamental limit of software testing?

Testing guarantees that the software is defect-free when all test cases pass

Testing can only show the presence of errors in a program; it cannot show there are no remaining faults

Testing proves software correctness when 100% branch coverage is achieved

Testing is only useful for functional requirements, not non-functional ones

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Validation vs. Verification - Key Distinction

1 pts

volume_mute

Complete the two questions that distinguish validation from verification: Validation: "Are we building the (1) product?" Verification: "Are we building the product (2)?"

Please drag and drop the selected option in the right place or type it instead

wrong

faster

right

correctly

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Three Stages of Commercial Testing

1 pts

volume_mute

Activities

×A separate QA team verifies the complete system meets all specified requirements

×A customer signs off on the system after testing it with real operational data

×A programmer writes automated unit tests for a new method as they implement it

×Beta users experiment with an early public release and report bugs online

Development testing

Release testing

User testing

Classify each activity into the correct stage of commercial software testing.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Inspection Advantage - Error Masking

1 pts

volume_mute

Why does software inspection avoid the problem of error masking that affects testing?

Inspections use formal verification that prevents errors from occurring

Inspections automatically fix errors before they can mask each other

Inspections do not involve executing the system, so errors in one part cannot cause misleading outputs in another

Inspections require errors to be corrected in the order they are found

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Parts of an Automated Unit Test

1 pts

volume_mute

To complete the line match

Click on an item in the first group
Click on an item in the second group
To delete a match, double click on a line

Part

Assertion

Setup

Call

Description

Invoke the object or method being tested

Compare the actual result with the expected result; true means pass, false means fail

Initialize the system with the test case inputs and expected outputs

An automated unit test has three standard parts. Match each part to its description.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Equivalence Partitioning - Core Principle

1 pts

volume_mute

Why can you test just one or a few values from each equivalence partition instead of all possible values?

Because the other values are mathematically equivalent and produce identical binary outputs

Because testing all values is prohibited by intellectual property restrictions

Because testing tools can only generate one value per partition automatically

Because programs normally behave in a comparable way for all members of an equivalence partition

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Four Interface Types

1 pts

volume_mute

Please drag and drop the options to sort them

Sort the four types of component interfaces by placing them in the order they are typically described (parameter, shared memory, procedural, message passing).

Procedural interfaces - one component encapsulates procedures callable by others

Parameter interfaces - data or function references passed from one component to another

Message passing interfaces - components request services by passing messages

Shared memory interfaces - a block of memory shared between subsystems

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

TDD Core Process - Identify the Missing Step

1 pts

volume_mute

In TDD, a developer (1) identifies a small functionality increment, (2) writes an automated test, (3) runs the test and it fails, (4) implements the functionality, and (5) re-runs all tests. If all tests now pass, what is the sixth step?

Write documentation for the new feature

Refactor the code to improve its structure without breaking any tests

Delete the test that was just written to keep the test suite lean

Submit the code for peer review before moving to the next increment

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Release Testing Approaches

1 pts

volume_mute

To complete the line match

Click on an item in the first group
Click on an item in the second group
To delete a match, double click on a line

Approach

Performance testing

Scenario testing

Stress testing

Requirements-based testing

Characteristic

Derives tests directly from each specified requirement to check it has been satisfied

Checks the system meets response time and throughput requirements at expected load

Uses realistic usage stories to test multiple features together and their interactions

Overloads the system beyond its design capacity to observe failure behavior

Match each release testing approach to its key characteristic.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

User Testing Types - Sort by Formality

1 pts

volume_mute

Please drag and drop the options to sort them

Arrange the three types of user testing from least formal (most exploratory) to most formal (most contractually binding).

Beta testing - a larger group of users experiments and reports problems

Alpha testing - selected users work with the development team on early releases

Acceptance testing - customers test with real data to decide on contract sign-off

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Three Interface Error Classes

1 pts

volume_mute

Scenarios

×A developer calls a network function assuming it will block until complete, but it is actually asynchronous

×In a real-time system, a sensor writes data to shared memory faster than the processor can read it, causing stale data

×A developer passes arguments to a sorting function in the wrong order, reversing the sort direction

Interface misuse

Interface misunderstanding

Timing error

Classify each scenario into the correct interface error class.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

TDD Benefits vs. Limitations

1 pts

volume_mute

Statements

Guideline-Based Testing for Sequences

1 pts

volume_mute

Which three guidelines are recommended for testing programs that process sequences or arrays?

Derive tests so that the first, middle, and last elements of the sequence are accessed

Always test with the maximum possible sequence length only

Test only with sequences containing unique values

Test with sequences that have only a single value

Use different sequences of different sizes in different tests

Only test sequences with an even number of elements

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

User Testing - Working Environment Impact

1 pts

volume_mute

A hospital patient information system passes all system tests and release tests in the developer's lab. During user testing in the hospital, nurses report that the system is unreliable and slow during busy periods. What does this illustrate?

User testing is unnecessary if release testing has already been completed

Influences from the real working environment (concurrent users, clinical interruptions, real data volumes) can cause issues invisible in the developer's artificial testing environment

The hospital's hardware is inadequate and must be upgraded before deployment

The developer's testing was incompetent and should be repeated

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Comprehensive Classification of Testing Concepts

1 pts

volume_mute

Statements

×Checks system delivers specified functionality; performed by a separate team

×Includes alpha, beta, and acceptance testing

×Primarily a defect testing process, interleaved with debugging

×Performed by the development team; includes unit, component, and system testing

×Essential because the developer cannot replicate the real working environment

Development testing

Release testing

User testing

Classify each statement as belonging to development testing, release testing, or user testing.

note_alt Add notes

flag Flag

volume_mute

Fundamental Limit of Testing

Correct Answer

Explanation

Validation vs. Verification - Key Distinction

Correct Answer

Explanation

Three Stages of Commercial Testing

Correct Answer

Explanation

Inspection Advantage - Error Masking

Correct Answer

Explanation

Parts of an Automated Unit Test

Part

Description

Correct Answer

Explanation

Equivalence Partitioning - Core Principle

Correct Answer

Explanation

Four Interface Types

Correct Answer

Explanation

TDD Core Process - Identify the Missing Step

Correct Answer

Explanation

Release Testing Approaches

Approach

Characteristic

Correct Answer

Explanation

User Testing Types - Sort by Formality

Correct Answer

Explanation

Three Interface Error Classes

Correct Answer

Explanation

TDD Benefits vs. Limitations

Correct Answer

Explanation

System Testing - Emergent Behavior

Correct Answer

Explanation

Acceptance Testing Stages - Correct Order

Correct Answer

Explanation

Automated vs. Manual Testing - Key Advantage

Correct Answer

Explanation

Mock Objects - Purpose and Use

Correct Answer

Explanation

Scenario Testing - Multiple Requirements Coverage

Correct Answer

Explanation

Guideline-Based Testing for Sequences

Correct Answer

Explanation

User Testing - Working Environment Impact

Correct Answer

Explanation

Comprehensive Classification of Testing Concepts

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: