Brainscape's Knowledge GenomeTM

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


See full index

Sqa > Sqa > Flashcards

Sqa Flashcards

1
Q

Acceptance Testing

A

Validates the software against user requirements and ensures it is ready for delivery.

Example sentence: The acceptance testing phase confirmed that the software met all specified user requirements.

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

Agile Development

A

An iterative and incremental approach to software development with a focus on collaboration, customer feedback, and small, rapid releases.

Additional information: Agile development emphasizes adaptability and flexibility in response to changing requirements.

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

Analysis

A

The process of examining requirements, design, and code to understand and improve software quality.

Example sentence: Thorough analysis of the software architecture revealed opportunities for optimization.

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

Audit

A

A formal examination of software processes, documentation, and products to ensure compliance with standards.

Example sentence: The audit identified areas where the software development process did not align with industry best practices.

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

Automated Testing

A

Using software tools to execute tests automatically, reducing manual effort and improving consistency.

Additional information: Automated testing is essential for regression testing and ensuring rapid feedback on code changes.

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

Backtracking

A

A debugging technique where you go back through the code to find the source of a defect.

Example sentence: Backtracking helped pinpoint the error in the algorithm implementation.

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

Bench Testing

A

Testing software in a controlled environment to isolate and identify defects.

Example sentence: Bench testing revealed memory leaks in the software under stress conditions.

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

Black-box Testing

A

Testing based on input and output without knowledge of the internal code structure.

Example sentence: Black-box testing focuses on the software’s functionality rather than its implementation details.

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

Bottom-Up Testing

A

Testing begins with lower-level components and progresses to higher-level components.

Example sentence: Bottom-up testing ensures that individual modules work correctly before integrating them into the larger system.

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

Boundary Value Analysis

A

Testing the boundaries between partitions to identify defects at the edges of input ranges.

Example sentence: Boundary value analysis helped uncover edge cases that caused unexpected behavior in the software.

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

Buddy Check

A

Informal code review where two colleagues review each other’s code.

Example sentence: The buddy check process improved code quality and knowledge sharing among team members.

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

Bug Record

A

A detailed log of defects found during testing, including steps to reproduce, severity, and status.

Example sentence: The bug record provided valuable insights into recurring issues and their impact on software quality.

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

Cause-Effect Graphing

A

A technique to identify and test the relationships between causes (inputs) and effects (outputs).

Example sentence: Cause-effect graphing helped prioritize testing efforts by focusing on critical paths in the software.

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

Circulation Review

A

A method where documents are circulated among reviewers for feedback and approval.

Example sentence: The circulation review process ensured that multiple stakeholders provided input on the software requirements.

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

CMMI (Capability Maturity Model Integration)

A

A framework for improving and assessing the maturity of software development processes.

Example sentence: Adhering to CMMI practices can lead to more predictable and efficient software development outcomes.

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

Code Inspection

A

A formal review of source code to identify defects and ensure coding standards.

Example sentence: Code inspection revealed inconsistencies in coding practices and potential security vulnerabilities.

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

Comparison

A

Evaluating software against predefined criteria or comparing two versions to identify differences.

Example sentence: The comparison of the new software release with the previous version highlighted performance improvements.

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

Component Testing

A

Testing individual components of software in isolation.

Example sentence: Component testing is crucial for verifying the functionality and behavior of each software module.

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

Condition Coverage

A

Ensuring each boolean condition in the code is tested for true and false outcomes.

Example sentence: Condition coverage testing identified logical errors that occurred when specific conditions were not properly evaluated.

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

Debugging

A

The process of finding and fixing defects in the software.

Example sentence: Debugging is an iterative and problem-solving process that improves software reliability.

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

Debugging by Backtracking

A

Tracing back through the code to find the source of a defect.

Example sentence: Debugging by backtracking helped identify the incorrect variable assignment that caused the software crash.

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

Debugging by Brute Force

A

Using extensive and often repetitive testing to locate a defect.

Example sentence: Debugging by brute force involved exhaustive testing to identify the root cause of the memory leak.

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

Debugging by Deduction

A

Using logical reasoning to identify the cause of a defect.

Example sentence: Debugging by deduction narrowed down the possible sources of the software error based on the observed behavior.

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

Debugging by Induction

A

Making observations and forming hypotheses to find the source of a defect.

Example sentence: Debugging by induction involved analyzing patterns in the software behavior to infer the likely causes of the defect.

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

Debugging by Testing

A

Running tests to identify and isolate defects in the software.

Example sentence: Debugging by testing involved creating test cases to reproduce the reported software issues.

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

Decision/Condition Coverage

A

Ensures all decision points and conditions are tested.

Example sentence: Decision/condition coverage testing confirmed that all possible logic branches in the software were exercised during testing.

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

Demonstration

A

