software testing final

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/125

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

126 Terms

1
New cards

Positive test

Testing which attempts to show that a given application does what it’s supposed to do when given an acceptable set of inputs

2
New cards

What is test execution results reporting?

Its crucial for communicating the status of testing activities between testing teams and stakeholders because it provides insight on the readiness of the software.

3
New cards

What does a test result report need?

Test summary, test cases executed, pass/fail stats, defect summary, execution timeline, logs and screenshots, and a coverage report

4
New cards

What’s the process of test reporting?

  1. Test execution

  2. Data collection

  3. Data Compilation

  4. Analysis

  5. Report generation

  6. Distribution

5
New cards

When testing mobile applications, what types of testing should we use?

Functional, Performance, Compatibility, Usability, Security, Localization, and Regression testing.

6
New cards

When testing mobile applications, why should we use Localization testing?

Because it adapts content to various languages and cultures for global user engagement.

7
New cards

In a bug lifecycle, what does “new” mean?

The bug is initially reported and unapproved

8
New cards

In a bug lifecycle, what does “Open” mean?

Approved as a valid bug and passed to developers

9
New cards

In a bug lifecycle, what does “test” mean?

After fixing, the bug is assigned back to testers

10
New cards

What is the bug life cycle?

  1. New

  2. Open

  3. Assigned

  4. Test

  5. Verified

  6. Closed

11
New cards

In Bug Severity, define "critical.”

Prevents further testing or application usage

12
New cards

In Bug Severity, define “Major”.

Causes a feature to fail or behave incorrectly

13
New cards

In Bug Severity, define "Medium”

Affects functionality but has a workaround

14
New cards

In Bug Severity, define "Minor”

Cosmetic issues without functional impact

15
New cards

A good bug report should be what?

Reproducible and specific enough for developers to identify and resolve the problem.

16
New cards

Top-down estimating is used for what?

early, high-level estimates

17
New cards

Define Accessibility Testing

A means to ensure applications are usable by individuals with disabilities, aligning with accessibility standards like WCAG

18
New cards

What is the purpose of code inspections?

Error detecting, compliance with standards, knowledge sharing, improving maintainability

19
New cards

What are the benefits of code inspections?

early detection of defects, Improved code quality, Learning opportunities, team building

20
New cards

A well-written, ready-to-execute test case should have what?

Pre-Conditions, Test steps, Expected Results, Post-Conditions

21
New cards

In a test case content, define a precondition

The initial step or conditions must be met before executing the test.

22
New cards

In test case content, define a Test Steps

Detailed instructions that outline each action the tester must perform to execute the test case.

23
New cards

In test case content, define an expected result

Descriptions of the outcomes that should result from each test step. This is crucial for determining if the test has passed or failed.

24
New cards

In the test case content, define Post-conditions

Any actions to restore the system to its original state after the test case execution. This may involve logging out, resetting data, or any clean-up steps.

25
New cards

Is Dynamic Application Security testing White box or Black box? and why?

Black-box testing because it runs the application by simulating real-world attacks

26
New cards

Is Static Application Security testing White-box or Black-box? and why?

White box because it analyses the source code without executing

27
New cards

Security Audit

A thorough evaluation of an application’s security controls, ensuring they meet compliance requirements and industry standards.

28
New cards

What are the different types of API testing?

Unit, Integration, and End-to-End testing

29
New cards

Contract Acceptance Testing

Validates that the software fulfills the contractual obligations.

30
New cards

Regulatory Compliance Testing

Ensures the system adheres to legal requirements.

31
New cards

Define Load Testing

Tests the system’s behavior under expected load conditions, identifying bottlenecks. --> positive and negative testing

32
New cards

Define Stress testing

Pushes the system beyond its limits to see where it breaks. This helps us determine the capacity of the application to improve it.

33
New cards

Define Compatibility Testing

Ensures the app works across different devices, screen sizes, and OS versions.

