Testing Metrics

Metric is a measurement of unit for calculating the Quality of project, process..etc
Metric is calculated using the formula

Below are few of the metrics

Test Coverage = Number of units (KLOC/FP) tested / total size of the system. (LOC represents Lines of Code)

Number of tests per unit size = Number of test cases per KLOC/FP (LOC represents Lines of Code).

Acceptance criteria tested = Acceptance criteria tested / total acceptance criteria

Defects per size = Defects detected / system size

Test cost (in %) = Cost of testing / total cost *100

Cost to locate defect = Cost of testing / the number of defects located

Achieving Budget = Actual cost of testing / Budgeted cost of testing

Defects detected in testing = Defects detected in testing / total system defects

Defects detected in production = Defects detected in production/system size

Quality of Testing = No of defects found during Testing/(No of defects found during testing + No of acceptance defects found after delivery) *100

Effectiveness of testing to business = Loss due to problems / total resources processed by the system.

System complaints = Number of third party complaints / number of transactions processed

Scale of Ten = Assessment of testing by giving rating in scale of 1 to 10

Source Code Analysis = Number of source code statements changed / total number of tests.

Effort Productivity = Test Planning Productivity = No of Test cases designed / Actual Effort for Design and Documentation

Test Execution Productivity = No of Test cycles executed / Actual Effort for testing

Software Testing Questions and Answers

sson

1. What’s the Software Testing?

A set of activities conducted with the intent of finding errors in software.

2.What is Acceptance Testing?
Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria.

3. What is Accessibility Testing?
Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

4.  What is Ad Hoc Testing?
A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality.

5. What is Application Programming Interface (API)?

A formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services.

6. What is Backus-Naur Form?

A metalanguage used to formally describe the syntax of a language.

7.  What is Beta Testing?

Testing of a release of a software product conducted by customers.

8. What is Application Binary Interface (ABI)?

A specification defining requirements for portability of applications in binary forms across different system platforms and environments.

9. What is Binary Portability Testing?

Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

10. What is Black Box Testing?

Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component.

11.  What is Bottom Up Testing?

An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.

12. What is Boundary Testing?
Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).

13. What is the difference between verification and validation?
Verification is a review without actually executing the process while validation is checking the product with actual execution. For instance, code review and syntax check is verification while actually running the product and checking the results is validation.

14. What is Bug?
A fault in a program which causes the program to perform in an unintended or unanticipated manner.

15. What is Defect?
If software misses some feature or function from what is there in requirement it is called as defect.

16.  What is Branch Testing?
Testing in which all branches in the program source code are tested at least once.

17. What is Breadth Testing?
A test suite that exercises the full functionality of a product but does not test features in detail.

18. What's the Alpha Testing ?
The Alpha Testing is conducted at the developer sites and in a controlled environment by the end user of the software

19. What's the Beta Testing ?
Testing the application after the installation at the client place.

20. What is Component Testing ?

Testing of individual software components (Unit Testing).

Software Testing Certifications

As a test engineer or QA engineer it is very important to have at least one of the Software testing certifications. This will help to broaden the software testing knowledge, also helpful for testing employees to get the promotion in their respective field in large MNC’s.

Here I am listing some important software testing certifications:
See the description to know why should one go for the respective certification.

CQA-Certified Quality Analyst: 
For Professional level of competence in the principles and practices of quality assurance in the IT profession.

CSTE-Certified Software Test Engineer:
Intended to establish standards for initial qualification and provide direction for the testing function through an aggressive educational program.

CSTP- Certified Software Test Professional:
To teach individuals from different disciplines sound and effective testing techniques and methods and to certify them as Software Testing Professionals.

CQE- Quality Engineer Certificate:
CQE is designed for those who understand the principles of product and service quality evaluation and control.

Quality Manager Certification:
For those who understand quality principles and standards in relation to organization and human resource management

CSQE- Certified Software Quality Engineer:
CSQE is designed for those who have a comprehensive understanding of software quality development and implementation; have a thorough understanding of software inspection and testing, verification, and validation; and can implement software development and maintenance processes and methods

CQIA- Quality Improvement Associate Certificate:
CQIA is designed to assess basic knowledge of quality tools and their uses by individuals who are involved in quality improvement projects, but do not necessarily come from traditional quality areas.

Certifying Software Testers Worldwide

Certifying Software Testers Worldwide