Showing the software’s functionality to stakeholders to confirm it meets requirements.

Example sentence: The demonstration of the software features to stakeholders validated that the product aligned with user expectations.

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

Equivalence Partitioning

A

Dividing input data into partitions that are expected to produce similar behavior.

Example sentence: Equivalence partitioning reduced the number of test cases needed to cover different data ranges in the software.

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

Error Analysis

A

Examining defects to understand their root causes and prevent future occurrences.

Example sentence: Error analysis identified common patterns in software defects that led to the implementation of preventive measures.

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

Error Checklist

A

A list of common errors to check for during reviews and testing.

Example sentence: The error checklist served as a reference guide for identifying known software issues during quality assurance activities.

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

Error Guessing

A

Using experience and intuition to identify likely areas of the software where defects may exist.

Example sentence: Error guessing helped prioritize testing efforts by focusing on high-risk areas of the software.

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

Extreme Program Testing

A

Testing software with extreme values or conditions to ensure robustness.

Example sentence: Extreme program testing simulated edge conditions to assess the software’s resilience under extreme scenarios.

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

Factory Testing

A

Testing performed in a controlled environment before deployment to the production environment.

Example sentence: Factory testing ensured that the software components were functional and stable before release.

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

First Article Qualification

A

Verifying that the first produced unit meets all specifications and requirements.

Example sentence: First article qualification confirmed that the initial production unit met the design and quality standards.

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

Function Testing

A

Validating individual functions of the software to ensure they work as intended.

Example sentence: Function testing verified that each software function performed the expected operations accurately.

36
Q

Functional Testing

A

Testing based on the software’s functional requirements and specifications.

Example sentence: Functional testing validated that the software features functioned according to the specified requirements.

37
Q

Grey-box Testing

A

Combines black-box and white-box testing techniques, using limited knowledge of the internal code.

Example sentence: Grey-box testing provided insights into the software functionality while also verifying internal code paths.

38
Q

Hallway Intercept

A

Informal usability testing where random people in a public space are asked to use the software and provide feedback.

Example sentence: Hallway intercept testing gathered user feedback from diverse individuals to improve software usability.

39
Q

Higher-Order Testing

A

Advanced testing techniques that go beyond basic testing methods.

Example sentence: Higher-order testing involved complex scenarios and performance testing to evaluate the software under realistic conditions.

40
Q

Incremental Testing

A

Testing in stages, where parts of the system are integrated and tested incrementally.

Example sentence: Incremental testing allowed for early detection of integration issues and ensured a smoother software development process.

41
Q

Inspection

A

A formal review process where a work product is examined in detail to identify defects.

Example sentence: Inspection uncovered design flaws in the software architecture that required immediate corrective action.

42
Q

Inspection Agenda

A

A planned schedule for conducting inspections, including objectives and steps to be followed.

Example sentence: The inspection agenda outlined the review process and criteria for evaluating the software design.

43
Q

Inspection Team

A

A group of people conducting a formal inspection of a software product.

Example sentence: The inspection team consisted of domain experts and developers to ensure comprehensive review coverage.

44
Q

Installation Testing

A

Ensures software installs correctly and functions as expected in its intended environment.

Example sentence: Installation testing verified that the software installation process was seamless across different operating systems.

45
Q

Integration Testing

A

Tests the interaction between integrated units/modules to detect interface defects.

Example sentence: Integration testing revealed communication issues between software components that required resolution.

46
Q

Load Testing

A

Evaluates software performance under expected user loads to identify bottlenecks and limits.

Example sentence: Load testing helped optimize server capacity to handle peak user traffic without performance degradation.

47
Q

Logic (Statement) Coverage Testing

A

Measures the extent to which the source code statements have been executed.

Example sentence: Logic coverage testing assessed the code paths that were executed during testing to ensure comprehensive code coverage.

48
Q

Milestone Reviews

A

Evaluates the project’s progress at specific points to ensure it meets the planned objectives.

Example sentence: Milestone reviews identified project delays and risks early on, enabling proactive risk mitigation strategies.

49
Q

Mitigation

A

Implementing strategies to reduce or eliminate risks in software development.

Example sentence: Mitigation measures were implemented to address security vulnerabilities identified during threat analysis.

50
Q

Module (Unit) Testing

A

Tests individual components or modules of a software separately.

Example sentence: Module testing verified the functionality of each software unit in isolation before integration with other modules.

51
Q

Multiple Condition Coverage

A

Ensures all possible combinations of conditions in a decision are tested.

Example sentence: Multiple condition coverage testing examined all logical pathways through the software to detect potential defects.

52
Q

Non-incremental (Big-Bang) Testing

A

Combines all modules together at once and tests the system as a whole.

Example sentence: Non-incremental testing detected integration issues that resulted from combining all software modules simultaneously.

53
Q

