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



  • Software Quality Terms , Testing glossary

    Software quality Terminologies contain a variety of common software testing terms used so that any beginner can be familiar with the common glossary of software testing .So below are few common software testing terms.

    Quality:

    The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations.

    Software quality: 

    Totality of functionality and features of a software product that bear on its ability to satisfy stated or implied needs is known as software quality.

    Cost of quality

    The total costs incurred on quality activities and issues ,often split into prevention costs, appraisal costs, internal failure costs and external failure costs.

    Software Testing terms- Cost of Quality

    Testing

        • Process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs), and to evaluate the features of the software item (Ref. IEEE Std 829).
        • Process of operating a system or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component.

    Software Testing:

    A set of activities conducted with the intent of finding errors in software.

    Software Quality bug

    Bugs

    A bug is an error or defect in software or hardware that causes a program to malfunction.This is one of the common and useful term in Software Testing Terminologies.

    Defect:

    The variation between the actual results and expected results is known as defect.

    Error:

    A mistake in the system under test; usually but not always a coding mistake on the part of the developer.

    Failure-

    After release of Product, if an end user finds an issue then that particular issue is called as failure.

    Coding:

    Generation of source code is called Coding.

    Debugging: 

    The process of identifying and removing errors from computer hardware or software.

    Test Scenario:

     A concept, which provides a short information about what to test.

     Test Case:

        •   Concept which provides detailed information what to test, steps to be taken and expected result of the same.
        •   Set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.

    Test Script:

    It is written in a programming language and it’s a short program used to test part of functionality of the software system. In other words a written set of steps that should be performed manually.

    Test Suite:

    A collection of tests used to validate the behaviour of a product.

    Or Test Suite is a list of related test cases. Suite may contain common initialisation and cleanup routines specific to the cases included.

    Test Plan:

    Document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning. Ref IEEE Std 829.

    Test Procedure:

     Test procedure is about how tester physically run the test cases, set-up the test required and execute procedure step that needs to be followed.

    Test Specification: 

    A document specifying the test approach for a software feature or features and the inputs, predicted results and execution conditions for the associated tests.

    Use Case: 

    The specification of tests that are conducted from the end-user perspective and it is a method for identifying, articulating, and arranging system requirements in software development

    Metric:

    A standard of measurement. Software metrics are the statistics describing the structure or content of a program. A metric should be a real objective measurement of something such as number of bugs per lines of code.

    Quality Control:

     QC Refers to a system of inspecting the final quality of the product so Basically it is product oriented

    Quality Analysis:

     Set of activities for ensuring high-quality products by preventing any defects that may occur in the development process.

    Traceability Matrix: 

    A document which is showing the relationship between Test Requirements and Test Cases.

    Validation:

    It is the process of evaluating software at the end of the development process to determine whether software meets the customer expectations and requirements.

    This is one of the common term used in Software Testing Terminologies.

    Verification:

    Process of evaluating products of a development phase to find out whether they meet the specified requirements.

    Test Basis:

    It is defined as the source of information or the document that is required to write test cases and also for test analysis.

    Test Object :

    The component or system to be tested.

    Test Items:

    The individual element to be tested. There usually is one test object and many test items.

    System under Test (SUT) :

    It refers to a system that is being tested for correct operation. The term is used mostly in software testing.

    Automation Testing

    It describes a form of testing where a computer runs the tests instead of a human ,  it can be performed using special automated testing software tools to execute a test case suite

    Exhaustive Testing

    This testing covers all possible inputs and outputs.

    Exploratory testing

    It is based on the tester’s experience; the tester creates the tests while he/she gets to know the system and executes the tests.

    ISTQB

    ISTQB stands for International Software Testing Qualifications Board. It  is responsible for international programs for testing certification.

    IEEE 829

    An international standard for test documentation published by the IEEE organization.

    It includes templates for the test plan, various test reports etc

    Severity

    impact of a particular defect on the software.

    Priority

    Urgency of fixing the defect.

    Recommended Articles:


















  • Leave a Reply

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

    Scroll to Top