| |
181. What Is Pair Programming?
Date Posted: 06/27/2012
This is a software development methodology where two people sit and do the programming. One programmer develops the code and the other one analyzes the code for effectiveness of logic, adherence to coding standards and syntax errors. The idea is if two people sit together and code, the code is very effective and is of a good quality.
Though the initial response was good for this methodology it’s not that much successful due to issues among the pair that participated in extreme programming. Some of the issues observed were time adjustment, prolonged arguments etc.
|
| |
| |
182. How Does Testing Save The Maintenance Effort?
Date Posted: 06/27/2012
If the project is well tested the number of defects identified in the maintenance phase will be less. Hence the effort to be invested to solve customer issues is less. Less effort means less budget and less cost. So by having an effective testing before releasing the project, we can reduce the effort involved in the maintenance phase and hence save the cost.
|
| |
| |
183. What Is EOL?
Date Posted: 06/27/2012
EOL means end of life of the project. This means after the EOL, no support will be provided for the bugs reported by the customer. In other words the maintenance phase of the project is completed.
|
| |
| |
184. What Are The Activities Of The Test Engineer In The Maintenance Phase?
Date Posted: 06/27/2012
Maintenance activity
Types of testing conducted
Hot fix
Hot fix retesting
Regression testing
Hot fix installation
Patches
Retesting of bugs fixed in the patch
Regression testing
Patch installation testing
Functional testing
Service pack
Retesting
Regression testing
Functional testing
Performance testing
Service pack installation testing
|
| |
| |
185. What Is Patch?
Date Posted: 06/27/2012
Patch is small software that contains fixes for one or more bugs identified in the application. Patches are released to customers by the vendor of the software with solutions for the issues identified in the product during the maintenance.
|
| |
| |
186. What Is Desk Check?
Date Posted: 06/27/2012
Ans: This is an informal review where a colleague comes to the desk/computer of author and quickly goes through the work product along with the author and also shares comments while going through it.
|
| |
| |
187. How Much Information You Can Review In One Day?
Date Posted: 06/27/2012
Ans: Per hour we review around 20 pages if it is document and 200 lines if it is code.
|
| |
| |
188. Explain What Do You Document During The Review Process?
Date Posted: 06/27/2012
Ans: We document page and line numbers of defect, origin of defect, severity of defect. We also document other information like work product ID, reviewers.
|
| |
| |
189. What Kind Of Bugs You Can Find During Static Testing?
Date Posted: 06/27/2012
Ans: The following kind of bugs can be found in static testing
Efficiency of logic
Memory leaks
Unreachable code
Variables that are never used
Programming standards violations
|
| |
| |
190. What Is The Difference Between Testing Techniques And Testing Types?
Date Posted: 06/27/2012
Ans: Testing techniques refers to white box and black box where as testing types refers to functional and non functional testing.
|
| |
