Tutorials Hut

Tutorials Hut

  • Testing Foundation

      Basics of Software Testing
       What is Software Testing?
       Objective of Testing
       Why is testing necessary?
       Common Terms used in Testing
       Verification Vs Validations
       QA Vs QC
       Debugging Vs Testing
       Seven Testing Principles
       SDLC Vs STLC
       Fundamentals of Test Process
       Software quality Factors
       Software Development Models
       Waterfall Model
       V models
       Iterative Model
       Test Levels
       Component Testing
       Integration Testing
       System Testing
       Acceptance Testing
       Strategies for Integration Testing
       Big Bang
       Stubs and Driver
       Top Down Testing
       Bottom Up Testing
       Test Types
       Functional Testing
       Non- Functional Testing
       Structural Testing
       Re-testing & Regression Testing
       Static AND Dynamic Techniques
       Static Technique
       Dynamic Technique
       Static Analysis by Tools
       White Box Techniques
       Statement Coverage Testing
       Branch Coverage Testing
       Decision Coverage Testing
       Path Coverage
       Black Box Techniques
       Equivalence Partitioning
       Boundary Value Analysis
       Decision Table testing
       State Transition testing
       Experience Based TestingTechniques
       Random Testing
       Exploratory Testing
       Error Guessing
       Functional Testing
       Integration Testing
       Unit Testing
       System Testing
       Smoke testing
       Sanity testing
       Regression Testing
       Usability Testing
       Security Testing
       User Acceptance Testing
       White Box & Black Box Testing
       Globalization & Localization Testing
       Non Functional Testing
       Compatibility testing
       Endurance testing
       Load testing
       Performance testing
       Recovery testing
       Scalability testing
       Stress testing
       Volume testing
       Test Planning and Estimation
       Test Planning
       Test Strategies Vs Test Plan
       Test Approaches
       Risk and Testing
       Product Risks
       Project Risks
       Defect Management
       Defect LifeCycle
       Severity Vs Priority



  • Debugging

    Debugging and Testing :Definition and Difference

    What is Debugging?

    Debugging is a process to detect and remove existing and potential bugs in a software that can lead to failure. Debugging is used to find the issue and resolve it.

     

    Development team receives defects identified by the testing team which they start debugging.

      • The purpose of this phase is to locate the bug and rids the software of it. 

    For its effective outcome developer should:

      • Set Bug Priority
      • Reproduce the Bug
      • Avoid assumptions

    Debugging Process

    To make the software programs or products defect-free, below process should be done before releasing them into the market. Below are steps involved in this process are,

      • Identifying the error – It saves time and avoids the errors . Finding errors at an earlier stage helps to reduce the number of errors and wastage of time.
      • Identifying the error location – The exact location of the error should be found to fix the defect faster and execute the code.
      • Examine the error – To understand the type of defect and reduce the number of errors we need to analyze the error. Solving one bug may lead to another bug that stops the application process.
      • Prove the analysis – Once the error has been analyzed, we need to prove the analysis. It uses a test automation process to write the test cases through the test framework.
      • Cover the lateral damage – The bugs can be resolved by making the appropriate changes and move onto the next stages of the code or programs to fix the other errors.
      • Fix and Validate – This is the final stage to check all the new errors, changes in the software or program and executes the application.

    What is Testing?

      • Testing is a process of checking the system under test is working as per requirements and find defects present in the software. 
      • Testing is done by the tester to identify the defects in the system (actual result of test case execution is not matching with expected result) and report the issues found to the developer team for debugging and fixing.
      • Testing is the process of verifying a system with the purpose of identifying any errors, gaps or missing requirements versus the actual requirement.

    A software test process consists of the activities listed below:

        1. Planning and control
        2. Analysis and design
        3. Implementation and execution
        4. Meeting exit criteria
        5. Test closure activities

    Difference between Debugging and Testing ( Debugging vs Testing)

    ParametersDebuggingTesting
    Purpose Locate and correct bugs found during testing.Find bugs and errors.
    Person ResponsibleDone by a programmer or developer.Testing is done by the tester.
    Nature of processIt is the process which cannot be forced. It is a deductive process.Testing is the process which can be planned, designed and executed.
    AutomatedIt cannot be automated.Most of the test cases in testing can be automated.
    PlannedIt is the process which cannot be forced.Testing is the process which can be planned, designed and executed.
    Person ResponsibleDebugging is done by a programmer or developer.Testing is done by the tester.
    Design KnowledgeDetailed design knowledge is required to perform debugging.Most of the testing can be done without design knowledge.
    Outsourcing ActivityCannot be outsourced to outside teams. It must be done by the inside development team.Testing can be outsourced.
    Recommended Articles:  



  • Testing Foundation

      Basics of Software Testing
       What is Software Testing?
       Objective of Testing
       Why is testing necessary?
       Common Terms used in Testing
       Verification Vs Validations
       QA Vs QC
       Debugging Vs Testing
       Seven Testing Principles
       SDLC Vs STLC
       Fundamentals of Test Process
       Software quality Factors
       Software Development Models
       Waterfall Model
       V models
       Iterative Model
       Test Levels
       Component Testing
       Integration Testing
       System Testing
       Acceptance Testing
       Strategies for Integration Testing
       Big Bang
       Stubs and Driver
       Top Down Testing
       Bottom Up Testing
       Test Types
       Functional Testing
       Non- Functional Testing
       Structural Testing
       Re-testing & Regression Testing
       Static AND Dynamic Techniques
       Static Technique
       Dynamic Technique
       Static Analysis by Tools
       White Box Techniques
       Statement Coverage Testing
       Branch Coverage Testing
       Decision Coverage Testing
       Path Coverage
       Black Box Techniques
       Equivalence Partitioning
       Boundary Value Analysis
       Decision Table testing
       State Transition testing
       Experience Based TestingTechniques
       Random Testing
       Exploratory Testing
       Error Guessing
       Functional Testing
       Integration Testing
       Unit Testing
       System Testing
       Smoke testing
       Sanity testing
       Regression Testing
       Usability Testing
       Security Testing
       User Acceptance Testing
       White Box & Black Box Testing
       Globalization & Localization Testing
       Non Functional Testing
       Compatibility testing
       Endurance testing
       Load testing
       Performance testing
       Recovery testing
       Scalability testing
       Stress testing
       Volume testing
       Test Planning and Estimation
       Test Planning
       Test Strategies Vs Test Plan
       Test Approaches
       Risk and Testing
       Product Risks
       Project Risks
       Defect Management
       Defect LifeCycle
       Severity Vs Priority

















  • Leave a Reply

    Your email address will not be published. Required fields are marked *

    Scroll to Top