Depth test: A test case that exercises some part of a system to a significant level of detail.
Dirty testing: Negative testing.
Exception Testing: Identify error messages and exception handling processes an conditions.
Exhaustive Testing: Executing the program with all possible combinations of values for program variables.
Feasible only for small, simple programs.
Formal Testing: Testing conducted in accordance with test plans and procedures that have been reviewed and approved by a customer, user, or designated level of management
Informal Testing: Testing is conducted in accordance without plans and procedures and reviews cannot be done properly here
State Transition Testing: Technique in which the states of a system are identified and then test cases are written to test from one condition to another state.
Structural Testing: Testing that takes into account the internal mechanism [structure] of a system or component. Types include branch testing, path testing, statement testing. Or testing to insure each program statement is made to execute during testing and that each program statement performs its intended function. Contrast with functional testing.
EX: white-box testing
Usability testing: Testing for ‘user-friendliness’. Clearly this is subjective, and will depend on the targeted end-user or customer.
Test Harness: A system of test drivers and other tools to support test execution (e.g., stubs, executable test cases, and test drivers).
Test Tree: A physical implementation of Test Suite.
Difference between Qa Eng Test Engineer
1. In Qa Engineer He Is Having Knowledge on Development and Testing
2. In Test Engineer He Is Having Knowledge on Testing
Testing in which all branches in the program source code are tested at least once
Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed.
This is an inspection/assessment activity that verifies compliance with plans, policies and procedures and ensures that resources are conserved
A test method satisfying the coverage criteria that each logical path through the program be tested. Often, paths through the program are grouped into a finite set of classes and one path from each class is tested.
Software quality factors:
Software quality factors are attributes of the software that, if they are wanted and not present, suppose a risk to the success of the software. There are 11 main factors and their definitions are given below. The priority and importance of the these attributes keeps changing from product to product. Like if the product being developed needs to be changed quite frequently, then flexibility and reusability of the product needs to be given priority.
The following are the quality factors
While testing a product, test manager has to take a lot of decisions like when to stop testing or when is the application ready for production, how to track testing progress, how to measure the quality of a product at a certain point in the testing cycle? Testing metrics can help to take better and accurate decisions Lets start by defining the term ‘Metric’
Ametric is a mathematical number that shows a relationship between two variables.
Software metrics are measures used to quantify status or results.
How to track testing progress?
The best way is to have a fixed number of test cases ready before test execution cycle begins. Then the testing progress is measured by the total number of test cases executed.
% Completion = (Number of test cases executed)/(Total number of test cases)
Not only the testing progress but also the following metrics are helpful to measure the quality of the product
% Test cases Passed = (Number of test cases Passed)/ (Number of test cases executed)
% Test cases Failed = (Number of test cases Failed)/ (Number of test cases executed)