Usability testing is a testing methodology where the end customer is asked to use the software to see if the product is easy to use, to see the customer perception and task time. The best way to finalize customer point of view for usability is by using prototype or mock up software during the initial stages. By giving customer prototype before the development startup we confirm that we are not missing anything fro m the user point of view. Prototype and Usability testing
Defect Cascading is a defect which is caused by other defect. So one defect triggers other defect. For instance in the accounting application below there is one defect called negative taxation. So the negative taxation defect affects the Ledger which in turn affects four other modules. Defect cascading
Alpha and Beta testing means different for different people. Alpha testing is the acceptance testing done at the development site. Some organizations have a bit different visualization of Alpha testing. They consider alpha testing as a testing which is conducted on early, unstable version of software. On the contrary Beta testing is acceptance testing conducted at the customer end. In short the difference between Beta testing and Alpha testing is the location where the tests are done. Alpha and Beta testing
In order to understand testing methodology we need to understand the concept of workbench. Work bench is a way of documenting how a specific activity has to be performed. A work bench is referred as phases, steps and tasks as shown in the below figure. Workbench with phases and steps There are four sections for every work bench:- Input: – Every task needs some defined input and entrance criteria. So for every work bench we need defined inputs. Input forms the first steps of the work bench. Execute: – This is the main task of the work bench which will transform the input in to … Click here to continue…..
If a defect is known at the initial stage then it should be removed during that stage / phase itself rather than doing it some later stages. It’s a recorded fact that if a defect is delayed for later phases are proven more costly. Below figure shows how a defect is costly as the phase moves ahead. A defect if identified and removed during the requirement and design phase is the most cost effective, while a defect removed during maintenance is 20 times costlier than requirement and design phases. For instance if a defect is identified during requirement and design we only need to change documentation … Click here to continue…..