ISTQB® has created the world's most successful scheme for certifying software testers.
As of December 2013, ISTQB® has issued 336,000 certifications in over 100 countries world-wide, with a growth rate of more than 12,000 certifications per quarter.
The scheme relies on a Body of Knowledge (Syllabi and Glossary) and exam rules that are applied consistently all over the world, with exams and supporting material being available in many languages.

Download the ISTQB® Brochure

Sample TestCases for Software Testing

TestCases for Yahoo messenger:

-------------------------------------------

1. verify to login

2. verify to add contact is working

3. send a message to contact available online and offline

4. send a file 

5. add an existing contact6. verify the settings

7. verify the contacts available online and and available(offline)

8. verify to delete contact

9. verify to add group

TestCase for mobile phone:

--------------------------------------

1.Check whether the dimensions of mobile are according to the requirements.

2.Check whether the colour is accroding to requirments.

3.Check whether the functionalities are with respect to the requirements.

4.Check whether the backup for battery is as given in the manual.

5.Check whether the functionalities are with respect to the manual.(extras,games,email services,bluetooth,camera etc.)

6.Checking for various items as charger,headphones,cable etc.

7.checking for display colour(B/w or colour) of the mobile as mentioned in requirements.

8.check whether the functionality of keys are proper.

9.check whether the model is according to the requirements.

10.check for memory used for storage.

11.checking out for memory where data is stored above the peak value.

12.checking for proper signal and network in maximum areas.

13.checking for performance of the mobile.

14.checking for the usability.

TestCases for Telephone:

------------------------------------

1.Lift the handset, u should get a tone.

2.Dial the number again u should here the dial tones

3.If the number is busy, in active, or any such issues you should get an alert about the same

4.If no such alerts , you should here riging tone in the hand set.

5.If it rings for a long time n destination doesnt picks up the call, an alert should be given.

6.If not the above case, at destination user must lift the phone.

7.When he lifts the phone ringing tone must be ended.

8.Now talking session must take place.

9.Both src and destination user can talk n hear properly.

10.If any one of them closes the session, again a tone must be heard at the other end.

11.Close of session in between

IBM's ETVX Concept

ETVX Concept

         IBM has introduced this ETVX model in 80's to document their processes.

'E' stands for the entry criteria which must be satisfied before a set of tasks can be performed.

         Ex: Like Approved SRS/FRS documents are required for the design of application / for Testing

  'T' is the set of tasks / procedures to be performed

          Ex: tasks include design test cases, reviews...etc

 'V' stands for the verification & validation process to ensure that the right tasks are performed
          Ex: validate the application as per the requirements and review the testing

 'X' stands for the exit criteria or the outputs of the tasks.

          Ex: The documents prepared like Test Log / defect reports / Test summary reports...etc

 If an activity fails in the validation check, either corrective action is taken or a rework is ordered. It can be used in any development process. Each phase in the process can be considered as an activity and structured using the ETVX model. If required, the tasks can be further subdivided and each subtask can be further structured using the ETVX model

Testing Metrics

Metrics used in Software Testing

Metric is a measurement of unit for calculating the Quality of project, process..etc
Metric is calculated using the formula

Below are few of the metrics

Test Coverage = Number of units (KLOC/FP) tested / total size of the system. (LOC represents Lines of Code)

Number of tests per unit size = Number of test cases per KLOC/FP (LOC represents Lines of Code).

Acceptance criteria tested = Acceptance criteria tested / total acceptance criteria

Defects per size = Defects detected / system size

Test cost (in %) = Cost of testing / total cost *100

Cost to locate defect = Cost of testing / the number of defects located

Achieving Budget = Actual cost of testing / Budgeted cost of testing

Defects detected in testing = Defects detected in testing / total system defects

Defects detected in production = Defects detected in production/system size

Quality of Testing = No of defects found during Testing/(No of defects found during testing + No of acceptance defects found after delivery) *100

Effectiveness of testing to business = Loss due to problems / total resources processed by the system.

System complaints = Number of third party complaints / number of transactions processed

Scale of Ten = Assessment of testing by giving rating in scale of 1 to 10

Source Code Analysis = Number of source code statements changed / total number of tests.

Effort Productivity = Test Planning Productivity = No of Test cases designed / Actual Effort for Design and Documentation

Test Execution Productivity = No of Test cycles executed / Actual Effort for testing

Definition of Testing :-

        
         Verify the application as per the customer requirements
         Verify can we develop the right product or not
         Verify the application as per industry standards
         Verify the application for bug free
         Combination of Verification and Validation   

h