34
New cards

Acceptance testing

verifies that a software product meets business requirements and is ready for release.

35
New cards

Define User Acceptance Testing

Focuses on ensuring the product works according to user expectations and business needs.

36
New cards

Operational Acceptance Testing

Tests non-functional aspects like performance, security, and reliability.

37
New cards

Negative test

Testing which attempts to show that an application does not do anything that it is not supposed to do when given an unacceptable set of inputs

38
New cards

Risk-Based Testing

Software testing that prioritizes the features and functions to be tested based on priority/importance and likelihood or impact of failure

39
New cards

State-Based Testing

Testing that involves driving test cases from a state transition model of the system or function being tested

40
New cards

Static testing

A form of software testing where the software isn’t used, consisting mainly of syntax checking of the code or manually reading code and documents to find errors

41
New cards

Dynamic Testing

A term used to describe the testing of the application through examination of the physical responses from the system. The software must be compiled and run to perform this testing.

42
New cards

White Box

Testing that takes into account the internal data structures and algorithms of a system or component

43
New cards

Grey Box

testing that involves having access to internal data structures and algorithms for purposes of designing the test cases, but then testing those at an external level

44
New cards

Black Box

Testing that ignores the internal mechanisms of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions

45
New cards

Equivalence testing

In this method, the tester identifies various classes/groups of input data. A class/group is a set of input conditions that are likely to be handled the same way by the system

46
New cards

Boundary Value Analysis

when a test engineer chooses values that lie along data extremes—including maximum, minimum, just inside ranges, just outside ranges, typical values, and error values.

47
New cards

All-Pairs testing

For every two input parameters to a system, tests all possible discrete combinations of those parameters

48
New cards

Which of the following is the basis for the testing axiom: "It's Impossible to Test a Program Completely, (4 pts)

a) The number of possible inputs is very large. 

b). The number of possible outputs is very large. 

c). The number of paths through the software is very large. 

d). The software specification is subjective and open to interpretation. 

e). All of these 

f). None of these 

e). All of these

49
New cards

What should be done to avoid “The Pesticide Paradox”?

a). Avoid over-testing any application to ensure that software bugs do not become "immune" to that testing. 

b). Software testers must continually write new and different tests to exercise different parts of the program to find more bugs. 

c). Only use test cases as regression tests once to ensure that the software will not become "immune" to them. 

d). Testers must strive to test all possible values/scenarios to ensure that software bugs do not become "immune" to that testing. 

e). All of these. 

f). None of these. 

B

50
New cards

“As the knowledge of internal coding structure is prerequisite, it becomes very easy to find out which type of input/data can help in testing the application effectively,” is an advantage of white box testing. True or false.

True

51
New cards

“Tests may need to be updated if the code base is rapidly changing” is an advantage of white box testing. True or false.

False

52
New cards

“White-box testing can speed up the testing process significantly” is an advantage of white box testing. True or False

False

53
New cards

This is an advantage of white box testing “It helps in optimizing to code by removing superfluous sections of code and condensing existing code”. True or False.

True

54
New cards

“It helps in removing hidden errors which may not come up during normal testing” is an advantage of white box testing. True or False.

True

55
New cards

What is NOT commonly used during a task estimation technique?

a) Expert opinion

b) Delphi technique

c) Three-point technique

d) Geometric technique

D

56
New cards

While the software developers are in the implementation phase, the testing team would be doing what?

a). Unit test development and execution

b). Projecting final cost of the testing effort

c). Testing the requirements

d). Integration test execution

e). Test case automation

f). Design review

g). Code review/inspection

h). Feature Validation

A, D, E, G

57
New cards

True or false. Code inspections should check standard compliance, code structure, and code logic.

True

58
New cards

True or False. Code inspection practices should not vary based on the programming language used.

False

59
New cards

Which of the following are not benefits of coding inspections? Select all that apply. (4 pts) 

