world at a GlanCE

System Testing: - After completion of integration testing, a separate testing team receives a software build from the development team. This team a set of block box testing techniques to validate that software build the system testing is satisfied into 3 categories. 1. Usability testing 2. Functional Testing 3. Non Functional Testing 1.Usability Testing: In general, the separate testing team starts test execution with usability testing. During this test, the team concentrates on user-friendliness of the software build screens. The usability testing consists of 2 sub tests. a) User  Interface Testing b) Manuals Support Testing a) User - interface Testing: - In User Interface Testing software build is tested for ‰ Ease of use (Understandability) ‰ Look & Feel (Attractiveness) ‰ Speed in Interface (Short navigations) These are applied on every screen in the software build. b) Manuals Support Testing: - Also known as Help - documents testing. During this test, the testing team co...

Integration Testing: After completion of dependent programs development & Unit testing, the programmers interconnect them. Then the programmers verify the interconnection of the programs in any one of the below four ways. 1. Top-Down Approach 2. Bottom-Up Approach 3. Hybrid Approach 4. System Approach 1.Top-Down Approach: The interconnection of the main program & some sub-programs is called the Top-Down Approach. Programmers use temporary programs called stubs instead of sub-programs, which are under construction. The other name for stubs is Called Programs. A stub returns the control to the main program. * In this Approach first Parent Modules are developed * After that Child Modules are developed * Then interconnect Parent & Child Modules. * In the interconnection process is there any the sub-module is under construction then the developers create temporary program Instead of sub modules that is called Stub. 2.Bottom  Up Approach: The interconnection of interna...