Tag: testing

Improper Handling of large and small values.

Improper Handling of configuration combinations

Improper Handling of classes of inputs

Improper Handling of typical workflows

Slow Response Time

Excessive Memory Consumption

Random Application termination

Failure to encrypt data

a. Filter rows when the Integration Service reads source data.

b. Join data originating from the same source database

c. Can specify a target load order based on the Source Qualifier transformations in a mapping

d. Create a custom query to issue a special SELECT statement for the Integration Service to read source data.

a. gives 1

b. throw an error

c. gives 2

d. will not evaluate.

a. Static or Dynamic Cache

b. Dynamic cache

c. static cache

d. Static and Dynamic Cache

True

False

A test environment description and test instructions.

A set of inputs, execution preconditions, and expected outcomes.

A test plan, test inputs, and logging instructions.

Execution instructions and a function description to determine correct outcome.

It enables us to reuse all our tests to improve ROI

It can be used to replace acceptance testing.

To reduce the amount of impact analysis we must do when modifying a system.

To discover any defects introduced or uncovered as a result of a change

Non-functional testing.

Structure-based testing (white box).

Static testing.

Functional testing (black box).

A goal of acceptance testing is to stress-test the system.

A goal of acceptance testing is to establish confidence in the system.

Acceptance testing is performed by technical staff.

Acceptance testing is only used to address functionality issues within the system