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

  • Decision Table Testing and State Transition Testing

    Decision Table Testing and State Transition testing are very much helpful in test design technique.

    Decision Table is also known as Cause-Effect Table. In this technique ,we will deal with combinations of inputs.

    We are explaining the most important manual software testing techniques.

    The topics discussed in this article are:

    Decision Table Testing

    What is Decision table?

        • A table showing combinations of inputs for testing the system behaviour
        • Or it is a systematic approach where the different input combinations and their corresponding system behaviour are captured in a tabular form.
        • Decision tables are very much helpful in test design technique.
        • Any complex business flow can be easily converted into the test scenarios & test cases using this technique with the help of decision table

    Decision table testing

        • A black-box test design technique in which test cases are designed to execute the combinations of inputs and their corresponding behaviour shown in a decision table.
        • It is referred to as a ’cause-effect’ table
        • Each column can then be considered as a test case of a business rule
        • It is good for testing business rules or combinations
        • Contains conditions (Input) and actions (Outputs)

    Advantages of Decision Table Testing:

        • It identifies if any gaps in the requirements.
        • Conversion of complex business rules into simple decisions tables.
        • Ideal for classification or discrete-regression.

    Lets take an example of Facebook page for clear understanding

    Decision Table testing

     No of test cases/sets =     No of unique values in condition 1 * No of unique values in condition 2 = 3* 3 = 9 Test cases

    State Transition Testing

          • A black box testing technique
          • State-transition diagrams are very useful for describing the behaviour of a system and are part of the Software Design Document.
          • Tests are designed to execute valid and invalid state transitions
          • State-Transition diagrams are an excellent tool to capture certain types of system requirements and to document internal system design.
          • This technique is used when features of a system are represented as states, which transform to another state.

    Deals With:

          • Sequence of Events
          • Handling of Events depending on Events and Conditions that occurred in the past

    Important terms

          • State: a condition in which a system is waiting for events
          • Event: Input that may cause a transition
          • Transition: Change from one state to another as result of event
          • Action: operation initiated by transition

    State diagram:

     It represents the states that a component can assume and shows the events that cause and/or result from a change from one state to another


         Recommended Articles:  

  • Leave a Reply

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

    Scroll to Top