a). Readability: Consistent code is easier to read and understand, especially for developers who did not originally write it. 

b). Maintainability: Following conventions makes it easier to modify and maintain the code, as developers can predict the structure and style. 

c). Precise, Unambiguous, and Clear: Code inspections help ensure that requirements are clear and have a single interpretation for every member of the team. 

d) Collaboration: When all team members follow the same conventions, it simplifies collaboration and reduces friction during code reviews. 

e) Tool Support: Many development tools (IDEs, linters, formatters) are configured to enforce or adhere to standard Java conventions, making it easier to maintain consistency automatically. 

f) All of these 

C

60
New cards

10) Which of the following are advantages of Black Box testing? Select all that applies. (4 pts)

a). The development of black box tests can be initiated at an early stage of the development of software. 

b). Tests in black box testing are conducted from the end-user perspective. 

c). It can be difficult to understand the root cause of issues uncovered via black box testing techniques. 

d). Testers don't need to have programming knowledge, resulting in potential cost savings (less expensive resources required) 

e). Testing is considered unbiased because the developers and testers work independently. 

f). Because black-box testing does not consider the internals of an application, it is difficult to determine test coverage. 

A, B, D, E

61
New cards

Unit testing is Black-Box, White-Box or Both?

Both

62
New cards

Design Review is Black-Box, White-Box or Both?

Black-Box

63
New cards

Requirements review is Black-Box, White-Box or Both?

Both

64
New cards

Functional/System testing is Black-Box, White-Box, or Both?

Black-Box

65
New cards

Is equivalence partitioning Black-Box, White-Box, or Both?

Black-Box

66
New cards

Is code review Black-Box, White-Box, or Both?

White-box

67
New cards

Is decision table testing Black-Box, White-Box, or Both?

Black-box

68
New cards

Is boundary value analysis Black-Box, White-Box, or Both?

Black-box

69
New cards

Is all-pairs testing Black-Box, White-Box, or Both?

Black-box

70
New cards

Is state-based testing Black-Box, White-Box, or Both?

Black-Box

71
New cards

Define Inside-Out risk-based testing

Begin with details about the situation and identify risks associated with them (internal). Ask "What can go wrong here?".

72
New cards

Define Outside-In Risk-Based Testing

Begin with a set of potential risks and match them to the details of the situation. You would consult a predefined list of risks and determine whether they apply here.

73
New cards

Define Unit Testing

The testing of individual software modules or groups of related modules.

74
New cards

Define Integration Testing

Testing in which software components, hardware components, or both are combined and tested to evaluate the interaction between them.

75
New cards

Define Functional/System Testing

Using black box testing techniques, testers examine the customer requirements specifications to plan and execute test cases that ensure the code does what it is intended to do.

76
New cards

Define Regression testing

Selective retesting of a system or component to verify that modifications have not caused unintended effects and that the system or components still comply with its specified requirements.

77
New cards

Define Beta Testing

When an advanced partial or full version of a software packaging is available, the development organization can offer it free to one or more potential users

78
New cards

Define Performance Testing

Testing is conducted to evaluate the compliance of a system or component with specified execution time requirements.

79
New cards

Define Usability Testing

Testing is conducted to evaluate the extent to which a user can learn to operate, prepare inputs for, and interpret outputs of a system or component.

80
New cards

Indicate what minimum set of data values you would use for testing the following input and why:

Only whole numbers can be input. A time duration, in minutes, -must be greater or equal to 1 and less than 360

I would test 0, 1, 359, and 360 because these values cover the boundary cases: 0 is just below the valid range, 1 is the minimum valid value, 359 is just within the upper boundary, and 360 is just outside the valid range. This helps ensure the program correctly identifies valid and invalid inputs at the edges."

81
New cards

Indicate what minimum set of data values you would use for testing the following input:

(only 2 decimal place values can be input) must not be less than $0.00. There is no maximum cost.

