1. What are the Testing metrics?
A. There are several test metrics identified as part of the overall testing activity in order to track and measure the entire testing process. These test metrics are collected at each phase of the testing life cycle /SDLC and analyzed and appropriate process improvements are determined and implemented as a result of these test metrics that are constantly collected and evaluated as a parallel activity together with testing both for manual and automated testing irrespective of the type of application. The test metrics can be broadly classified into the following three categories such as:
Project Related Metrics – such as Test Size, # of Test Cases tested per day –Automated (NTTA), # of Test Cases tested per day –Manual (NTTM), # of Test Cases created per day – Manual (TCED), Total number of review defects (RD), Total number of testing defects (TD), etc
Process Related Metrics – such as Schedule Adherence (SA), Effort Variance (EV), Schedule Slippage (SS), Test Cases and Scripts Rework Effort, etc.
Customer related Metrics – such as Percentage of defects leaked per release (PDLPR), Percentage of automation per release (PAPR), Application Stability Index (ASI), etc
2. What are the difficulties if you do testing without test cases?
A. Test Cases would provide formal way of performing testing, which contribute for the expected requirements coverage without test case design;
- Expectations may not be clear
- Possibility of missing some of the test scenarios
- Test Data not documented and hence no proper impact on the functionalities.
- Test execution can be initiated by testers without 100% system knowledge.
It cannot guaranty the expected test coverage
3. What are the fields in Defect report?
A . The defect report will have
- Defect ID
- Assigned To
- Detected By
- Resolution Type
- Fixed By
- Build Ver
- Repro Steps
- Release Ver
4. How important is the user Interface testing on the web applications and how do you perform?
A. User Interface can be defined as the interaction between the user and the computer. That is the first point of contact between the user and the application. On a broader perspective, User interface testing involves testing the external features of the application (excluding its functionality). By this we mean testing the components in the application like objects, images, hyperlinks, contents, buttons etc. Testing of the user interface is very essential in the whole SDLC as the end user would be concerned only on the user interface and not on the 1000 lines of brilliantly written code. User interface results in developing perceptions about the application. A single simple defect in the user interface could suppress the entire effort put in the development of the application.
User Interface testing of a web application involves testing the following components present:
- Text present in every page.
- All links in a page.
- All the images present in all the pages.
- Layout provided for each region in a page.
- Text displayed in the drop-down.
Contents in tool tip.
5 What is smoke testing?
A. A quick and initial test to make sure the system can operate and process at least a minimal workload. It is a good idea to use a smoke test as entry criteria into feature testing, in order to ensure that the system is testable, and to avoid wasting time trying to test a system, which fails frequently.
6. What is adhoc testing?
A. A random and informal test performed based on the experience, this would be conducted at later stages in the test execution life cycle since the test case execution may not provide 100 % test coverage.
We would use this test to improve test coverage by identifying the defects, which are uncovered by the test cases.
7. What is peer review?
A. It is an informal review process used for work product evaluation.
- Document the review comments
- Defined fault-detection process
- Includes peers and technical experts
- No Management participation
8. What is performance testing?
A. Testing conducted to evaluate the compliance of a system or component with specified performance requirements.
In other words, testing conducted to measure several system characteristics such as processing speed, response time, resource consumption, throughput, system threshold limits and efficiency