Please enable JavaScript.
Coggle requires JavaScript to display documents.
Feature testing plan ((What is the input. Invalid types input.What happens…
Feature testing plan
What is the input. Invalid types input.What happens when user skips a field or puts in wrong data - error or default put into field?
random data added to fields - garbage data, too many characters/too few, typos. Delete default data - errors?
-
-
once you found accepted bad input, use it a lot to test the rest of the software
-
test for memory leaks - watch for screen redraw issues, slow performance
-
-
-
Determine what feature is supposed to do. - read specs,
-
not just the feature needs to be tested, but what data it acts on (RGB, CMYK)
-
Need to control the UI, environment, OS, other software, file system
-
-
How does it fail - graceful? or crash - can it be helped by helpful error messages? What data needs to be saved? Missing error messages? confusing errors? OS/other related errors? Spec should contain errors??
Create test plan
Goals, - method of testing
-
-
-
-
-
-
Strategy - rules and processes, tools, metrics, configurations.
-
-
-
FEATUREs
-
-
test functionality - feature options - stress tests, max/min characters, performance, etc.
Test outside options - different types of images, etc
-
-
-
-
-
Test case types
-
-
-
Workflow - use like a user, find holes, discrepancies, etc
Analyze the product
Design the Test Strategy
Define Test Criteria
Define the Test Objectives
Resource Planning
Plan Test Environment
Schedule & Estimation
Determine Test Deliverables
-
-