• Quality,  Software Testing

    Build Status Report

    Build Status Report We may receive multiple builds for a project, so for each build, we have to prepare the below Test Report and we need to send this build status report to the Lead or Project Manager. Test Matrix: Matrix means the measurement of the Task, so Test Matrix means the measurement of the Testing.   Pending: If the Developer has not given the functionality in the build then Tester can’t execute those Test Cases, so it comes under Pending.   Skipped: If some Test cases fail and due that failure we are unable to execute the dependent test cases, so those test cases come under Skipped. Example: In…

  • Bug Life Cycle
    Quality,  Software Testing

    BUG LIFE CYCLE

    Bug Life Cycle (BLC) is the life cycle of the bug from finding a New bug to Closed that bug. First of all when a new build Release from the Development Team to the Testing Team. Testing Team performs Testing on the build. If No any bug found in the build then that stable build delivered to the Client. If any bug found in the build then the Status of that bug will be New and Testing Team send that bug to the Development Team. Development Team will check that bug according to the given bug description from the Testing Team. If Development Team found that reported bug is a…

  • Result Analysis
    Quality,  Software Testing

    Result Analysis

    Test Result Analysis: While executing the Test Cases, the Test Engineer do result analysis by comparing the Actual result with Expected result. If both the results are matching, then Test Engineer will update the Result as Pass under the Result column of Test Case Template. If the Actual Test result and Expected Test result are not matching to each other, then Test Engineer will update the Result as Fail under Result column of Test Case Template. The same process will continue for all the Test Cases. For Pass Test Cases will provide Green colour whereas for Fail Test Cases will provide Red Colour in the Test Template. If any Test…

  • Test Case Execution
    Quality,  Software Testing

    Test Case Execution

    After preparing all the Test Cases in the Test Template for all the Requirements, the phase Test Case Execution will conduct by the Testing Team. Once all the Test Cases are baselined, Testing Team wait for the build: Once the build is released from the Development Team to Testing Team, so the build will deploy in Test Environment, then the Testing Team will perform Sanity Test first. Once the Sanity Test on the build is pass, then the Testing Team will execute all the prepared Test Cases for the build according to the Test Steps. The Sanity Test results will be sent to the Development Team also. Testing Team will…

  • STLC - Software Testing Life Cycle Part - 1 Software Testing Plan
    Quality,  Software Testing

    STLC – Software Testing Life Cycle

    STLC – Software Testing Life Cycle contains below phases: Software Testing Plan Software Testing Design  Test Case Execution  Result & Analysis  Reporting & BLC (Bug Life Cycle) Delivery & Maintenance Test Summary Report   Software Test Plan: The plan is a strategic document which describes how to perform one task in an effective and efficient manner. Software Test Plan is also a strategic document which describes how to perform Testing in an effective and efficient manner. The Test Lead will prepare the Test Plan. Once it has prepared then it will send to the Testing Team for review.   Please click here to view details of Software Test Plan Please…

  • Regression Testing and Re - Testing
    Quality,  Software Testing

    Regression Testing and Re – Testing

    Regression Testing: Testing already tested functionalities on the Iterative and Incremental builds is known as Regression Testing. It will be performed in two ways: Whenever the bug is identified, it will be reported to the developer. The developer will fix it and send it back to the Testing team. The Test Engineer will check whether the bug is really fixed or not. The Test Cases which are passed in the previous build will be tested again on the new build and check whether passed Test Cases working same as previous or not. Testing already tested functionalities is Regression Testing, Testing the new functionalities is not Regression Testing, it comes under…

  • Software Test Plan
    Quality,  Software Testing

    Software Test Plan

    Software Test Plan Software Test Plan is a strategic document in which it has explained that how the testing will be conduct on the particular software project. It is very necessary to know about this plan because it gives the clear idea of about every phase of testing. Objectives and Scope: This document provides a high level view of the type of test that is scheduled to be carried out and the features that will and will not be tested. The objective of this document is to test the functionality of the XXXX Application. Features to be tested: The features which are to be tested are: Admin Merchant Delivery system…