The goal of a software tester is to find bugs, find them as early as possible, and make sure they get fixed.
Inscription à :
Publier les commentaires (Atom)
Qui êtes-vous ?
Archives du blog
-
▼
2008
(42)
-
►
août
(31)
- Certification Process Checklists
- Defect Removal Efficiency (DRE)
- Incident Description
- Repetitive Tasks
- Black-Box vs. White-Box
- Levels of Test Planning
- Preventive Testing
- Risk Analysis
- Metrics to Measure Performance
- Test Effectiveness
- Test Coverage
- The Bug Fix Rate
- The Number of Bugs Found
- Bug Type Classification
- Severity of Bugs
- Bugs
- Fundamental Metrics for Software Testing
- How to Succeed with MITs
- The Most Important Tests (MITs) Method
- How to Determine a Factor of Safety
- The Engineering Approach
- Approaches to Managing Software Testing
- The quality process - traditional vs. new
- Improving the Quality Process - Improving Document...
- Improving the Quality Process - Improving Document...
- Improving the Quality Process - Improving Document...
- Improving the Quality Process - Picking the Correc...
- Improving the Quality Process - Introduction
- Traditional tools used by quality assurance and so...
- What the Auditors Want to Know from the Testers
- Software Testing Fundamentals-Methods and Metrics
-
▼
juillet
(11)
- The Benefits of Automation and Tools
- The fundamentals of software testing
- Follow Experience, Intuition, and Hunches
- Think like a Hacker
- Look for Bugs Where You've Already Found Them
- Repetition, Stress, and Load
- What Makes a Good Software Tester?
- What Exactly Does a Software Tester Do?
- The Cost of Bugs
- Why Do Bugs Occur?
- What Is a Bug?
-
►
août
(31)
0 commentaires:
Enregistrer un commentaire