An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower-level components being simulated by stubs. Tested components are then used to test lower-level components. The process is repeated until the lowest level components have been tested. In this approach, testing is conducted from the main module to the submodule. if the submodule is not developed a temporary program called STUB is used for simulating the submodule. Advantages: * Advantageous if major flaws occur toward the top of the program. * Once the I/O functions are added, the representation Read More
Bottom Up Integration Testing
An approach to integration testing where the lowest level components are tested first then used to facilitate the testing of higher-level components. The process is repeated until the component at the top of the hierarchy is tested. In this approach, testing is conducted from the submodule to the main module, if the main module is not developed a temporary program called DRIVERS is used to simulate the main module. Advantages: * Advantageous if major flaws occur toward the bottom of the program. * Test conditions are easier to create. * Observation of test results is easier. Disadvantages: * Driver Modules Read More
Branch testing
Branch Testing/ Decision Coverage: Test coverage criteria require enough test cases such that each condition in a decision takes on all possible outcomes at least once, and each point of entry to a program or subroutine is invoked at least once. That is, every branch (decision) taken each way, true and false. It helps in validating all the branches in the code making sure that no branch leads to abnormal behavior of the application. Formula: Branch Testing=(Number of decisions outcomes tested / Total Number of decision Outcomes) x 100 % A branch is the outcome of a decision, so branch Read More
Accessibility Testing
What is Accessibility Testing? Accessibility testing is the technique of making sure that your product is accessibility compliant. There could be many reasons why your product needs to be accessibility compliant as stated above. Accessibility testing is a type of systems testing designed to determine whether individuals with disabilities will be able to use the system in question, which could be software, hardware, or some other type of system. Disabilities encompass a wide range of physical problems, including learning disabilities as well as difficulties with sight, hearing, and movement. Why accessibility Testing?Typical accessibility problems can be classified into the Read More
Acceptance testing
Acceptance testing, a testing technique performed to determine whether or not the software system has met the required specifications. The main purpose of this test is to evaluate the system’s compliance with the business requirements and verify if it is has met the required criteria for delivery to end-users. After the system test has corrected all or most defects, the system will be delivered to the user or customer for acceptance testing. Acceptance testing is basically done by the user or customer although other stakeholders may be involved as well. The goal of acceptance testing is to establish confidence in Read More
Adhoc Testing
Adhoc testing is an informal testing type to break the system. This testing is usually an unplanned activity. It does not follow any test design techniques to create test cases. In fact is does not create test cases altogether! This testing is primarily performed if the knowledge of testers in the system under test is very high. Testers randomly test the application without any test cases or any business requirement document. Adhoc Testing does not follow any structured way of testing and it is randomly done on any part of the application. The main aim of this testing Read More