Guidelines for Software Testing.

Software Testing is not only about finding defects during test execution. Following are the key guidelines for software testing for improving product quality and delivering quality software product. 1. Testing should uncover software defects and improve software quality. Test team should focus on finding the defects in the software like any deviation from the software requirement specification(…)

Product Risk Vs Project Risk

What is Product Risk Product risk is the risk associated with the software or system, the possibility that software or system may fail to satisfy end user/customers expectations is known as product risk. There may be the possibility that the software or system does not have the functionality specified by the customer or the stakeholders(…)

What is Risk Based Testing?

Before understanding what is risk based testing you should know what a risk is. A risk is something that has not happened yet and it may never happen in future as well. Risk is the possibility of a negative or undesirable outcome or event. We need to handle risk because if it happens, then it may(…)

How to test Web-Based Applications

What is a web based application A web based application is an application which can be accessed and used over the network. i.e. internet, intranet or extranets. Internet is the worldwide collection of interconnected networks. Intranets are the networks which are used within the organizations by internal employees and extranets are the networks which are(…)

Guidelines for writing good and effective Defect Entry.

1. Keep the Defect Summary concise. The defect summary should be very concise and to the point, developer should not need to scroll through the synopsis. For example, “Customer data import fails when .zip file is selected”. Also it is a good practice to indicate the affected area by putting one or two words before(…)

When to automate Software Testing

Being a software tester you might have come across various situations where automation is not advantageous at all and manual testing works better in those situations. Some examples where manual testing is preferred over automation are: UI keeps on changing very frequently. If automation is done for this UI it needs to be changed every(…)

What is Scenario Testing?

Scenario testing is done to make sure that the end to end functioning of software is working fine, or all the business process flows of the software are working fine. In scenario testing the testers put themselves in the end users shoes and figure out the the real world scenarios or use cases which can(…)

Difference between Smoke and Sanity Testing

Smoke Testing Smoke testing term came from hardware testing, when you get new hardware and power it on if smoke comes out then you do not proceed with testing. Smoke testing is done to check the normal health of the build and make sure if it is possible to continue testing. It is done in(…)

Features of Software Configuration Management

Software Configuration Management is the process of tracking and controlling the software changes. The basic features provided by any SCM tools are as follows: Concurrency Management Version Control Synchronization Let us go through all these features one by one. Concurrency Management When two or more tasks are happening at same time it is known as concurrent operation.(…)

What is Software Configuration Management

A software is a collection of items like programs, data, documents etc. that can be changed easily. Throughout the software development cycle the software design documents, software code or software requirements document etc. are changed often and it is very important that the changes done in software are done in a controlled manner. Software Configuration(…)

Quality Assurance vs Quality Control

Quality Assurance Quality Control 1. Process Driven Approach: It is a process to monitor and improve existing quality processes. 1. Concerned with Product: It measures and controls the quality of the software as it is being developed. 2. Quality Assurance ensures that the processes designed for the product development and services are effective enough to(…)

What is Quality Assurance?

1. Quality Assurance (QA) is a process driven approach, it is a process to monitor and improve existing quality processes. 2. It is a process of verifying whether the software product or services meets or exceeds the customer expectations. 3. It ensures that the product or services are developed or implemented on agreed standards.

How to use
Atlassian Confluence
effectively?

Do you want to learn and standout from others in Software Testing? Enter your email below to get full confluence training for FREE.