"Мы верим в Бога. От всех остальных требуется подтверждение"
(Уильям Эдвардс Деминг)
Major Activities And The Generic Testing Process
The main principles of software testing can be best described on the basis of the main activities that take part in testing.

Although there are many various methods to sort them, the main test activities consist of the following phases, which are located in strict chronological order:
Test Planning and Preparation
The main objectives of this phase are the right choice of testing purposes, general testing strategy and preparation of specific test cases and the common testing scheme.
Test Execution
This phase aims at a thorough review and analysis of the software product behavior.
Analysis
At first it is carried out a final inspection and analysis in order to determine whether the problem has been investigated. If so, then we apply the following activities in order to make sure that the main causes of failures and errors are eliminated.
The general scheme of these activities can be described with the help of general testing process. Comparing with the general software development process, these activities have many similarities. In fact, we can consider this overall testing process as an instance of the general quality engineering process to testing. The basic test activities are focused around test execution or implementation of the actual tests.
At a minimum, testing involves running the software and interaction with related observations. Actually, many types of informal tests include just the activities connected to test execution, with some informal means of communication with the results and remove the errors, but without much planning and preparation. However, test planning and preparation activities play a much more significant role in the overall testing process.
The performance of a specific test case or a sub-division of the test execution sequence is often considered as a test run. One of the main tools to effective test carrying out is the processing of problems to ensure that defected runs will not block the execution of other test cases. This is especially important for systems that require further management. Despite the fact that many people believe that error correction is part of the development process, re-verification is considered as a part of testing.
The data that was obtained during the execution can be used to find and remove defects, which can cause serious errors. Once we have determined whether the test is working correctly or wrong, appropriate actions can be used to find and neutralize the underlying defects. Further analyses can be carried out to provide reliable feedback to the software testing and to the overall engineering process.
Analyzing the results provide us with information on the evaluation of the progress of work, effort, defects and product quality. This information can help us to decide when we need to stop testing relying on facts. Some of the tests can help to identify opportunities for continuous improvement of product quality. That’s why some other activities also need to be supported.
Quote of the Day
Our Clients:
Knowledge Center
-
QA Testing Materials
- The Basis Of Interaction Testing
- Software Testing Sub-Stages
- Finite-State Machines for Web Testing
- Software Testing With Different Types Of Checklists
- What Is Checklist-Based Testing?
- Main Software Testing Activities
- Users and Third-Party Testers In Software Projects
- Organization and Management of Software Testing Teams
- Software Test Implementation Measurements
- Why Is It Important to Have Testable Requirements?
- Test Suite Management
- Test Suite Preparation
- What Is The Difference Between Coverage-Based Testing And Usage-Based Statistical Testing
- Two Main Forms Of Stopping Software Testing
- The Meaning of Structural Testing In Software Project
- Major Activities And The Generic Testing Process
- Sub-Activities in Test Planning and Preparation
- Software Testing: Concepts, Issues And Techniques
- Human Efforts In Quality Assurance Activities. Part II
- Human Efforts In Quality Assurance Activities. Part I
- Forming a Quality Assurance Strategy
- Setting Software Quality Purposes
- What to Test and What Type of Faults Are Found?
- Verification and Conformance In Software Testing
- Validation and Failures In Software Testing
- Waterfall Process In the Quality Assurance Activities
- Operating with Pre-/Post-Release Software Bugs
- Software Bug Handling And Related Activities
- Software Bugs’ Averting Activities
- Show all
- What Is Quality In Software Engineering?
- Software Bugs In The Context of Quality Assurance
- At What Defect Level Should We Stop Software Testing?
- When Can a Specific Testing Activity be Conducted?
- When Should We Do Backup and Recovery Testing?
- What Is Documentation Testing?
- Performance Testing And Different Test Types
- Test Documents In The Software Development Lifecycle
- Quality Cost Analysis: Main types of Costs Associated with Software Products
- What Is Defect Removal Efficiency In Software Testing?
- The Severity Ratings In Software Project
- Software Projects Analysis And Design
- Definition and Meaning of Exploratory Testing
- Definition and Meaning of Configuration Management. Part II
- Definition and Meaning of Configuration Management. Part I
- Design of Applications and Regression Testing
- Test Plan Documents Used in a Project
- Main Types Of Strategies For Rolling Out To The End Users
- What Does Testing Company Need From User To Start Proper Testing?
- Start Software Testing On Early Stages. How Does This Affect Cost?
- User Acceptance Testing as One of the Main Service Models in Software Testing Company. Part II
- User Acceptance Testing as One of the Main Service Models in Software Testing Company. Part I
- 5 Types of Software Testing Teams
- Software Test Plan Process
- Incident Management in Software Testing
- The Main Goals of Software Test Plan
- Test Planning and Development Documentation
- The Theory of Software Testing. Testing the Specifications
- Test Execution Documentation
- Definition of Beta Testing
- Performance-Based Decisions: Deciding When and What to Test. Part II
- Performance-Based Decisions: Deciding When and What to Test. Part I
- Error Guessing in Software Testing
- V-MODEL Descriptions. Responsibility of QA Managers and Software Testers
- V-MODEL Descriptions. Responsibility of Developers, Project Managers and Business Analyst
- Fundamental Test Process
- The V-Model Framework
- Risk Management In Software Testing
- Oracle. Definition and Meaning
- Psychology In Software Testing
- How Much Does Quality Cost? Part II
- How Much Does Quality Cost? Part I
- Economics of Testing
- Software Bug's Life Cycle
- When Should You Test?
- Completeness of Software Testing. The Criteria for White Box. Part II
- Completeness of Software Testing. The Criteria for White Box. Part I
- Completeness of Software Testing. The Criteria for Black Box
- Completeness of Software Testing. Introduction
- Practice of Automated Functional Testing in Microsoft Visual Studio
- Estimation of Number of Errors in the Program. Mills Model. Part II
- Estimation of Number of Errors in the Program. Mills Model. Part I
- Ad Hoc and Exploratory. What is the Difference Between Theory and Practice?
- Modern Methods of SQL Injection Attacks: Identification
- Testing of Mobile Applications
- Complete Software Testing Outsourcing. Part II
- Complete Software Testing Outsourcing. Part I
- The Rapid Expansion of the Company's Resources as the Goal of Outsourcing
- Independent Quality Audit. Part III
- Independent Quality Audit. Part II
- Independent Quality Audit. Part I
- Testing of Existing Software Products
- Overview of Automated Testing Tools
- Independent Software Testing
- Necessary Tools to Test Linux
- Basics of Automated Functional Testing
- Product Life Cycle and Testing
- Models of Organization of Independent Testing
- Tools for Testing From HP
- Tools for Testing From the IBM Rational
- What Do We Need to Know to Become an Expert in Performance Testing?
- How to Сontrol Test Data
- The Basic Load Testing Tools
- The Importance of Software Testing Automation
- Selenium: Subsidiary Tools
- Attacks on Unprotected Login Forms
- 10 Usability Heuristics
- The Introduction to JMeter
- Autotests: Myths And Reality
- Evaluation of software reliability
- Developers Don’t Like Testers, Because They Don’t Know How to Use Them
- 15 Important Theses About Usability Testing
- Load Testing of the Projects
- Pylot - Tool For Load Testing of Web Applications
- Key Terms of Load Testing
- An Example of System Requirements
- Life Duration of Software Bug
- 4 Attributes of Qualitative and Well-Written Test-Case
- Superstitions in Software Testing
- Fundamentals of Mobile Application Testing
- 3 Tips to Reduce Mobile Application Testing Efforts
- Project Applications that are Easy to Test
- Software Testing Checklist – 5 Steps to Success
- Top 10 Critical Software Bugs of 2010 Year
- 3 Types of Mobile Wireless Applications
- What Is A Mobile App and Why Do I Want One?
- What is Fuzz Testing?
- Mutation Testing – Way to Verify Your QA Team
- Effective Use Case Example
- Well-Performing Application is Goal of Performance Testing
- The Parable of the Pyramids in a New Way
- Pareto Principle in Software Testing
- Who is a Good Tester?
- Has the Software Tester Right to Make Mistakes?
- 5 Tips to Get Started in Software Testing
- 3 Tools to Test UI Mockups Compliance
- 5 Simple Ways to Reproduce Not Reproducible Bug
- 4 Best Add-ons to Identify Selenium Locators
- Running Selenium Server Using Custom Firefox Profile
- 3 Goals of Usability Testing
- 3 Forms of Acceptance Testing and their Application
- Test Strategies for Smartphones and Mobile Devices
- Embedded Software Testing
- Testing Techniques for Mobile Applications
- Tutorial Database Testing using SQL
- 12 Best Cross Browser Testing Tools to Ease Your Browser Compatibility Testing Efforts
- 6 Tips to Get Started with Automated Testing
- Do I Need to Test the Automated Tests?
- Technical Terms Used in Testing World
- ISTQB Advanced Practioner Level Practice Exam 1
- Mobile Usability Testing: Problems and Solutions
- Does any one know a good open source tool for Test Management and Bug Tracking?
- Software Quality Metrics
- How to Make Adhoc Testing More Effective
- Test Plan for a Mobile Applications
- 10 reasons why you are not getting job in software testing
- Top 20 Practical Software Testing Tips
- Wasting Your Time By Not Writing Tests
- Test Checklist For Mobile Applications
- Sample Deliverables
- Software Testing Glossary


