I would test -0.01 and 0.00

82
New cards

indicate what minimum set of data values you would use for testing the following input:

(String any character can be input) catalog ID that is exactly 9 characters and contains only upper/lowercase letters and numbers.

9 char Alpha + Numeric

8 char A + N

10 char A + N

9-char w/ special characters

null/empty

83
New cards

Indicate what min set of data values would you use for testing the following input:

(only a single character can be input) The item code must be a single uppercase letter character from A through Z. No other values are allowed.

A, Z, a, 1, any special character

84
New cards

Using the weighted three-point technique, assume you have an optimistic estimate of 3 days, a pessimistic estimate of 13 days, and a most likely estimate of 5 days. What would the resulting final estimate be?

6 days because 3 + 13 + (4 × 5) = 36/6 = 6

85
New cards

Using the flat average three-point technique, assume you have an optimistic estimate of 3 days, a pessimistic estimate of 13 days, and a most likely estimate of 5 days. What would the resulting final estimate be?

7 days because 3 + 13 + 5 = 21/3 = 7

86
New cards

A fully specified test case would contain which 3 sections?

A). Pre-Conditions/Pre-Requisites

B). Alternate Endings

C). Cleanup Actions & Verification

D). Test Actions & Verifications

E). Regression Steps

F). Automated Instructions

A, C, D

87
New cards

While the software developers are doing requirements gathering, the testing team would be doing what?

A). determining testing needs

B). Developing the cost of the test effort

C). Testing the requirements

D). Evaluating the usefulness of each required feature

E). Design review

F). Code Review/Inspection

G). Estimating the test effort

H). Test resource planning

I). Determine the duration of the software development

J). Develop/Receive Acceptance Tests

A, C, G, H

88
New cards

While the software developers are doing issue fixes, the testing team would be doing what?

A). Functional test execution

B). Developing the cost of the test effort

C). Testing the requirements

D). Evaluating the usefulness of each required feature

E). Design review

F). Code Review/Inspection

G). Acceptance Test Execution

H). Regression test execution

I). Security test execution

J). Develop/Receive Acceptance Tests

K). Performance test execution

L). Automated Test Execution

M). Beta Test execution

N). Test result reporting

A, G, H, I, K, L, N

89
New cards

While the software developers are doing design, the testing team would be doing what?

A). determining testing needs

B). Developing the cost of the test effort

C). Security test development

D). Performance test development

E). Design review

F). Code Review/Inspection

G). Estimating the test effort

H). Test resource planning

I). Determine the duration of the software development

J). Develop/Receive Acceptance Tests

K). Test case development

L). Usability test development

M). Integration test development

C, D, E, K, L, M,

90
New cards

Define correct based on SRS

Every requirement specified in the requirements document will be accurate

91
New cards

Define Manageable based on SRS

Requirements should be expressed in such a way that each item can be changed without excessive impact on other items.

92
New cards

Define “Free of Design Detail” based on SRS

Requirements documents should not include implementation details

93
New cards

Define “Consistent” based on SRS

Requirements should not conflict with each other

94
New cards

Define “Relevant” based on SRS

Each item is pertinent to the problem and its solution

95
New cards

Define “Complete” based on SRS

Every requirement should be comprehensive and give all information on what is expected

96
New cards

Define Feasible according to the SRS

It should be possible to implement the requirements with the available resources and time given

97
New cards

Define Testable according to the SRS

It should be possible to determine whether the stated requirements have been satisfied or not.

98
New cards

Define Precise and Unambiguous according to the SRS

Each item in the requirement should be clear and have a single interpretation for every member of the team.

99
New cards

What is JUnit testing?

Test automation framework in Java is used mainly for unit testing.

100
New cards

Define Automated Functional Testing

Ensures that an application behaves as expected from an end-user’s perspective. By automating the execution of test cases, teams can validate functionality and quickly identify defects early in the development process.