Software Testing Basics

BLACK BOX TESTING  is  as defined as a testing technique in which functionality of Application  is tested without looking at the internal code and details of the software. This type of testing is based entirely on software requirements and specifications. In BlackBox Testing we just focus on inputs and output of the software system without bothering about internal knowledge of the software. This can be both Functional or Non-Functional FUNCTIONAL TESTING: In functional testing  actions or functions of the system are being tested by providing the input and comparing the actual output with the expected output. Few major types of Functional Testing are: Smoke Testing Sanity Testing Integration Testing System Testing Regression Testing User Acceptance Testing NON- FUNCTIONAL TESTING: There are several non-functional aspects as well that are required to be tested to improve the quality and performance of the application. Few major types of Non-Functional Testing include: Usability Testing L

DIFFERENCE BETWEEN DEFECT , BUG, ERROR AND FAILURE  DEFECT: If  difference exist  between actual result and expected result  and that difference is found by developer and  corrected by himself in the development phase then it’s called a defect.   Example if developer  has developed  a code  and while performing (Unit Testing) developed  found that the code is not functioning  as per requirement  then in tat case the issue occurred  is known as DEFECT. BUG: If testers find any mismatch in the application/system in testing phase then they call it as Bug. Example if the developer has done the development  and performed Unit testing of a login form then the module is sent to Tester for performing testing. In this phase if tester found that the client requirement is not matching with the  result of application then tester report it as Bug.  NOTE:  there is a contradiction in the usage of Bug and Defect. People widely say the bug is an informal name for the defect. ERROR If we can’t compile

What is a Bug? In Software testing, when the expected result and actual result is not matching, an incident needs to be raised. That incident may be a Bug. .                       ACTUAL RESULT  ≠ EXPECTED RESULT = BUG/ ERROR/DEFECT Bug is occurred by  programmer's fault or mistake. And this has to be found by tester and get it corrected in order to maintain accuracy of software. For this Bug has a defined life cycle through which it has to undergo. Life Cycle of a Bug: The different states of a bug in the bug life cycle are as follows: New:  When a tester finds a new defect. He should provide a proper Defect document to the Development team to reproduce and fix the defect. In this state, the status of the defect posted by tester is “New” Assigned :  Defects which are in the status of New will be approved By (if valid) and assigned to the development team by Test Lead/Project Lead/Project Manager. Once the defect is assigned then the status of the bug changes to “Assigned” Open:  

What is Software Testing? SOFTWARE TESTING  is defined as  activity to check whether the A ctual results match the Expected results  and to ensure that the software system is  Defect / Bug  free ( as per customer requirement) .  Software testing also helps to identify errors, gaps, or missing requirements in contrary to the actual requirements. It can be either done manually or using automated tools. Some prefer saying Software testing as a  White Box  (Testing done by Analyzing code) and  Black Box Testing (Testing done by Analyzing application as per user without digging into the code. Example Verifying login form of application). In simple terms, Software Testing means the Verification of Application Under Test (AUT). Importance of Software Testing  Normal Trend  - --In today's time there are plenty of startups and low budget software companies who donot prefer Software Tester in their company  as it is a extra burden as per wages and other extra facility which they have to prov

STLC(SOFTWARE TESTING LIFE CYCLE) It is a sequence of specific activities conducted during the testing process to ensure software quality goals are met. STLC involves both verification and validation activities. Contrary to popular belief, Software Testing is not just a single/isolate activity, i.e. testing. It consists of a series of activities carried out methodologically to help certify your software product. STLC stands for Software Testing Life Cycle. PHASES OF STLC : Requirement Analysis Test Planning Test case development Test Environment setup Test Execution Test Cycle closure What is Entry and Exit Criteria? Entry Criteria:  Entry Criteria gives the prerequisite items that must be completed before testing can begin. Exit Criteria:  Exit Criteria defines the items that must be completed before testing can be concluded. Requirement Analysis During this phase, test team studies the requirements from a testing point of view to identify the testable requirements. The QA team may in

A software life cycle model is a descriptive representation of the software development cycle. SDLC models might have a different approach but the basic phases and activity remain the same for all the models. 1) Waterfall Model 2) V-Shaped Model 3) Prototype Model 4) Spiral Model 5) Iterative Incremental Model  6) Big Bang Model 7) Agile Model Waterfall Model The  Waterfall Model  was the first Process Model to be introduced. It is very simple to understand and use it. In a  Waterfall  model, each phase must be completed before the next phase can begin and there is no overlapping in the phases.  The waterfall  model is the earliest  SDLC   approach that was used for software development. n “ The Waterfall ” approach, the whole process of  software development  is divided into separate phases. The outcome of one phase acts as the input for the next phase sequentially. This means that any phase in the development process begins only if the previous phase is complete. The waterfall model