Podcast
Questions and Answers
In software testing, what is the primary purpose of evaluating software against requirements?
In software testing, what is the primary purpose of evaluating software against requirements?
- To ensure the software meets the needs gathered from users and system specifications. (correct)
- To optimize the software's performance speed.
- To determine the cost-effectiveness of the software.
- To simplify the user interface of the software.
Which of the following best describes the role of a software test plan?
Which of the following best describes the role of a software test plan?
- A technique for optimizing software performance.
- A method for documenting code errors.
- A tool used to automatically generate test cases.
- A document that outlines the strategy, scope, resources, and schedule of intended testing activities. (correct)
What elements are typically included in a test case?
What elements are typically included in a test case?
- Inputs, execution conditions, testing procedure, and expected results. (correct)
- Hardware specifications, network configurations, and security protocols.
- Project timelines, team member assignments, and risk assessments.
- Software license details, user feedback, and cost analysis.
What does 'test coverage' measure in the context of unit testing?
What does 'test coverage' measure in the context of unit testing?
In integration testing, what is the primary purpose of simulating the behaviour of lower-level modules in a top-down approach?
In integration testing, what is the primary purpose of simulating the behaviour of lower-level modules in a top-down approach?
Which of the following is an advantage of using a top-down approach in integration testing?
Which of the following is an advantage of using a top-down approach in integration testing?
A key advantage of using a bottom-up approach in integration testing is that:
A key advantage of using a bottom-up approach in integration testing is that:
What is the primary goal of regression testing?
What is the primary goal of regression testing?
What is the focus of system testing?
What is the focus of system testing?
Which of the following best describes the purpose of acceptance testing?
Which of the following best describes the purpose of acceptance testing?
What is the main characteristic of black-box testing?
What is the main characteristic of black-box testing?
How does white-box testing differ from black-box testing?
How does white-box testing differ from black-box testing?
Under what condition is fuzz testing considered to have found an issue?
Under what condition is fuzz testing considered to have found an issue?
What is the key focus of Test Driven Development (TDD)?
What is the key focus of Test Driven Development (TDD)?
What is a key benefit of Test-Driven Development (TDD)?
What is a key benefit of Test-Driven Development (TDD)?
Which testing level focuses on individual units or components of the software?
Which testing level focuses on individual units or components of the software?
What is the primary purpose of integration testing?
What is the primary purpose of integration testing?
If modules are integrated from the bottom up, what component is tested last?
If modules are integrated from the bottom up, what component is tested last?
What is the role of stubs in top-down integration testing?
What is the role of stubs in top-down integration testing?
Which testing type requires knowledge of the internal code structure?
Which testing type requires knowledge of the internal code structure?
What is a disadvantage of bottom-up integration testing?
What is a disadvantage of bottom-up integration testing?
What is the primary use case for fuzz testing?
What is the primary use case for fuzz testing?
What characteristic makes fuzz testing easily automatable?
What characteristic makes fuzz testing easily automatable?
What is verified during regression testing?
What is verified during regression testing?
Who is often responsible for performing acceptance testing?
Who is often responsible for performing acceptance testing?
Flashcards
Software Testing
Software Testing
Evaluating software against requirements gathered from users and system specifications (SDD).
Software Test Plan
Software Test Plan
A document describing the scope and activities of software testing.
Test Case
Test Case
Detailed specification of inputs, execution, conditions, testing procedures and expected results.
Unit Testing
Unit Testing
Signup and view all the flashcards
Test Coverage
Test Coverage
Signup and view all the flashcards
Integration Testing
Integration Testing
Signup and view all the flashcards
Top-Down Integration
Top-Down Integration
Signup and view all the flashcards
Bottom-Up Integration
Bottom-Up Integration
Signup and view all the flashcards
Regression Testing
Regression Testing
Signup and view all the flashcards
System Testing
System Testing
Signup and view all the flashcards
Acceptance Testing
Acceptance Testing
Signup and view all the flashcards
Black-Box Testing
Black-Box Testing
Signup and view all the flashcards
White-Box Testing
White-Box Testing
Signup and view all the flashcards
Fuzz Testing
Fuzz Testing
Signup and view all the flashcards
Test Driven Development (TDD)
Test Driven Development (TDD)
Signup and view all the flashcards
Study Notes
- Software testing is evaluating software against user requirements and system specifications in the Software Design Document (SDD)
- Test time duration approximates coding time.
Software Test Plan
- The software test plan is a document that describes the scope and activities of software testing
- Test case procedures include procedures, inputs, and expected outputs/results
- Examples include a unit testing plan, integration testing plan, and system testing plan
- A test case specifies the inputs, execution conditions, testing procedure, and expected results
- It defines a single test to achieve a software testing objective
- Includes exercising a program path or verifying compliance with a specific requirement.
Levels of Software Testing
- Unit testing
- Integration testing
- Regression testing
- System testing
- Acceptance testing
Unit Testing
- Unit testing is a method to determine whether an individual unit of source code behaves correctly
- Focus on functional correctness and completeness of individual program units like functions or modules.
- Software developers typically perform unit testing
- All paths should be tested during unit testing
- Test coverage describes how much the source code of a program is executed when a test suite is run.
- Higher coverage indicates better testing
Integration Testing
- It is the phase in software testing, where individual software modules are combined and tested as a group
- Developers or testers can perform integration testing
- Top-down approach is an integration testing technique that simulates the behavior of the lower-level modules that are not integrated yet
- Fault localization is a basic component in fault management systems and identifies the cause of defects
- Advantages of the Top-down Integration testing approach include easier fault localization and possibility of getting an early prototype
- Disadvantages include the need for lots of stubs/mock objects and potentially reusable modules may be inadequately tested
- Bottom-up approach is a testing strategy that tests modules at the lower level with higher modules until all modules and aspects of the software are tested properly.
- The Bottom-up integration approach has easier fault localization and needs no stubs/fewer mock objects
- The Bottom-up integration approach has disadvantages like needing drivers
Regression Testing
- Regression testing verifies that a code change in the software does not impact existing functionalities of the product
- Reduces the side effects
- It is different than retesting
System Testing
- Testing is conducted on a complete integrated system and evaluates the system's compliance with its specified design requirements
- Can be done on simulators
Acceptance Testing
- Acceptance testing is formal testing with respect to user needs, requirements and business processes
- It's conducted to determine whether a system satisfies acceptance criteria and to enable the user, customers, or other authorized entity to determine whether the system is accepted.
- Customers make the decision for acceptance testing
Testing Techniques
- Black-box testing examines the functionality of software without peering into its internal structures or workings
- It can apply to all test levels from unit testing to system testing
- White-box testing tests internal structures or workings of software as opposed to its functionality
- It applies to all test levels from unit to system testing
- Fuzz testing is feeding random inputs to an application and to verify if the application can handle the random inputs
- Proposed by Barton Miller at the University of Wisconsin Madison in 1989
Test Driven Development
- It is a technique for building reliable software that guides software development by writing tests
- It is about design, where design is evolved through refactoring
- Developers write unit tests (not testers)
- Early problem discovery, facilitates change, simplifies integration, self documentation, and it visualizes the design are benefits
Studying That Suits You
Use AI to generate personalized quizzes and flashcards to suit your learning preferences.
