What Categories of Errors is Black Box Testing Expected to Find?
- Incorrect or Missing Functionality
- Interface Errors
- Errors in Data Structures
- Behavior or Performance Errors
- External Database Errors
- Initialization and Termination Errors
What are the Factors to Consider for Black Box Testing Inputs?
- Inputs that force error messages
- Inputs that cause input buffer overflows
- Repeat inputs or series of inputs
- Inputs that force invalid outputs
- Inputs that force too small or too large computation results
Advantages of Black Box Testing?
- Efficient for large systems
- Separates tester and developer
- Tester can be non-technical
- No need for detailed functional knowledge
- Tests done from end-user POV
- Helps identify functional specification vagueness and contradictions
- Test cases can be designed as soon as functional specifications are complete
Disadvantages of Black Box Testing?
- Test cases challenging to design
- Difficult to identify tricky inputs if not based on specifications
- Difficult to identify all possible inputs
- Writing test cases is slow
- Chance of having unidentified paths in testing
- Chances of having repeated tests from the programmer
What are the Black-box Testing Techniques
- Graph-based testing methods
- Equivalence partitioning
- Boundary value analysis
- Decision table testing
- Omission testing/null case
- Load testing
- Stress testing
What is Graph-based Testing?
- Utilizing graphical representations of software to design and execute test cases
What are the Parts of Graph-based Testing Graphs?
- Nodes: software objects (circle)
- Links/links: relationships between objects
- Node Weights: describes node properties
What are the 3 Node Categories in Graph-based Testing?
- Directed Link (one-directional arrow)
- Bidirectional/Undirected/Symmetric Link (Both Directions)
- Parallel Links (different relationships)
What are the 3 Types of Graphs Used in Graph-based Testing?
- State-transition graph: for behavior changes with status
- Activity/flow graph: for processes or navigation
- Use-case model: to capture main + alternate/exception scenarios with actos
What is Equivalence Partitioning in Graph-based testing?
Dividing input data into groups of equivalent values to reduce test cases to be developed
What is an Equivalence Class in Equivalence Partitioning?
A set of valid or invalid states for input conditions
What is Boundary Value Analysis?
A type of equivalence partitioning testing that selecting inputs at the boundaries of test data
What is Decision Table Testing?
Multiple Input Combinations Producing Different Outcomes
What is Omission Testing?
- Checks for inputs the developer forgot to handle or didnt anticipate
- AKA Missing Case Testing
What is Null Case Testing?
- Inputting nothing
- Specific case of omission testing
What is Load Testing?
Performance testing application’s behavior under normal and anticipated peak conditions
What is Stress Testing?
Performance testing beyond normal operational capacity until system crash
What is a Test Case?
Document consisting of conditions or actions performed to vervify expected functionality of software
What are Test Cases?
Inputs to test the system and the predicted outputs
What is Test Case Documentation?
contains a set of test cases for a system, testing process, who, what, when, how, and anticipated results
What is a Test Case Name in Test Case Documentation?
Main way to identify a test case, direct description of what the test is intended for
What are the Three Categories of the Three-level Priority Categorization Scheme in Test Case Documentation?
- High: tests that must be executed in any case
- Medium: execute only when time permits
- Low: if not executed, will not cause big upsets
What are the Parts of a Test Case Documentation?
- Project Name
- Test Case ID
- Test Case Name
- Priority Level
- Test Designed By
- Test Designed Date
- Test Executed By
- Test Execution Date
- Short Description
- Preconditions
- Steps
- Actions
- Expected Results
