Professional Documents
Culture Documents
Smoke Testing
Smoke Testing
Smoke Testing
Since it is well-documented that software errors, even a single one can cost
millions more than your entire testing budget, the first priority should be first
to deliver reliable software. Once this is achieved, then foucs on optimizing the
time and costs. In other words, if your software doesn't work, it doesn't matter
how fast or cheap you deliver it.
Why automate?
When not to automate
How not to automate
Setting realistic expectations
Getting and keeping management commitments
Terminology
Selecting a Test Automation Approach (This will be the best time to include all the
GUI Testing Tools)
Capture/ Playback
Structure
Advantages
Disadvantages
Comparison Considerations
Data-Driven
Structure
Advantages
Disadvantages
Data Considerations
Table-Driven
Structure
Advantages
Disadvantages
Test Execution
Test log
Error log
Capture and replay does not result in a test library that is robust, maintainable
or transferable as changes do occur.
Not everything can be automated, do allow time for tasks that can't be automated -
you will still need to gather test requirements, define test cases, maintain your
test library, administer the test environment, and review and analyze the test
results. On an ongoing basis you will also need time to add new test cases based on
enhancements or defects, so that your coverage can constantly be improving.