During software testing, as defects are found, analysis of defects can give surprising results!
Defect Clustering in Software Testing means that the majority of the defects are caused by a small number of modules, i.e. the distribution of defects are not across the application but rather centralized in limited sections of the application.
This is particularly true for large systems where the complexity, size, change and developer mistakes can impact the quality of the system and affect particular modules.
Defect Clustering Continue reading “Defect Clustering in Software Testing”
Katalon Studio is a simple and powerful test automation solution for not only web and mobile applications but also web services, a revolution of the Selenium and Appium frameworks. Katalon Studio allows users with less experience in programming to work effortlessly by providing a predefined automation framework with hundreds of built-in keywords. This guide explains all the basic steps, from downloading to activating the build, so that new users can start Katalon Studio for the first time.
Download Katalon Studio
Katalon Studio is available for free, supporting both Windows and Mac. Visit the Katalon Studio website to download the latest version. Continue reading “What is Katalon Studio? How To Installing and Setting up.”
Black Box Testing- Black box testing is a software testing method where testers are not required to know coding or internal structure of the software. Black box testing method relies on testing software with various inputs and validating results against expected output.
White Box Testing-This testing is based on knowledge of the internal logic of an application’s code. Also known as Glass box Testing. Internal software and code working should be known for this type of testing. Tests are based on coverage of code statements, branches, paths, conditions.
Unit testing – Testing of individual software components or modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Continue reading “Types of Software Testing”
It is performed to evaluate the performance of components of a particular system in a specific situation. This type of testing generally does not give pass or fail. It is basically done to set the benchmark & standard of the application against Concurrency / Throughput, Server response time, Latency, Render response time etc. In other words, you can say it is technical & formal evaluation for responsiveness, speed, scalability and stability characteristics. Continue reading “Performance, Load and stress-testing in software testing?”
Verification is static type of s/w testing. It means code is not executed. The product is evaluated by going through the code.
Verification is a static practice of verifying documents, design, code and program. It includes all the activities associated with producing high quality software: inspection, design analysis and specification analysis. It is a relatively objective process.
Verification will help to determine whether the software is of high quality, but it will not ensure that the system is useful. Verification is concerned with whether the system is well-engineered and error-free. Continue reading “Verification And Validation”
All testers have asked themselves this question at some point in their career. When do I stop testing a product and consider the job done?
You Can’t determine when to stop testing. Now a days software applications are so complex and should run in a interdependent environment that complete 100 % testing can never be done. Few things are there to stop…. There are some markers that help us in determining the closure of the testing phase of software development life cycle. Continue reading “When do I STOP testing?(Exit Criteria in Software Testing)”
A defect life cycle is the movement of a bug or defect in different stages of its lifetime, right from the beginning when it is first identified till the time is marked as verified and closed.
Depending on the defect management tool used and the organisation, we can have different states as well different nomenclature for the states in the defect life cycle.
- New – A bug or defect when detected is in New state.
- Assigned – The newly detected bug when assigned to the corresponding developer is in Assigned state.
- Open – When the developer works on the bug, the bug lies in Open state.
- Rejected – A bug lies in rejected state in case the developer feels the bug is not genuine.
- Deferred – A deferred bug is one, fix of which is deferred for some time(for the next releases) based on urgency and criticality of the bug.
- Duplicate – If the bug is repeated twice or the two bugs mention the same concept of the bug, then the recent/latest bug status is changed to duplicate.
- Fixed – When a bug is resolved by the developer it is marked as fixed and assigned to the tester.
- Reopen – If the tester is not satisfied with issue resolution the bug is moved to Reopen state.
- Retest: At this stage the tester do the retesting of the changed code which developer has given to him to check whether the defect got fixed or not
- Close – After the bug is verified, it is moved to Close status.
Error: Error is a human action that produces an incorrect result.
Error means normally arises in software Error means to change the functionality of the program.
This could be happen because of confusion in understand requirement.
Bug: Bugs arise from mistakes and errors, made by people, in either a program’s
source code or its design.
Simply Bug is an error found BEFORE the application goes into production.
Defect: It is the difference between expected and actual result in the context of testing.
Defect is the deviation of the customer requirement.
Failure:It is the inability of a system or a component to perform its required functions within specified performance requirements.
Failure occurs when fault executes.
When I started the 8-Week ago to writing a blog Challenge, I had no idea what the response might be. I was amazed when about around 150 people see this everyday.It seems that there is a quiet revolution in progress.
So Today i will write short article on Agile Methodology in software testing.
Agile is an iterative development methodology, where requirements evolve through collaboration between the customer and organization team. Continue reading “Agile Methodology”
In This Tutorial, we would be discussing about the installation procedure of Automation Tool Selenium webdrive
To be able to use WebDriver for run test cases, there are some prerequisites that need to be in place like the basic environment setup as follows.
Step 1:First Install Java on your machine from here and it will be open below page and download JDK.
Next page looks like below.. Continue reading “WebDriver Setup and Installation”