Software Testing Models



How to Design Test Cases Using State Transition Testing Technique?

(adsbygoogle = window.adsbygoogle || []).push({});

In the previous article we have seen about “How to Design Test Cases Using Cause and Effect Graph Testing Technique” Similar way in today’s article we are learning one more interesting test technique used in the software testing called “State transition testing technique”.

State transition testing is a form of Dynamic Testing Technique that comes in use when the system explained as a finite number of states and the

Continue reading →

What is Cause and Effect Graph Testing Technique - How to Design Test Cases With Example?

Cause-Effect flow diagram

Cause-Effect Graph graphically shows the connection between a given outcome and all issues that manipulate the outcome. Cause Effect Graph is a black box testing technique. It is also known as Ishikawa diagram because of the way it looks, invented by Kaoru Ishikawa or fish bone diagram.

It is generally uses for hardware testing but now adapted to software testing, usually tests external behavior of a system. It is a testing technique that aids in

Continue reading →

What is Risk Based Testing in Software testing?

Risk Based Testing Approach

Today’s article is going to be a complete guide to learn Risk Based Testing in Software testing. Before explaining Risk based testing, it is necessary to know what mean by Risk in software testing. A Risk is a problem or situation that has not happened yet and it may never happen in future as well. It is basically a possible problem.

In this article we understand what is risk based testing, reasons & situations to

Continue reading →

Positive and Negative Testing In Software Testing

Positive and Negative Testing In Software Testing

Software testing is process of Verification and Validation to check whether software application under test is working as expected. To test the application we need to give some input and check if getting result as per mentioned in the requirements or not. This testing activity is carried out to find the defects in the code & improve the quality of software application. Testing of application can be carried out in two different ways,

Continue reading →

Difference between Regression Testing vs Retesting?

Difference between Retesting and Regression Testing

Next commonly ask interview question in any software testing interview is “What is difference between Regression Testing and Retesting?” Regression testing and Retesting have different objectives and priorities, they equally important for project’s success.

 

Definition of Retesting and Regression Testing:

Re-Testing: After a defect is detected and fixed, the software should be retested to confirm that the original defect has been successfully removed. This is called Confirmation Testing or Re-Testing

Regression testing: Testing your

Continue reading →

What is Globalization, Internationalization and Localization in Software Testing?

What is Globalization Internationalization and Localization?

In Today’s competitive world many of the clients are targeting the global audience, which means going beyond borders and working with clients to make sure application has proper global sets in terms of functional, readable, and viewable in multiple platforms and cross-browsers. Along with that there are many languages in the world, so in this situation do we need to create a separate application or website for each languages & countries? The answer is NO.

Continue reading →

Key to Successful BVT – How to run the Build Verification Test?

BVT (Build Verification Test)

What is BVT (Build Verification Test)?

Build Verification Test is a set of pre-defined test cases run on every build to make sure that build is testable for further testing. BVT test is carried out before build pass to testing team for further testing. This test contains pre-defined Test Cases which focus on the core functionality of software application to make sure that build is stable & ok to start with actual testing. This test

Continue reading →

Why testing should start early in software development life cycle?

Software Development Life Cycle Planning

One of the software testing principles say that “Start Testing Early” in the software development life cycle, so in this article we will see what all advantages & practical reasons if we start testing early in SDLC.

It has been observed that most of the errors are identified in the testing phase which is already introduced in the requirement or design phase. Defects identified later in SDLC are expensive to fix than defects identified in

Continue reading →

Top 10 reasons why there are Bugs in Software!

Top 10 reasons why there are Bugs in Software!

Many of the testers are thinking that why these bugs are introduced in the code or why developer leaves the bugs in the code. I think this is contradictory type of question means if no introduction of errors in the code then there is no need of testing of software, just develop the defect free software application & use it without testing. This is not practicable, if the complexity of the software application increased then

Continue reading →

Defect Priority

What is Defect Priority?

Defect Priority signifies how important & urgently it is to fix this defect. In other words Priority means how fast it has to be fixed. The Defect priority status is set by the project manager based on the customer requirements & based on Project Priorities the product fixes are done. Priority is related to scheduling to resolve the problem. It is a pointer towards the importance of the bug & if

Continue reading →