There are major four ways of rolling out any project:- Pilot: – Actual production system is installed at a single or to limited number of users. Pilot basically means that the product is actually rolled out to limited users for real work. Gradual Implementation: – In this implementation we ship the entire… Continue reading
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… Continue reading
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… Continue reading
In order to understand testing methodology we need to understand the concept of workbench. Workbench 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… Continue reading
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… Continue reading
Latent defect is an existing defect that has not yet caused a failure just because the exact set of conditions has never been met. Masked defect is an existing defect that hasn’t yet caused a failure, just because another defect has prevented that part of the code from being executed. Below scenario… Continue reading
The product has to be finally used by the user. So he is the most important person as he has highest interest than any one else in the project. From the user we need the following data as shown in the below figure:- The first important thing is the Acceptance test plan… Continue reading
Note: – This question is to check do you really know practically which phase is the most defect prone. Design phase is the more error prone than the execution phase. One of the most frequent defects which occur during design is that, it does not cover the complete requirements of the customer. Second… Continue reading
Note: – This question will normally be asked to judge whether you have traditional or the modern way of testing attitude. In traditional testing methodology (sad to say many companies still have that attitude) testing is always done after the build and execution. But that’s a wrong thinking. Because earlier we catch a… Continue reading