Where test progress monitoring is about gathering detailed test data, there reporting test status is about effectively communicating our findings to other project stakeholders. [Read more…]
A good incident report is a technical document. We have few rules of thumb that can help you write a better incident report:
- First, use a careful, attentive approach to execute your tests. You never know when you are going to find a problem. If you are pounding on the keyboard while gossiping with office mates or thinking about a movie you just saw, you might miss few of the strange behaviors. [Read more…]
After logging the incidents that occur in the field or after deployment of the system we also need some way of reporting, tracking, and managing them. It is most common to find defects reported against the code or the system itself. However, there are cases where defects are reported against requirements and design specifications, user and operator guides and tests also. [Read more…]
When we talk about incidents we mean to indicate the possibility that a questionable behavior is not necessarily a true defect. We log these incidents so that we can keep the record of what we observed and can follow up the incident and track what is done to correct it. [Read more…]
While executing a test, you might observe that the actual results vary from expected results. When the actual result is different from the expected result then it is called as incidents, bugs, defects, problems or issues. [Read more…]
There are many techniques to analyze the testing. They are:
- One technique for risk analysis is a close reading of the requirements specification, design specifications, user documentation and other items.
- Another technique is brainstorming with many of the project stakeholders. [Read more…]
Risk based testing is basically a testing done for the project based on risks. Risk based testing uses risk to prioritize and emphasize the appropriate tests during test execution. In simple terms – Risk is the probability of occurrence of an undesirable outcome.
This outcome is also associated with an impact. Since there might not be sufficient time to test all functionality, Risk based testing involves testing the functionality which has the highest impact and probability of failure.
Risk-based testing is the idea that we can organize our testing efforts in a way that reduces the residual level of product risk when the system is deployed. [Read more…]
Testing is an activity like the rest of the project and thus it is subject to risks that cause danger to the project.
The project risk that can endanger the project are:
- Risk such as the late delivery of the test items to the test team or availability issues with the test environment.
- There are also indirect risks such as excessive delays in repairing defects found in testing or problems with getting professional system administration support for the test environment. [Read more…]
Product risk is the possibility that the system or software might fail to satisfy or fulfill some reasonable expectation of the customer, user, or stakeholder. (Some authors also called the ‘Product risks’ as ‘Quality risks’ as they are risks to the quality of the product.) [Read more…]
In software testing Risks are the possible problems that might endanger the objectives of the project stakeholders. It is the possibility of a negative or undesirable outcome. A risk is something that has not happened yet and it may never happen; it is a potential problem. [Read more…]