Milestone Reviews

A

Evaluates the project’s progress at specific points to ensure it meets the planned objectives.

Example: Milestone reviews are conducted at the end of each development phase.

54
Q

Mitigation

A

Implementing strategies to reduce or eliminate risks in software development.

Mitigation techniques include risk avoidance and risk transfer.

55
Q

Module (Unit) Testing

A

Tests individual components or modules of a software separately.

Module testing is often automated to ensure thorough coverage.

56
Q

Multiple Condition Coverage

A

Ensures all possible combinations of conditions in a decision are tested.

This testing technique helps uncover complex logic errors.

57
Q

Non-incremental (Big-Bang) Testing

A

Combines all modules together at once and tests the system as a whole.

Big-Bang testing can be risky due to limited visibility into individual module performance.

58
Q

Observation

A

Monitoring and recording behavior of a software system during testing.

Observation is crucial for identifying unexpected system behaviors.

59
Q

Operational Scenario Testing

A

Validates the software against real-world scenarios and usage conditions.

Operational scenario testing helps ensure software reliability in practical situations.

60
Q

Packaging and Delivery

A

The process of preparing software for distribution and delivering it to the end users.

Packaging and delivery involve creating installation packages and deployment procedures.

61
Q

Path Coverage Testing

A

Ensures all possible paths through the code are executed.

Path coverage testing helps identify untested code paths.

62
Q

Peer Rating

A

A method where peers evaluate the performance or quality of a product or process.

Peer rating can provide valuable insights from a different perspective.

63
Q

Peer Review

A

Examination of software work products by colleagues to identify defects and improvements.

Peer reviews are commonly conducted before code merges.

64
Q

Performance Testing

A

Measures software’s responsiveness, stability, and scalability under load.

Performance testing helps ensure software meets performance requirements.

65
Q

Product Integration

A

Combining components or systems into a larger product and ensuring they work together.

Product integration testing verifies interactions between integrated components.

66
Q

Project Manager Review

A

An assessment by the project manager to ensure project alignment with goals and requirements.

Project manager reviews help maintain project focus and direction.

67
Q

Qualification Testing

A

Verifies if a system meets specified requirements and performs correctly in its intended environment.

Qualification testing is often part of the final acceptance process.

68
Q

Regression Testing

A

Re-running previously completed tests to ensure changes haven’t introduced new defects.

Regression testing is important after software updates or modifications.

69
Q

Review

A

A process of examining software work products to identify defects and improvements.

Review processes can include code reviews, design reviews, and document reviews.

70
Q

Scrum

A

An agile framework for managing complex software development involving iterative progress through sprints.

Scrum emphasizes collaboration, adaptation, and continuous improvement.

71
Q

Simulation

A

Using models to replicate the behavior of a system for testing purposes.

Simulation can help predict system behavior under different conditions.

72
Q

Statement Coverage

A

Ensures every statement in the code is executed at least once during testing.

Statement coverage is a basic metric for code coverage analysis.

73
Q

Stress Testing

A

Evaluates software stability and reliability under extreme conditions.

Stress testing helps uncover system weaknesses under high load.

74
Q

Structured Walkthrough

A

A detailed review of a software product guided by a set procedure.

Structured walkthroughs help identify issues early in the development process.

75
Q

System Testing

A

Validates the complete and integrated software system to ensure it meets requirements.

System testing verifies end-to-end functionality and performance.

76
Q

Technical Review

A

Analyzing a software product to ensure it meets technical standards and requirements.

Technical reviews focus on software architecture, design, and implementation.

77
Q

Testing

A

The process of executing a program with the intent of finding errors.

Testing is an essential part of the software development life cycle.

78
Q

Top-Down Testing

A

Starts with the highest-level modules and progressively integrates and tests lower-level modules.

Top-down testing can help identify integration issues early in development.

79
Q

Unit Testing

A

Verifying the functionality of individual units/components of software.

Unit testing is often automated and performed by developers.

80
Q

Usability Questionnaire

A

A survey used to collect user feedback on the software’s usability.

Usability questionnaires help gather user perspectives on software usability.

81
Q

Usability Testing

A

Evaluates how easy and user-friendly the software is for end-users.

Usability testing often involves real users performing tasks with the software.

82
Q

Validation

A

Ensures the software meets user needs and requirements.

Validation confirms that the software satisfies its intended purpose.

83
Q

Verification

A

Ensures the software correctly implements specified functions.

Verification focuses on verifying that the software meets specified requirements.

84
Q

Walkthrough

A

A step-by-step presentation of a process or system by its creator to gather feedback.

Walkthroughs can help identify potential issues early in the development process.

85
Q

White-box Testing

A

Testing based on an analysis of the internal workings and structure of the software.

White-box testing is also known as clear box or glass box testing.

Sqa (1 decks)

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