Software QA Testing
Fundamentals
Welcome to this comprehensive presentation on Software QA Testing
Fundamentals. We'll explore the essential concepts that form the backbone of
quality assurance in software development, including test levels, test cases,
test plans, and test case design techniques.
This presentation will provide you with a solid foundation in QA testing
methodology, helping you understand how to effectively validate software
quality throughout the development lifecycle.
by Jess Sinues
Core QA Concepts
Understanding foundational testing terminology and documentation is
essential for effective quality assurance. Let's explore the four primary test
levels that structure the QA process.
Unit Testing
Tests individual components/classes in isolation, performed by
developers during the coding phase
Integration Testing
Validates interactions between modules using approaches like
Big Bang vs Incremental
System Testing
End-to-end validation of the complete system, including
performance and security testing
Acceptance Testing
User-focused validation against business requirements,
including UAT and Alpha/Beta testing
Test Documentation
Essentials
Proper documentation is the backbone of effective QA processes. Test cases
and test plans provide structure and traceability throughout the testing
lifecycle.
Test Cases Test Plans
Formal specification of inputs, Comprehensive documents
steps, and expected outputs. outlining Scope, Timeline,
Contains Test ID, Preconditions, Resource Allocation, Exit
Test Data, and Expected Results. Criteria, and Test Environment
Must be traceable to Specifications. The creation
requirements and include both process involves defining release
positive and negative scenarios. scope, scheduling test phases,
and designing test strategy.
Test Case Design Techniques
Methods like Equivalence Partitioning, Boundary Value Analysis,
Decision Table Testing, State Transition, and Error Guessing help create
effective test cases that maximize coverage while minimizing redundancy.
Test Cases in Detail
Anatomy of a Test Case Execution Process Test Case Types
Test cases contain unique ID, Execute tests methodically, recording Positive cases verify software works
descriptive title, preconditions, and actual outcomes against expected results. correctly with valid inputs.
step-by-step instructions.
Mark cases as pass/fail and document any Negative cases test system response to
Each case also includes expected results defects with detailed evidence. invalid inputs or unexpected conditions.
and actual outcomes for easy verification.
Test Case Writing Approaches
Describe-it Format Traditional Format Behavior-Driven Development
Focuses on describing features and Structured approach using fixed templates (BDD) Format
scenarios in a narrative style that is easy to with preconditions, steps, and expected Uses natural language in Given-When-
understand. results. Then format to describe behavior.
Enhances collaboration between Best for regulatory compliance and Ideal for agile teams and stakeholder
testers and developers complex systems collaboration
Encourages living documentation that Provides detailed traceability and Bridges communication gaps between
evolves with the system documentation technical and business teams
Question: When do we use what?
Hands-On QA Activities
Identify which type of test case writing Practical application reinforces theoretical knowledge. These
format should be used in the following: integrated activities will help you develop real-world QA skills by
applying testing concepts to concrete scenarios.
Test Case Writing Techniques
Equivalence Partitioning:
A specification-based black-box technique that divides
input data into valid and invalid partitions to reduce
test cases while maintaining coverage. Boundary Value Analysis:
A method focusing on testing at the edges of input
ranges to identify errors at boundaries, complementing
State Transition Testing: equivalence partitioning.
Technique that models system behavior as states and
transitions, creating test cases based on state changes
triggered by events or inputs.
Equivalence Partitioning Deep Dive
Equivalence partitioning divides input data into classes where all elements should behave the same way. This reduces test cases while
maintaining thorough coverage.
This technique is important because it optimizes testing efforts by minimizing redundant test cases while ensuring all input scenarios
are effectively evaluated. It helps testers focus on representative inputs, improving efficiency and defect detection.
Equivalence partitioning is commonly used in input validation, form field testing, system configuration testing, and any scenario where
inputs can be grouped by similar expected behavior.
Identify Input Create Partitions Select Test Values Execute Tests
Domains Group inputs into valid and Choose one representative Run tests with selected
Determine all possible invalid classes with similar value from each partition. values to verify entire
inputs the software will behavior. partition behavior.
accept.
Example: Age Verification System
Valid Partition (18-65) Invalid Partition (Under Invalid Partition (Over 65)
Test with age 35 to represent all valid
18) Test with age 70 to check senior-
adult ages. Test with age 16 to verify underage specific handling.
restriction works.
Boundary Value Analysis Deep Dive
Identify Boundaries Select Test Values
Locate exact points where behavior changes. Test directly at Minimum boundary value
boundaries and just inside/outside these critical thresholds. Just below minimum
Maximum boundary value
Just above maximum
Example: Age Verification Benefits
Test ages 17, 18, 19 for minimum boundary. Test ages 64, 65, Catches edge case defects commonly missed in regular
66 for maximum boundary. testing. Complements equivalence partitioning for
comprehensive coverage.
State Transition Testing Deep Dive
State transition testing models system behavior as
interconnected states that change in response to events or
inputs. This technique excels at finding defects in complex,
state-dependent systems.
Verify Invalid Paths
Create Test Cases Test that prohibited state
Define Transitions Design tests for valid transitions are properly
Identify States Map events that trigger transitions and boundary prevented.
Document all possible system movement between states. conditions.
conditions (logged in,
processing, error).
State transition testing is particularly effective for workflow applications, authentication systems, and e-commerce processes where
behavior depends on previous actions.
