Metrics means measurement. Metrics is just a series of measurements.
|
| Test Matrices Sample |  | ___________________________________ |
|
| Question: I need information about Metrics, which is used to find faults. it is something related with measurement. I need to know how it is used in Quality Assurance. Answer: You can measure the arrival and departure times of developers, if you have them clock in, but that won't tell you much since not all work is done in the office (and it doesn't mean that they're working when they're in the office). This is, however, still a metric. The same holds for a true "quality metric". The most familiar one is defects per thousand lines of (uncommented) code. But this metric assumes that: 1) you count the lines of code 2) the complexity of the code isn't an issue 3) the programmers aren't playing games (like using continuance characters so that what could have been written in one line isn't done in five lines) 4) all defects are uncovered in the code in a single pass 5) each defect discovered is all others 6) defects are uncovered in a linear manner between revisions or builds The fact is that first you need to know what your goal is. Then you need to discover or create a metric that will help you achieve that goal. Then you need to implement it and be prepared to adjust it. You can't use measurements (metrics) to find faults, at least not in software, so that's not a reasonable goal. You can use metrics to help determine if most of the defects have been discovered already. You can use them to tell you how much longer it will take to uncover a reasonable amount of defects. For either of these metrics you will need to know how previous projects of similar size and complexity (using similar languages, etc.) were done in order to get a reasonable comparison.
|
The following implementations were made:Related Documents
[List and description of implementations made]
6. Dependencies/Risks
 |
| STLC |
Test Requirements ? Requirement Specification documents ? Functional Specification documents ? Design Specification documents (use cases, etc) ? Use case Documents ? Test Trace-ability Matrix for identifying Test Coverage Test Planning ? Test Scope, Test Environment ? Different Test phase and Test Methodologies ? Manual and Automation Testing ? Defect Mgmt, Configuration Mgmt, Risk Mgmt. Etc ? Evaluation & identification ? Test, Defect tracking tools Test Environment Setup ? Test Bed installation and configuration ? Network connectivity?s ? All the Software/ tools Installation and configuration ? Coordination with Vendors and others Test Design ? Test Traceability Matrix and Test coverage ? Test Scenarios Identification & Test Case preparation ? Test data and Test scripts preparation ? Test case reviews and Approval ? Base lining under Configuration Management Test Automation ? Automation requirement identification ? Tool Evaluation and Identification. ? Designing or identifying Framework and scripting ? Script Integration, Review and Approval ? Base lining under Configuration Management Test Execution and Defect Tracking ? Executing Test cases ? Testing Test Scripts ? Capture, review and analyze Test Results ? Raised the defects and tracking for its closure Test Reports and Acceptance ? Test summary reports ? Test Metrics and process Improvements made ? Build release ? Receiving acceptance
Hope this will help for all
Selenium Interview Questions on Textbox 1. How to get text in textbox? 2. How to get attributes like size, placeholder of text box? We have ...
