Testing - The New World!

Quality software is reasonably  bug or defect  free, delivered on time and within budget, meets requirements and/or expectations, and is maintainable. Key aspects of quality for the customer include: Good design – looks and style Good functionality – it does the job well Reliable – acceptable level of breakdowns or failure Consistency Durable – lasts as long as it should Good after sales service Value for money Good design – looks and style: It is very important to have a good design. The application or product should meet all the requirement specifications and at the same time it should be user friendly. The customers are basically attracted by the good looks and style of the application. The right color combinations, font size and the styling of the texts and buttons are very important. Good functionality – it does the job well: Along with the good looks of the application or the product it’s very important that the functionality should be intact. All th...

What is the difference between Severity and Priority? There are two key things in defects of the  software testing . They are: 1)     Severity 2)     Priority What is the difference between Severity and Priority? 1)  Severity : It is the extent to which the  defect  can affect the software. In other words it defines the impact that a given defect has on the system.  For example:  If an application or web page crashes when a remote link is clicked, in this case clicking the remote link by an user is rare but the impact of  application crashing is severe. So the severity is high but priority is low. Severity can be of following types: Critical:  The defect that results in the termination of the complete system or one or more component of the system and causes extensive corruption of the data. The failed function is unusable and there is no acceptable alternative method to achieve the r...

What is Verification in software testing? or What is software verification? Verification  makes sure that the product is designed to deliver all functionality to the customer. Verification is done at the starting of the development process. It includes reviews and meetings, walk-throughs, inspection, etc. to evaluate documents, plans, code, requirements and specifications. Suppose you are building a table. Here the verification is about checking all the parts of the table, whether all the four legs are of correct size or not. If one leg of table is not of the right size it will imbalance the end product. Similar behavior is also noticed in case of the software product or application. If any feature of software product or application is not up to the mark or if any  defect  is found then it will result into the failure of the end product. Hence, verification is very important. It takes place at the starting of the development process. ...

What is Retesting? When to use it? Advantages and Disadvantages Retesting is testing of a particular  bug  after it has been fixed. Usually tester raises the bug when they find it while testing the product or its component. This bug is assigned to a developer and he fixes it. Post fixing the bug is assigned to the tester for its  verification . This testing is known as retesting. Retesting is done by replicating the same scenario with same data in new build. In retesting those test cases are included which were failed earlier. Retesting ensures that the issue has been fixed and is working as expected. It is a planned testing with proper steps of verification When a bug is raised and is rejected by the developer saying that it’s not re-creatable in their environment then in this case also the testers do the re-testing of the bug to ensure that whether it’s a genuine bug or not. In some cases the entire module is required to be re-tested to ensure the quality of...

If under certain environment and situation defects in the application or product get executed then the system will produce the wrong results causing a failure. Not all  defects  result in failures, some may stay inactive in the code and we may never notice them. Example:  Defects in dead code will never result in failures. It is not just defects that give rise to failure. Failures can also be caused because of the other reasons also like: Because of the environmental conditions as well like a radiation burst, a strong magnetic field, electronic field or pollution could cause faults in hardware or firmware. Those faults might prevent or change the execution of software. Failures may also arise because of human error in interacting with the software, perhaps a wrong input value being entered or an output being misinterpreted. Finally failures may also be caused by someone deliberately trying to cause a failure in the system. Difference between Error, De...

What is Software Quality? Quality software is reasonably  bug or defect  free, delivered on time and within budget, meets requirements and/or expectations, and is maintainable. ISO 8402-1986 standard defines quality as  “the totality of features and characteristics of a product or service that bears its ability to satisfy stated or implied needs.” Key aspects of quality for the customer include: Good design – looks and style Good functionality – it does the job well Reliable – acceptable level of breakdowns or failure Consistency Durable – lasts as long as it should Good after sales service Value for money Good design – looks and style: It is very important to have a good design. The application or product should meet all the requirement specifications and at the same time it should be user friendly. The customers are basically attracted by the good looks and style of the application. The right color combinations, font size and the styling of the...