Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

345 > System Testing > Flashcards

System Testing Flashcards

1
Q

Trigger Conditions

A

Inputs that will give rise to failures indicating the existence of faults that can be isolated and eliminated

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

When does Unit testing begin

A

Happens in parallel with construction. Each developer tests the units that he or she is implementing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Assemblages

A

Large sub-systems of combined unit tests that are tested together.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Alpha Testing

A

1st stage of system testing, developers test the entire product

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Beta Testing

A

2nd state of system testing, involves actual users testing the product in either a simulated env. or the actual env.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Subsystem testing

A

unit and integration testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

System testing

A

Alpha and beta testing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Differences b/w system and subsystem testing

A

system involves an increment of the entire product
subsystem testing does not
System involves units or sub-systems that were constructed by several people
Units tests typically created and executed by the developer who constructed the unit

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Who preforms sub-system tests?

A

People who have intimate knowledge of the engineering design and implementation of the product, include CLEAR and BLACK-box techniques

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Who preforms system testing?

A

People without knowledge of product design. BLACK BOX

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

How are sub-system tests created?

A

From detailed requirements specs or detailed user storiess

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

How are system tests created?

A

From descriptions of interactions b/w users and the system (use cases or user stories about features). State of system is likely to change during a test

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What do Unit testing and integration testing depend on?

A

The nature of the product: customize or build the product Differences matter these differences don’t matter in system tests

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Finger pointing is more likely to occur in sub-system or system testing?

A

System testing because entire team vs. individual

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Personnel Alpha Testing

A

Testers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Enviornment Alpha Testing

A

Controlled - to isolate and record failures

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Purpose Alpha Testing

A

Validation (indirect) and Verification

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Recording Alpha Testing

A

Extensive Logging

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Personnel Beta Testing Acceptance and Installation

A

Users

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Environment Beta Testing Acceptance

A

Controlled

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Purpose Beta Testing Acceptance

A

Validation (Direct)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Recording Beta Testing Acceptance

A

Limited Logging

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Environment Beta Testing Installation

A

Uncontrolled

24
Q

Purpose Beta Testing Installation

A

Verification

25
Q

Recording Beta Testing Installation

A

Limited Logging

26
Q

Problems with Alpha Testing

A

Conflict of interest - not always want to identify failures want to prove it is fault free
Don’t want testing and development team to become adversairies

27
Q

Functional alpha testing

A

attempts to validate and verify the features provided by the software product. Validation when the tests are created and verification when the tests are conducted

28
Q

How is Functional alpha testing conducted (bottom-up or top-down)?

A

Bottom-up, most basic functionality tested first to make it easier to isolate failures

29
Q

Operational Profiles

A

Contain information about the relative frequency of different use cases and the order in which use cases typically occur. Tests are then reflect these patterns of usage

30
Q

Non-Functional Alpha Testing

A

Execution requirements (response time and memory usage)

31
Q

Types of Non-Functional Alpha Testing (6)

A 
Timing tests
reliability tests
availability test
Stress Tests
Recover Tests
Configuration Tests
32
Q

Timing Tests

A

Evaluate non-functional requirements related to the time required to perform a function

33
Q

Benchmarks

A

Standardized timing tests

34
Q

Reliability Tests

A

determine the probability that the product will fail in a given interval of time

35
Q

Availability tests

A

Determine the probability that a product will be usable at a particular time

36
Q

Stress Tests/Torture tests

A

Determine robustness (ability to operate under a wide range of conditions) and the safety (ability to minimize the damage resulting from a failure) of the system

37
Q

Stress tests that exclusively focus on safety are called?

A

Recovery tests

38
Q

Configuration tests

A

used to assess the product of different hardware or software platforms and in different operating enviornments

39
Q

Usability Tests

A

Tests checking requirements about the user interface

40
Q

Internationalization/localization tests

A

Usability tests that involve both translations and locale-specific information (currencies, number formats, and time and date info)

41
Q

Accessibility testing

A

ensures that the user interface is appropriate for all people regardless of physical ability.

42
Q

Beta Acceptance Testing

A

Done by clients to validate the product (satisfies clients’ needs and desires).
Order and frequency in which features are used is not controlled
But all features are tested
Tests functional and non-functional execution

43
Q

Beta Installation Testing

A

Used to verify product, to determine that it operates properly in the user’s environment. Not expert testers so failures they report may be hard to understand (minimize dependence on installation testing)

44
Q

Traditional Process

A

Some requirements will be mapped to unit test and others will be mapped to system tests (few mapped to integration tests)

45
Q

Most important testing in traditional process?

A

Unit testing (occur earlier hence more important) Integration doesn’t begin until fairly late in process

46
Q

Stubs

A

Placeholder code that stands in for units that have not yet been constructed (for traditional interface)

47
Q

When does alpha testing occur in traditional process

A

Near the end, because don’t need working version until end

48
Q

Test Plan

A

Document that plans the system testing in traditional process

49
Q

How are tests made for traditional processes

A

From requirements specs

50
Q

When are alpha and integration testing for Scrum?

A

Every sprint to show items in project backlog are complete

51
Q

Build Verification Tests/smoke tests

A

Product is built and tested each day using automated tests, ensure that product remains at a given quality throughout its incremental development.

Need to smoke test code before each commit

52
Q

Release candidates (RC)

A

Product versions containing all features planned for a release (beta testing for Beta testing but beta can still be done with each sprint depends on team)

53
Q

Which process makes it harder to preform regression testing?

A

Scrum, because hard to isolate regression testing from the rest of testing process because without a formal requirements spec it is difficult to distinguish old features from new features (hard to have baseline for tests)

54
Q

How to record GUI tests

A

record interactions

script that records actions (often easier to understand than recordings and easier to rerun than recordings)

55
Q

Bug tracking systems

A

Tools that exist to help testers record, track and report test results

56
Q

Engineering Design for System Testing

A

Design patterns that make it easier to conduct system tests. Command pattern encapsulates functionality in individual objects. (test independently of the events that trigger that functionality

57
Q

Construction for System Testing

A

Make decisions during the construction phase that facilitate system testing. Some languages and libraries have built-in support for logging. Try catch make it easier to build a flexible test harness

345 (7 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions