Socrative Week 5

Question 1

What knowledge does the tester have about the software in black box testing?

Answer 1

No knowledge of inner workings of software

Question 2

In black box testing, the tester accesses the system as a user would?

Answer 2

True

Question 3

In black box testing, the SW system is a machine that?

Answer 3

Accepts input
Provides output
Makes changes based on the tester request

Question 4

In black box testing, the tester focuses on whether or not the system operates as expected from the ___ perspective

Answer 4

User

Question 5

In black box testing, the tester looks for user-facing defects which are defects the user would encounter

Answer 5

True

Question 6

In black box testing, the tester is?

Answer 6

An ordinary user

Question 7

Why do black box testing?

Answer 7

Functional errors
Errors in data structures or external database access
Behavior of performance errors
Initialization and termination errors
Interface errors
Incorrect or missing functions

Question 8

Black box testing method is applicable to which software testing levels?

Answer 8

Integration testing
System testing
Acceptance testing

Question 9

The higher the SW test level, the bigger and more complex the box, the more black box testing method comes into use

Answer 9

True

Question 10

Some test design techniques in black box testing include equivalent class partitioning, boundary value analysis, and cause effect graphing

Answer 10

True

Question 11

Equivalence class partitioning involves?

Answer 11

Dividing input values into valid and invalid partitions

Selecting representative values from each partition as test data

Question 12

Boundary value analysis involves?

Answer 12

Determining boundaries for input values

Selecting values that are the boundaries and just inside/outside of the boundaries as test data

Question 13

Cause Effect Graphing involves?

Answer 13

Identifying the cases (input conditions) and effects (output conditions)
Producing a cause-effect graph and generating test cases

Question 14

Programs need to deal with various situations, some require unique program elements to handle them correctly?

Answer 14

True

Question 15

Which of the following are testing risks?

Answer 15

Programmers might fail to recognize a particular situation as unique and needing unique handling
Programmers recognize that the situation is unique but might create unique elements of the program that handle the situation incorrectly
Programmers might fail to recognize or properly define these boundaries

Question 16

Equivalence partitioning helps you recognize and test unique situations to ensure the programmer didn’t make such mistakes

Answer 16

True

Question 17

In equivalence class partitioning there is one set of input values that maps to an output value and this set is called an___?

Answer 17

Equivalence class
Equivalence partition

Question 18

Equivalence class partitioning separates a specific functionality into distinct equivalence classes based on input values

Answer 18

True

Question 19

Testers create equivalence classes by grouping input values that do something dissimilar

Answer 19

False

Question 20

Equivalence classes enable testers to create tests which cover all or most parts of functionality, and avoid over-testing just one part

Answer 20

True

Question 21

Equivalence classes can be applied at any level of testing and is often a good test design technique to use first.

Answer 21

True

Question 22

Boundary value analysis is black box test design technique used to find errors at boundaries of input domain rather than finding those errors in the center of input

Answer 22

True

Question 23

Equivalence Partitioning and Boundary value analysis are linked to each and can be used together at all levels of testing?

Answer 23

True

Question 24

Interior values are?

Answer 24

Values which are not boundary values

Question 25

Black box testing advantages include?

Answer 25

Tests are done from a user’s point of view and will help in exposing discrepancies in the specifications
Tests can be conducted by a body of testers independent from the developers, allowing for an objective perspective and the avoidance of developer-bias
Test cases can be designed as soon as the specifications are complete
Tester doesn’t need to know programming languages or how the software has been implemented