Written on 10:34 PM by MURALI KRISHNA
Testing Dictionary
Acceptance Testing
Formal testing conducted to enable a user, customer, or other authorized entity to determine whether to accept a system or component.
Actual Outcome
The behaviour actually produced when the object is tested under specified conditions.
Adding Value
Adding something that the customer wants that was not there before.
Ad hoc Testing
Testing carried out using no recognized test case design technique.
Alpha Testing
Simulated or actual operational testing at an in-house site not otherwise involved with the software developers.
Arc Testing
A test case design technique for a component in which test cases are designed to execute branch outcomes.
Backus-Naur Form
A metalanguage used to formally describe the syntax of a language.
Basic Block
A sequence of one or more consecutive, executable statements containing no branches.
Basis Test Set
A set of test cases derived from the code logic, which ensure that 100% branch coverage is achieved.
Bebugging
The process of intentionally adding known faults to those already in a computer program for the purpose of monitoring the rate of detection and removal, and estimating the number of faults remaining in the program.
Behaviour
The combination of input values and preconditions and the required response for a function of a system. The full specification of a function would normally comprise one or more behaviours.
Benchmarking
Comparing your product to the best competitors'.
Beta Testing
Operational testing at a site not otherwise involved with the software developers.
Big-bang Testing
Integration testing where no incremental testing takes place prior to all the system's components being combined to form the system.
Black Box Testing
Test case selection that is based on an analysis of the specification of the component without reference to its internal workings. Testing by looking only at the inputs and outputs, not at the insides of a program.
Sometimes also called "Requirements Based Testing". You don't need to be a programmer, you only need to know what the program is supposed to do and be able to tell whether an output is correct or not.
Bottom-up Testing
An approach to 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.
Boundary Value
An input value or output value which is on the boundary between equivalence classes, or an incremental distance either side of the boundary.
Boundary Value Analysis
A test case design technique for a component in which test cases are designed which include representatives of boundary values.
Boundary Value Coverage
The percentage of boundary values of the component's equivalence classes, which have been exercised by a test case suite.
Boundary Value Testing
A test case design technique for a component in which test cases are designed which include representatives of boundary values.
Boundary Value Coverage
The percentage of boundary values of the component's equivalence classes, which have been exercised by a test case suite.
Boundary Value Testing
A test case design technique for a component in which test cases are designed which include representatives of boundary values.
Branch
A conditional transfer of control from any statement to any other statement in a component, or an unconditional transfer of control from any statement to any other statement in the component except the next statement, or when a component has more than one entry point, a transfer of control to an entry point of the component.
Branch Condition
A condition within a decision.
Branch Condition Combination Coverage
The percentage of combinations of all branch condition outcomes in every decision that have been exercised by a test case suite.
Branch Condition Combination Testing
A test case design technique in which test cases are designed to execute combinations of branch condition outcomes.
Branch Condition Coverage
The percentage of branch condition outcomes in every decision that have been exercised by a test case suite.
Branch Condition Testing
A test case design technique in which test cases are designed to execute branch condition outcomes.
Branch Coverage
The percentage of branches that have been exercised by a test case suite.
Branch Outcome
The result of a decision (which therefore determines the control flow alternative taken).
Branch Point
A program point at which the control flow has two or more alternative routes.
Branch Testing
A test case design technique for a component in which test cases are designed to execute branch outcomes.
Bring to the Table
Refers to what each individual in a meeting can contribute to a meeting, for example, a design or brainstorming meetings.
Bug
A manifestation of an error in software. A fault, if encountered may cause a failure.
Bug Seeding
The process of intentionally adding known faults to those already in a computer program for the purpose of monitoring the rate of detection and removal, and estimating the number of faults remaining in the program.
C-use
A data use not in a condition.
Capture/Playback Tool
A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time.
Capture/Replay Tool
A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time.
CAST
Acronym for computer-aided software testing.
Cause-effect Graph
A graphical representation of inputs or stimuli (causes) with their associated outputs (effects), which can be used to design test cases.
Cause-effect Graphing
A test case design technique in which test cases are designed by consideration of cause-effect graphs.
Certification
The process of confirming that a system or component complies with its specified requirements and is acceptable for operational use.
Chow's Coverage Metrics
The percentage of sequences of N-transitions that have been exercised by a test case suite.
Code Coverage
An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.
If we have a set of tests that gives Code Coverage, it simply means that, if you run all the tests, every line of the code is executed at least once by some test.
Code-based Testing
Designing tests based on objectives derived from the implementation (e.g., tests that execute specific control flow paths or use specific data items).
Compatibility Testing
Testing whether the system is compatible with other systems with which it should communicate.
Complete Path Testing
A test case design technique in which the test case suite comprises all combinations of input values and preconditions for component variables.
Component
A minimal software item for which a separate specification is available.
Component Testing
The testing of individual software components.
Computation Data Use
A data use not in a condition. Also called C-use.
Concurrent (or Simultaneous) Engineering
Integrating the design, manufacturing, and test processes.
Condition
A Boolean expression containing no Boolean operators. For instance, A < B is a condition but A and B is not.
Condition Coverage
The percentage of branch condition outcomes in every decision that have been exercised by a test case suite.
Condition Outcome
The evaluation of a condition to TRUE or FALSE.
Conformance Criterion
Some method of judging whether or not the component's action on a particular specified input value conforms to the specification.
Conformance Testing
The process of testing that an implementation conforms to the specification on which it is based.
Continuous Improvement
The PDSA process of iteration which results in improving a product.
Control Flow
An abstract representation of all possible sequences of events in a program's execution.
Control Flow Graph
The diagrammatic representation of the possible alternative control flow paths through a component.
Control Flow Path
A sequence of executable statements of a component, from an entry point to an exit point.
Conversion Testing
Testing of programs or procedures used to convert data from existing systems for use in replacement systems.
Correctness
The degree to which software conforms to its specification.
Coverage
The degree, expressed as a percentage, to which a specified coverage item has been exercised by a test case suite.
A measure applied to a set of tests. The most important are called Code Coverage and Path Coverage. There are a number of intermediate types of coverage defined, moving up the ladder from Code Coverage (weak) to Path Coverage (strong, but hard to get). These definitions are called things like Decision -Condition Coverage, but they're seldom important in the real world. For the curious, they are covered in detail in Glenford Myers' book, The Art of Software Testing.
Coverage Item
An entity or property used as a basis for testing.
Customer Satisfaction
Meeting or exceeding a customer's expectations for a product or service.
Data Coupling
Data coupling is where one piece of code interacts with another by modifying a data object that the other code reads. Data coupling is normal in computer operations, where data is repeatedly modified until the desired result is obtained. However, unintentional data coupling is bad. It causes many hard to find bugs, and it causes all "side effect" bugs caused by changing existing systems. It's the reason why you need to test all paths to do really tight testing. The best way to combat it is with Regression Testing, to make sure that a change didn't break something else.
Data Definition
An executable statement where a variable is assigned a value.
Data Definition C-use Coverage
The percentage of data definition C-use pairs in a component that are exercised by a test case suite.
Data Definition C-use Pair
A data definition and computation data use, where the data use uses the value defined in the data definition.
Data Definition P-use Coverage
The percentage of data definition P-use pairs in a component that are exercised by a test case suite.
Data Definition P-use Pair
A data definition and predicate data use, where the data use uses the value defined in the data definition.
Data Definition-use Coverage
The percentage of data definition-use pairs in a component that are exercised by a test case suite.
Data Definition-use Pair
A data definition and data use , where the data use uses the value defined in the data definition.
Data Definition-use Testing
A test case design technique for a component in which test cases are designed to execute data definition-use pairs.
Data Flow Coverage
Test coverage measure based on variable usage within the code. Examples are data definition-use coverage, data definition P-use coverage, data definition C-use coverage, etc.
Data Flow Testing
Testing in which test cases are designed based on variable usage within the code.
Data Use
An executable statement where the value of a variable is accessed.
Debugging
The process of finding and removing the causes of failures in software.
Decision
A program point at which the control flow has two or more alternative routes.
Decision Condition
A condition within a decision.
Decision Coverage
The percentage of decision outcomes that have been exercised by a test case suite.
Decision Outcome
The result of a decision (which therefore determines the control flow alternative taken).
Design
The creation of a specification from concepts.
Design-based Testing
Designing tests based on objectives derived from the architectural or detail design of the software (e.g., tests that execute specific invocation paths or probe the worst case behaviour of algorithms).
Desk Checking
The testing of software by the manual simulation of its execution.
Dirty Testing
Testing aimed at showing software does not work.
Documentation Testing
Testing concerned with the accuracy of documentation.
Domain
The set from which values are selected.
Domain Testing
A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Dynamic Analysis
The process of evaluating a system or component based upon its behaviour during execution.
Driver
A throwaway little module that calls something we need to test, because the real guy who'll be calling it isn't available.
For example, suppose module A needs module X to fire it up.
X isn't here yet, so we use a stub:
Emulator
A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system.
Entry Point
The first executable statement within a component.
Equivalence Class
A portion of the component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification.
An Equivalence Class (EC) of input values is a group of values that all cause the same sequence of operations to occur.
In Black Box terms, they are all treated the same way according to the specs. Different input values within an Equivalence Class may give different answers, but the answers are produced by the same procedure.
In Glass Box terms, they all cause execution to go down the same path.
Equivalence Partition
A portion of the component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification.
Equivalence Partition Coverage
The percentage of equivalence classes generated for the component, which have been exercised by a test case suite.
Equivalence Partition Testing
A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Error
A human action that produces an incorrect result.
Error Guessing
A test case design technique where the experience of the tester is used to postulate what faults might occur, and to design tests specifically to expose them.
Error Seeding
The process of intentionally adding known faults to those already in a computer program for the purpose of monitoring the rate of detection and removal, and estimating the number of faults remaining in the program.
Executable Statement
A statement which, when compiled, is translated into object code, which will be executed procedurally when the program is running and may perform an action on program data.
Exercised
A program element is exercised by a test case when the input value causes the execution of that element, such as a statement, branch, or other structural element.
Exhaustive Testing
A test case design technique in which the test case suite comprises all combinations of input values and preconditions for component variables.
Exit Point
The last executable statement within a component.
Facility Testing
Test case selection that is based on an analysis of the specification of the component without reference to its internal workings.
Failure
Deviation of the software from its expected delivery or service.
Fault
A manifestation of an error in software. A fault, if encountered may cause a failure.
Feasible Path
A path for which there exists a set of input values and execution conditions, which causes it to be executed.
Feature Testing
Test case selection that is based on an analysis of the specification of the component without reference to its internal workings.
Flow Charting
Creating a 'map' of the steps in a process.
Functional Chunk
The fundamental unit of testing.
Its precise definition is "The smallest piece of code for which all the inputs and outputs are meaningful at the spec level." This means that we can test it Black Box, and design the tests before the code arrives without regard to how it was coded, and also tell whether the results it gives are correct.
Functional Specification
The document that describes in detail the characteristics of the product with regard to its intended capability.
Functional Test Case Design
Test case selection that is based on an analysis of the specification of the component without reference to its internal workings.
Glass Box Testing
Test case selection that is based on an analysis of the internal structure of the component.
Testing by looking only at the code.
Sometimes also called "Code Based Testing".
Obviously you need to be a programmer and you need to have the source code to do this.
Incremental Integration
A systematic way for putting the pieces of a system together one at a time, testing as each piece is added. We not only test that the new piece works, but we also test that it didn't break something else by running the RTS (Regression Test Set).
Incremental Testing
Integration testing where system components are integrated into the system one at a time until the entire system is integrated.
Independence
Separation of responsibilities, which ensures the accomplishment of objective evaluation.
Infeasible Path
A path, which cannot be exercised by any set of possible input values.
Input
A variable (whether stored within a component or outside it) that is read by the component.
Input Domain
The set of all possible inputs.
Input Value
An instance of an input.
Inspection
A group review quality improvement process for written material. It consists of two aspects; product (document itself) improvement and process improvement (of both document production and inspection).
Installability Testing
Testing concerned with the installation procedures for the system.
Instrumentation
The insertion of additional code into the program in order to collect information about program behaviour during program execution.
Instrumenter
A software tool used to carry out instrumentation.
Integration
The process of combining components into larger assemblies.
Integration Testing
Testing performed to expose faults in the interfaces and in the interaction between integrated components.
Interface Testing
Integration testing where the interfaces between system components are tested.
Isolation Testing
Component testing of individual components in isolation from surrounding components, with surrounding components being simulated by stubs.
LCSAJ
A Linear Code Sequence And Jump, consisting of the following three items (conventionally identified by line numbers in a source code listing): the start of the linear sequence of executable statements, the end of the linear sequence, and the target line to which control flow is transferred at the end of the linear sequence.
LCSAJ Coverage
The percentage of LCSAJs of a component, which are exercised by a test case suite.
LCSAJ Testing
A test case design technique for a component in which test cases are designed to execute LCSAJs.
Logic-coverage Testing
Test case selection that is based on an analysis of the internal structure of the component.
Logic-driven Testing
Test case selection that is based on an analysis of the internal structure of the component.
Maintainability Testing
Testing whether the system meets its specified objectives for maintainability.
Manufacturing
Creating a product from specifications.
Metrics
Ways to measure: e.g., time, cost, customer satisfaction, quality.
Modified Condition/Decision Coverage
The percentage of all branch condition outcomes that independently affect a decision outcome that have been exercised by a test case suite.
Modified Condition/Decision Testing
A test case design technique in which test cases are designed to execute branch condition outcomes that independently affect a decision outcome.
Multiple Condition Coverage
The percentage of combinations of all branch condition outcomes in every decision that have been exercised by a test case suite.
Mutation Analysis
A method to determine test case suite thoroughness by measuring the extent to which a test case suite can discriminate the program from slight variants (mutants) of the program. See also The process of intentionally adding known faults to those already in a computer program for the purpose of monitoring the rate of detection and removal, and estimating the number of faults remaining in the program.
N-switch Coverage
The percentage of sequences of N-transitions that have been exercised by a test case suite.
N-switch Testing
A form of state transition testing in which test cases are designed to execute all valid sequences of N-transitions.
N-transitions
A sequence of N+1 transitions.
Negative Testing
Testing aimed at showing software does not work.
Non-functional Requirements Testing
Testing of those requirements that do not relate to functionality. i.e. performance, usability, etc.
Operational Testing
Testing conducted to evaluate a system or component in its operational environment.
Oracle
A mechanism to produce the predicted outcomes to compare with the actual outcomes of the software under test.
Outcome
Actual outcome or predicted outcome. This is the outcome of a test.
Output
A variable (whether stored within a component or outside it) that is written to by the component.
Output Domain
The set of all possible outputs.
Output Value
An instance of an output.
P-use
A data use in a predicate.
Partition Testing
A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.
Path
A sequence of executable statements of a component, from an entry point to an exit point.
Path Coverage
The percentage of paths in a component exercised by a test case suite.
A set of tests that gives Path Coverage for some code if the set goes down each path at least once.
The difference between this and Code Coverage is that Path Coverage means not just "visiting" a line of code, but also includes how you got there and where you're going next. It therefore uncovers more bugs, especially those caused by Data Coupling.
However, it's impossible to get this level of coverage except perhaps for a tiny critical piece of code.
Path Sensitizing
Choosing a set of input values to force the execution of a component to take a given path.
Path Testing
A test case design technique in which test cases are designed to execute paths of a component.
Performance Testing
Testing conducted to evaluate the compliance of a system or component with specified performance requirements.
Portability Testing
Testing aimed at demonstrating the software can be ported to specified hardware or software platforms.
Precondition
Environmental and state conditions which must be fulfilled before the component can be executed with a particular input value.
Predicate
A logical expression, which evaluates to TRUE or FALSE, normally to direct the execution path in code.
Predicate Data Use
A data use in a predicate.
Predicted Outcome
The behaviour predicted by the specification of an object under specified conditions.
Process
What is actually done to create a product.
Program Instrumenter
A software tool used to carry out instrumentation.
Progressive Testing
Testing of new features after regression testing of previous features.
Pseudo-random
A series which appears to be random but is in fact generated according to some prearranged sequence.
Quality Tools
Tools used to measure and observe every aspect of the creation of a product.
Recovery Testing
Testing aimed at verifying the system's ability to recover from varying degrees of failure.
Regression Testing
Retesting of a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.
Re-running a set of tests that used to work to make sure that changes to the system didn't break anything. It's usually run after each set of maintenance or enhancement changes, but is also very useful for Incremental Integration of a system.
RTS (Regression Test Set)
The set of tests used for Regression Testing. It should be complete enough so that the system is defined to "work correctly" when this set of tests runs without error.
Requirements-based Testing
Designing tests based on objectives derived from requirements for the software component (e.g., tests that exercise specific functions or probe the non-functional constraints such as performance or security).
Result
Actual outcome or predicted outcome. This is the outcome of a test.
Review
A process or meeting during which a work product, or set of work products, is presented to project personnel, managers, users or other interested parties for comment or approval.
Security Testing
Testing whether the system meets its specified security objectives.
Serviceability Testing
Testing whether the system meets its specified objectives for maintainability.
Simple Subpath
A subpath of the control flow graph in which no program part is executed more than necessary.
Simulation
The representation of selected behavioural characteristics of one physical or abstract system by another system.
Simulator
A device, computer program or system used during software verification, which behaves or operates like a given system when provided with a set of controlled inputs.
Six-Sigma Quality
Meaning 99.999997% perfect; only 3.4 defects in a million.
Source Statement
An entity in a programming language, which is typically the smallest indivisible unit of execution.
SPC
Statistical process control; used for measuring the conformance
of a product to specifications.
Specification
A description of a component's function in terms of its output values for specified input values under specified preconditions.
Specified Input
An input for which the specification predicts an outcome.
State Transition
A transition between two allowable states of a system or component.
State Transition Testing
A test case design technique in which test cases are designed to execute state transitions.
Statement
An entity in a programming language, which is typically the smallest indivisible unit of execution.
Statement Coverage
The percentage of executable statements in a component that have been exercised by a test case suite.
Statement Testing
A test case design technique for a component in which test cases are designed to execute statements.
Static Analysis
Analysis of a program carried out without executing the program.
Static Analyzer
A tool that carries out static analysis.
Static Testing
Testing of an object without execution on a computer.
Statistical Testing
A test case design technique in which a model is used of the statistical distribution of the input to construct representative test cases.
Storage Testing
Testing whether the system meets its specified storage objectives.
Stress Testing
Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements.
Structural Coverage
Coverage measures based on the internal structure of the component.
Structural Test Case Design
Test case selection that is based on an analysis of the internal structure of the component.
Structural Testing
Test case selection that is based on an analysis of the internal structure of the component.
Structured Basis Testing
A test case design technique in which test cases are derived from the code logic to achieve 100% branch coverage.
Structured Walkthrough
A review of requirements, designs or code characterized by the author of the object under review guiding the progression of the review.
Stub
A skeletal or special-purpose implementation of a software module, used to develop or test a component that calls or is otherwise dependent on it. A little throwaway module that can be called to make another module work (and hence be testable).
For example, if we want to test module A but it needs to call module B, which isn't available, we can use a quick little stub for B. It just answers "hello from b" or something similar; if asked to return a number it always returns the same number - like 100.
Subpath
A sequence of executable statements within a component.
Symbolic Evaluation
A static analysis technique that derives a symbolic expression for program paths.
Syntax Testing
A test case design technique for a component or system in which test case design is based upon the syntax of the input.
System Testing
The process of testing an integrated system to verify that it meets specified requirements.
Technical Requirements Testing
Testing of those requirements that do not relate to functionality. i.e. performance, usability, etc.
Test
Testing the product for defects.
Test Automation
The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.
Test Case
A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement.
Test Case Design Technique
A method used to derive or select test cases.
Test Case Suite
A collection of one or more test cases for the software under test.
Test Comparator
A test tool that compares the actual outputs produced by the software under test with the expected outputs for that test case.
Test Completion Criterion
A criterion for determining when planned testing is complete, defined in terms of a test measurement technique.
Test Coverage
The degree, expressed as a percentage, to which a specified coverage item has been exercised by a test case suite.
Test Driver
A program or test tool used to execute software against a test case suite.
Test Environment
A description of the hardware and software environment in which the tests will be run, and any other software with which the software under test interacts when under test including stubs and test drivers.
Test Execution
The processing of a test case suite by the software under test, producing an outcome.
Test Execution Technique
The method used to perform the actual test execution, e.g. manual, capture/playback tool, etc.
Test Generator
A program that generates test cases in accordance to a specified strategy or heuristic.
Test Harness
A testing tool that comprises a test driver and a test comparator.
Test Measurement Technique
A method used to measure test coverage items.
Test Outcome
Actual outcome or predicted outcome. This is the outcome of a test. The result of a decision (which therefore determines the control flow alternative taken). The evaluation of a condition to TRUE or FALSE.
Test Plan
A record of the test planning process detailing the degree of tester independence, the test environment, the test case design techniques and test measurement techniques to be used, and the rationale for their choice.
Test Procedure
A document providing detailed instructions for the execution of one or more test cases.
Test Records
For each test, an unambiguous record of the identities and versions of the component under test, the test specification, and actual outcome.
Test Script
Commonly used to refer to the automated test procedure used with a test harness.
Test Specification
For each test case, the coverage item, the initial state of the software under test, the input, and the predicted outcome.
Test Target
A set of test completion criteria.
Testing
The process of exercising software to verify that it satisfies specified requirements and to detect errors.
Thread Testing
A variation of top-down testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels.
Top-down Testing
An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested.
Total Quality Control (TQM)
Controlling everything about a process.
Unit Testing
The testing of individual software components.
A Unit, as we use it in these techniques, is a very small piece of code with only a few inputs and outputs. The key thing is that these inputs and outputs may be implementation details (counters, array indices, pointers) and are not necessarily real world objects that are described in the specs. If all the inputs and outputs are real-world things, then we have a special kind of Unit, the Functional Chunk, which is ideal for testing. Most ordinary Units are tested by the programmer who wrote them, although a much better practice to have them subsequently tested by a different programmer.
Caution: There is no agreement out there about what a "unit" or "module" or subsystem" etc. really is. I've heard 50,000 line COBOL programs described as "units". So the Unit defined here is, in fact, a definition.
Usability Testing
Testing the ease with which users can learn and use a product.
Validation
Determination of the correctness of the products of software development with respect to the user needs and requirements.
Verification
The process of evaluating a system or component to determine whether the products of the given development phase satisfy the conditions imposed at the start of that phase.
Volume Testing
Testing where the system is subjected to large volumes of data.
Walkthrough
A review of requirements, designs or code characterized by the author of the object under review guiding the progression of the review.
White Box Testing
Test case selection that is based on an analysis of the internal structure of the component.
|
Written on 10:29 PM by MURALI KRISHNA
Testing tools Faqs
1. What are the entry and exit points in test plan?
A. Entry point of test plan is- that functional description to be tested and required procedure is the exit point.
2. What is the use of “swing time” in Load runner?
A. Elapsed time indicates swing time(to determine the performance of the application under load)
3. What is internationalization?
A. It means that following standards. Ex. ISO/CMM/Six Sigma.
4. What are the different functions in winrunner?
A. Analog functions, Context Sensitive functions, Customization functions, Miscellaneous and Standard functions.
5. What are the testings involved in black-box testing?
A. Acceptance Testing, Control-flow, Data flow and integrity, capability, stress testing, user-interface, regression, performance, potential bugs, beta test, release test, utilities.
6. What is integration testing?
A. A test related to more than one module called integration testing .
7. What is unit testing?
A. A test at module level is called unit testing.
8.What are the documents prepared for ISO?
A. Quality manual, Quality procedures, work Instructions formats.
9. What is the difference between Load & Stress testing?
A. Load testing is used to estimate under incremental load, while stress testing used to find bugs when an application working at maximum volumes of resources.
10. What are CMM levels? Explain? Key process areas? (V & III)
A. 5 levels.
11. What is memory leakage?
A. Improper allocations/de-allocations of memory during execution time.
12. What are external functions?
A. External functions means that a function defined in one test and used in another tests.
13. What are data table functions?
A. ddt_open(), ddt_update_from _db(), ddt_save() ,ddt_get_row_count(), ddt_set_rows(), ddt_val(), ddt_close().
14. What are the files using in winrunner?
A. Script files, checklist files, expected values files, data table files, guimap files, start up script files.
15. What is exception handing?
A. To remove runtime testing problems, we can use exception handling.
16. What are exceptions in winrunner?
A. TSL, Object, Pop-up and URL
17. What is GUI map file? Explain?
A. GUI map file consists of “logical names” and ‘physical descriptions’ of objects & windows, which are recognized for each object/window during recording and running.
18. What are the add- ins in winrunner?
A. Web Test, ActiveX, Power Builder and Visual Basic.
19. What is visual recorder in Load runner?
24. How to open GUI map file?
A. Using GUI map editor.
25. How can it be known when to stop testing?
A. When existing test cases show any application change (called mutation).
26. What are the parameters in Load runner?
A. Elapsed, Transaction, Response, Hit per second and Throughput.
27. How do you read text from an application?
A. Get text and Select text for(for web)
28. How can you map custom classes to standard classes?
A. By using Virtual Object Wizard.
29. What is s/w testing?
A. Verification and Validation of an Application.
30. Why you need a test plan? What is test plan?
A. Test plan specified process and scheduling of an application.
31. What is big bang testing? Or informal testing?
A. It means that a testing on total system.
32. What is formal testing?
A. Formal(or Incremental) means ‘until testing’.
33. What is mutation testing?
A. Small changes identified by existing test cases.
34. What is regression testing?
A. Regression means that execution of test cases on new version of application/modified version.
35. What is stress, security testing?
A. Security testing means that the testing of an application depends on Authorization and encryption/decryption cases.
36. What is test case?
A. Test case is a small issue to test functionality.
37. What is the diff between function and Test case?
A. Test cases are derived from functionality.
38. Contents of Test plan?
A. Test team, Test scheduling, Test factors, Approach, Functionality list of Test case.
39. Difference between water fall model and iterative model?
A. Waterfall is a single thread process where as Iterative is multiple thread process.
40. Where to use private and public functions in script?
A. private functions are only applied on current Test and public functions applied anywhere.
41. What is system testing?
A. A Test at system level.
42. What are the major bugs you find in the application you have tested?
A. Load test errors.
43. What are the minor bugs you find in the application you have tested?
A. User interface errors.
44. What is the life cycle of bug reporting?
A. Bug detection=>fixing the bug=>bug reproducing=>report creation=>bug submission.
45. On what basis the test plan is prepared?
A. Test manager develops Test Plan based on development plan(SRS and FRS)
46. What you will do after preparing test cases?
A. Test procedure preparation after selection of test case.
47. What is the formula used in white box testing?
A. In White-box testing, tester concentrates on what is requirement of program and what is the functionality of the program.
48. When test cases will be prepared, after coding or before coding?
A. Test cases are prepared at design level.
49. What are the documents you have in testing environment?
A. Testing policy, testing strategy, testing methodology, test plan, test cases, test scenarios, test procedures, test scripts, logs and bug reports.
50. What makes a good s/w quality assurance engineer?
A. QA engineer produce suggestions to tester to increase the strength of the testing process.
51. What is testing life cycle? What is bug tracking life cycle?
A. Life cycle means testing at all development stages.
52. What if the s/w has so many bugs, it can not really be tested?
A. Be bugging(not debugging) is a process to estimate defects before testing.
53. How does a Client/Server environment effect testing?
A. In Client/Server(C/S) testing, testers follows these steps:
i. Assess Readiness(Integration of C/S process)
ii. Assess key process.
iii. Perform testing.
54. How can WWW be tested?
A. To Test web applications, testers follows these steps:]
i. Select Web based risks
ii. Select Web based tests
iii. Select Web based tools
iv Perform tests
55. What is s/w quality assurance?
A. QA shows, customer satisfaction of application, including features and flaws.
56. Can U tell me why does s/w have bugs?
A. Different members at different levels develop software applications.
57. What is verification problems in s/w development process?
A. Verification:- To Check application based on corresponding development documents.
Validation:- To Check whether the application functionality equals to customer’s expectation
Walkthrough:- Is the Review of the Total application functionality.
58. What are 5 common problems in s/w development process?
A. i. Poor requirements
ii. Improper scheduling
iii. Testing with wrong criteria
iv. Miscommunication.
59. What is s/w quality?
A. Customer satisfaction including no.of features/flaws.
60. Will automated testing tools make testing easier?
A. Automated testing decreases complexity in testing, when applications consists of:
i. More external interfaces
ii. Type of external interfaces
iii. No of releases
iv. Maturity in application etc.
61. What are the silk test tools to manage, execute and interprets your scripts?
A. In silk testing, we can follow below test process:
i. Plan inclusion
ii. Recapturing
iii. Recording(script)
iv. Run the script
v. Analyze defects
vi. Manual report
62. What is smoke testing? Out time editor, the result processor, the debugger?
A. A test case with wrong criteria. It specified indication of bug.
63. How do you set the parameters when test the Client/Server application?
A. In C/S Load Testing, we can depend on elapsed transaction and response times.
64. What is recovery system? Can you give some functions that override some of the default behaviour?
A. Default script enter, Default script exit.
65. Why silk test sees objects as custom windows?
A. Silk test sees each objects as user-defined. Because this tool used java application testing.
66. Can you test an application in silk test that is running on another system?
A. Yes
67. Can you test multiple different applications simultaneously?
A. Yes. We can concentrate on more test cases simultaneously because each application test has different test cases.
68. What is spawn statement? Why it is used?
A. To maintain delay, during execution time for synchronization.
Spawn(time in seconds)
69. What is application state and base state and call state?
A. Application State: Is a situation in application
Base State : Is the starting state of application
Call State : Is the state of application
70. What is difference between winrunner and silk test?
A. Test procedure Vs. Object oriented script; Different process Vs. Single threaded.
71. How does winrunner identifies GUI objects?
A. Logical names and physical descriptions.
72. How do you program tests with TSL?
A. A program, test using TSL at “exe” level.
73. What TL_STEP function is used?
A. To insert user defined error message in Test log.
74. What is the difference b/w pause();,message();?
A. pause()-used to display a message with termination of process.
Report-msg()-used to give message in test results table.
75. What is batch test?
A. Execution of more than one tests simultaneously.
76. What is DON in silk?
A. In silk test, silk agent is Don, It displays at status bar.
77. What is the base class for all the classes in Silk Test?
A. In silk test, Application name is base class to all classes in scripting.
78. What is the use of style bits in Custom class in silk?
A. The class of object in verify window is called style of custom class.
79. What is extension in silk?
A. .t is the extension of test case, .pln for test plan.
80. What .inc file consists in silk?
A. .inc is the extension of test frame.
81. how do you create a user defined class in silk
A. It allows user defined classes in script.
82. What are agents in silk?
A. Capturing agents, recording and running agents.
83. how do you refer your test case in .t file through Test plan?
A. . pln is extension of test plan and it specifies .t as test case.
84. Will TSL supports function overloading & operator overloading?
A. TSL allows function overloading, but not operator overloading.
85. If you purchase a software, what test you perform?
A. Purchased software is called off-the-shelf software. To test this application,we can perform functionality testing.
86. Did you see user defined TSL in your project?
A. Yes
87. How many functions you write in your project?
A. Depends on requirement, to define more then one user-defined functions.
88. What are key features the Bug tracking database must offer?
A. Bug Tracking database provide test doc, retrieving and maintenance.
89. Write a program in TSL to get data from data table and feed them your edited fields in the application?
A. Data driven test(ddt).
90. What is negative testing?
A. A Test with Fail criteria.
91. What is change management process?
A. Change management process is used to test the changes in existing application, which is in maintenance stage.
92. What is configuration management process?
A. Configuration management process is used to verify the configuration of the existing application performance changes.
93. What is version control?
A. Maturity in new version compare to the previous version.
94. What is defect tracking?
95. What is security testing?
A. Whether this appli follows correct authorization of Encrypt and Descript procedure or not.
96. What is good code?
A. More functionality with less statements and meets customer requirements.
97. What is digital signature test?
A. By bitmap testing.
98. What is sort testing?
A. Used to test sorting tech. In your application.
99. What is memory leakage testing?
A. Stress testing identifies memory leakages.
100. What is data driven automation?
A. To run existing test case with different input values, we can use Data driven test.
101. What is compatibility testing?
A. When application server on different input values, we can use Data driven test.
102. What is defect deficiency? If A is the no. of bugs found in Alpha test, B is the no.of bugs found in Beta test, what no?
A. Defect deficiency/defect removal efficiency is defined by the formula:
A/(A+B) where A: No. of bugs in previous test
B: No.of bugs in present test.
103. How will you choose a tool in test automation? How will you find the tools work well with your existing system?
A. To select a tool, we can depends on:
i. Scripting style of tool
ii. Scripting updating
iii. Reusability of scripting
iv. Readability of scripting
v. Batch
104. How can data caching have a negative effect in Load testing results?
A. In load testing, we will get negative results when no available large memory areas and does not clear items from buffer.
105. What are the benefits of creating multiple actions within any virtual user scripts?
A. We can use more than on operator actions to estimate performance of each operation through single test.
106. How do you scope, organize and execute your project?
A. According to standards and customer requirements.
107. What sort of things would you put down in your bug report?
A. Bug severity/priority or main factors to list out defects.
108. Should we test every possible combination/scenario for a program?
A. Tester tries to test all possible test cases for application.
109. What metrics you feel important to publish in organization?
A. In an organization, we can use LOC(luer of code) related and functional point related metrics.
110. What is your worst experience in project?
A. Finding bugs, reproducing bugs is important in bug tracking, but all bugs are not reproducible.
111. What is your experience in code analyzers?
A. Pseudo code analyzers are used to estimate the logic of program without execution.
112. How did you involve in bug fix cycle between developer and QA?
A. Tester working as middle position in between QA and developer with bug tracking stages.
113. How do you know your code has met specification when there are no specifications?
A. A tester identifies the functionality of program depends on specifications. If there is no specification then he/she
i. Can depends on estimated functionality by self(acts as customer)
ii. Previous version and
iii. Direct communication with customer.
114. What type of documents would you need for QA/QC Testing?
A. Testing policy=>strategy=>methodology=>…etc.
115. How you participated in integration testing?
A. Participate in integration testing with compound test cases of modules.
116. How would you ensure 100% coverage of testing?
A. Testers prepare test cases related to all functional items to ensure 100% of testing coverage.
117. What are basic and core practices for a QA specialist?
A. QA Analyst identifies all functional items and give possible cases to test.
118. What are basic elements in defect report?
A. Defect report consists of:
i. program to be tested
ii. Tester name
iii. Date and time
iv. Severity
v. Summary
vi. Reason(optional)
vii. Priority
viii. Assigned to etc…
119. How do you prioritize testing task with in a project?
A. Depends on the severity the priority will be decided depends on the functionality of the test case.
120. Do you know of metrics that help you in estimate the size of the testing efforts?
A. We can use benchmark testing to develop metrics.
121. Discuss economics of automation and role of metrics in testing?
A. Economics of automation depends on no.of external interfaces, types of interface and maturity in application.
122. What methodologies do you need to develop test cases?
A. To develop test cases, we can use functionality list and standards of the organization.
123. Difference between test strategy and test plan?
A. Test strategy specifies the mapping between the factors and development stages. Test plan specifies actual process and schedule of testing of that project.
124. If you do stress testing? What conclusions can you arrival?
A. Correctness of application. When you run an application at the maximum values of resources.
125. What is difference between CMM and CMMI?
A. CMM/Integrated
126. What is compilation define w.r.t Load runner?
A. Load Runner point of view, compilation means that the Vuser script consists of correct syntaxes and semantics.
127. What is s/w defect life cycle?
128. What is equivalence partitioning?
A. Equivalence partitioning is used to combine same type of test cases related to single functionality/feature/module.
129. What type of scripting techniques for test automation do you know?
A. C-oriented TSL, VB-oriented SQA suite and Java-oriented silk test.
130. What criteria would you used to select web transactions for Load testing?
A. Web server related criteria Ex: e-business Vuser type in load runner.
131. Explain some techniques for developing s/w components w.r.t testability?
A. V-model
132. Describe components of a typical test plan such as tools for interactive products and database products as well as cause and effect graphs and data flow diagrams?
A. Depends on DFD testers imagine an approach to test a factor.
133. When have you had to focus on data integrity?
A. In integrating testing we can concentrate on data integrity.
134. How to import a DLL file in TSL Script?
A. By compiled module concept, logical DLLs.
135. How to write virtual API scripts in Test Director?
A. Test Director provides a facility of launching option connected to functional testing tool, which creates test script.
136. What is requirement phase testing?
A. Walk through, Reviews and Inspections.
137. What is Design phase testing?
A. Reviews, Inspections and prototypes.
138. What is program phase testing?
A. White-box testing/structural.
139. What is back-end testing? How to do?
A. Database testing is called back-end testing.
140. Why you are following Water-fall model?
A. There is no time and cost restrictions, we can choose waterfall model to develop an application.
141. When to use iterative model, Spiral model, RAD model?
142. What are the different bug-tracking tools?
A. Test Director, Test manager etc.
|
Written on 10:27 PM by MURALI KRISHNA
Test Execution Process
The preparation to test the application is now over. The test team should next plan the execution of the test on the application. In this section, we will see how test execution is performed.
Stages of Testing
Three passes
Tests on the application are done on stages. Test execution takes place in three passes or sometimes four passes depending on the state of the application. They are:
Pre IST or Pass 0: This is done to check the health of the system before the start of the test process. This stage may not be applicable to most test process. Free form testing will be adopted in this stage.
Comprehensive or Pass 1: All the test scripts developed for testing are executed. Some cases the application may not have certain module(s) ready for test, hence they will be covered comprehensively in the next pass. The testing here should not only cover all test cases but also business cycles as defined in the application.
Discrepancy or Pass 2: All Test scripts that have resulted in a defect during the comprehensive pass should executed. In other words, all defects that have been fixed should be retested. Function points that may be affected by the defect should also be taken up for testing. Automated test scripts captured during the pass one are used here. This type of testing is called as Regression testing. Defects that are not fixed will be executed only after they are fixed.
Sanity or Pass 3: This is the final round in the test process. This is done either at the client's site or at Same Organization depending on the strategy adopted. This is done in order to check if the system is sane enough for the next stage i.e. UAT or production as the case may be under a isolated environment. Ideally the defects that are fixed from the previous pass are checked and freeform testing done to ensure integrity is conducted.
|
Written on 10:23 PM by MURALI KRISHNA
Test Preparation Process
Baseline Documents
Construction of an application and testing are done using certain documents. These documents are written in sequence, each of it derived from the previous document.
Business Requirement
This document describes users needs for the application. This is done over a period of time, and going through various levels of requirements. This should also portrays functionalities that are technically feasible within the stipulated times frames for delivery of the application.
As this contains user perspective requirements. User Acceptance Test is based on this document.
How to read a Business Requirement?
In case of the Integrated Test Process, this document is used to understand the user requirements and find the gaps between the User Requirement and Functional Specification.
User Acceptance Test team should break the business requirement document into modules depending on how the user will use the application. While reading the document, test team should put themselves as end users of the application. This document would serve as a base for UAT test preparation.
Functional Specification
This document describes the functional needs, design of the flow and user maintained parameters. These are primarily derived from Business Requirement document, which specifies the client's business needs.
The proposed application should adhere to the specifications specified in this document. This is used henceforth to develop further documents for software construction and validation and verification of the software.
In order to achieve synchronization between the software construction and testing process. Functional Specification (FS) serves as the Base document.
How to read a Functional Specification?
The testing process begins by first understanding the functional specifications. The FS is normally divided into modules. The tester should understand the entire functionality that is proposed in the document by reading it thoroughly.
It is natural for a tester at this point to get confused on the total flow and functionality. In order to overcome these, it is advisable for the tester to read the document multiple times, seeking clarifications then and there until clarity is achieved.
Testers are then given a module or multiple modules for validation and verification. These modules then become the tester's responsibility.
The Tester should then begin to acquire an in-depth knowledge of their respective modules. In the process, these modules should be split into segments like field level validations, module rules, business rules etc. In order to do the same modules precisely the tester should interpret importance and its role within the application.
A high level understanding of the data requirements for respective modules is also expected from the tester at this point.
Interaction with test lead at this juncture is crucial to draw a testing approach, like an end-to-end test coverage or individual test. (Explained later in the document)
Tester's Reading Perspective
Functional specification is sometimes written assuming some level of knowledge of the Testers and constructors. We can categorize the explanations by
Explicit Rules: Functionality expressed as conditions clearly in writing, in the document.
Example
Date of a particular field should be system date
Implicit Rules: Functionality that is implied based on what is expressed as a specification/condition or requirement of a user.
Example
FS would mention the following for a deposit creation
Start Date Field: Should be = or > than the system date
Maturity Date Field: Should be = or > than the system date
Under this condition, the implied specification derived is that, Start date should not be equal to the maturity date
The tester must also bear in mind, the test type i.e. Integrated System Testing (IST) or User Acceptance Testing (UAT). Based on this, he should orient his testing approach.
Design Specification
This document is prepared based on the functional specification. It contains the system architecture, table structures and program specifications. This is ideally prepared and used by the construction team. The Test Team should also have a detailed understanding of the design specification in order to understand the system architecture.
System specification This document is a combination of functional specification and design specification. This is used in case of small applications or an enhancement to an application. Under such situations it may not be advisable make two documents.
Prototype
This is look and feel representation of the application that is proposed. This basically shows the placement of the fields, modules and generic flow of the application. The main objective of the prototype is to demonstrate the understanding of the application to the users and obtain their buy-in before actual design and construction begins.
The development team also uses the prototype as a guide to build the application. This is usually done using HTML or MS PowerPoint with user interaction facility.
Scenarios in Prototype
The flow and positioning of the fields and modules are projected using several possible business scenarios derived from the application functionality.
Testers should not expect all possible scenarios to be covered in the prototype.
Flow of Prototype
The flow and positioning are derived from initial documentation off the project. A project is normally dynamic during initial stages, and hence tester should bear in mind the changes to the specification, if any, while using the prototype to develop test conditions.
It is a value addition to the project when tester can identify mismatches between the specifications and prototype, as the application can be rectified in the initial stages itself.
|
Written on 3:10 AM by MURALI KRISHNA
Performance testing:
1. Performance testing is designed to test run time performance of software within the context of an integrated system. It is not until all systems elements are fully integrated and certified as free of defects the true performance of a system can be ascertained.
2. Performance tests are often coupled with stress testing and often require both hardware and software infrastructure. That is, it is necessary to measure resource utilization in an exacting fashion. External instrumentation can monitor intervals, log events. By instrument the system, the tester can uncover situations that lead to degradations and possible system failure.
Security testing:If your site requires firewalls, encryption, user authentication, financial transactions, or access to databases with sensitive data, you may need to test these and also test your site's overall protection against unauthorized internal or external access.
Exploratory Testing:Often taken to mean a creative, internal software test that is not based on formal test plans or test cases; testers may be learning the software as they test it.
Benefits Realization tests: With the increased focus on the value of Business returns obtained from investments in information technology, this type of test or analysis is becoming more critical. The benefits realization test is a test or analysis conducted after an application is moved into production in order to determine whether the application is likely to deliver the original projected benefits. The analysis is usually conducted by the business user or client group who requested the project and results are reported back to executive management.
Mutation Testing:Mutation testing is a method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation requires large computational resources.
Sanity testing:Typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems to a crawl, or destroying databases, the software may not be in a 'sane' enough condition to warrant further testing in its current state.
Build Acceptance Tests: Build Acceptance Tests should take less than 2-3 hours to complete (15 minutes is typical). These test cases simply ensure that the application can be built and installed successfully. Other related test cases ensure that Testing received the proper Development Release Document plus other build related information (drop point, etc.). The objective is to determine if further testing is possible. If any Level 1 test case fails, the build is returned to developers un-tested.
Smoke Tests : Smoke Tests should be automated and take less than 2-3 hours (20 minutes is typical). These tests cases verify the major functionality a high level. The objective is to determine if further testing is possible. These test cases should emphasize breadth more than depth. All components should be touched, and every major feature should be tested briefly by the Smoke Test. If any Level 2 test case fails, the build is returned to developers un-tested.
Bug Regression Testing :Every bug that was “Open” during the previous build, but marked as “Fixed, Needs Re-Testing” for the current build under test, will need to be regressed, or re-tested. Once the smoke test is completed, all resolved bugs need to be regressed. It should take between 5 minutes to 1 hour to regress most bugs.
Database Testing: Database testing done manually in real time, it check the data flow between front end back end.Observing that operations, which are operated on front-end is effected on back-end or not.The approach is as follows:
While adding a record there' front-end check back-end that addition of record is effected or not. So same for delete, update, Some other database testing checking for mandatory fields, checking for constraints and rules applied on the table , some time check the procedure using SQL Query analyzer.
Functional Testing (or) Business functional testing:All the functions in the applications should be tested against the requirements document to ensure that the product conforms with what was specified.(They meet functional requirements)
Verifies the crucial business functions are working in the application. Business functions are generally defined in the requirements Document. Each business function has certain rules, which can’t be broken. Whether they applied to the user interface behavior or data behind the applications. Both levels need to be verified. Business functions may span several windows (or) several menu options, So simply testing that all windows and menus can be used is not enough to verify the business functions. You must verify the business functions as discrete units of your testing.
Functional testing
Study SRS
Identify Unit Functions
For each unit function
Take each input function
Identify Equivalence class
Form Test cases
Form Test cases for boundary values
From Test cases for Error Guessing
Form Unit function v/s Test cases, Cross Reference Matrix
User Interface Testing (or) structural testing: It verifies whether all the objects of user interface design specifications are met. It examines the spelling of button test, window title test and label test. Checks for the consistency or duplication of accelerator key letters and examines the positions and alignments of window objects.
Volume Testing: Testing the applications with voluminous amount of data and see whether the application produces the anticipated results. (Boundary value analysis).
Stress Testing: Testing the applications response when there is a scarcity for system resources.
Load Testing: It verifies the performance of the server under stress of many clients requesting data at the same time.
Installation testing: The tester should install the systems to determine whether installation process is viable or not based on the installation guide.
Configuration Testing: The system should be tested to determine it works correctly with appropriate software and hardware configurations.
Compatibility Testing: The system should be tested to determine whether it is compatible with other systems (applications) that it needs to interface with.
Documentation Testing: It is performed to verify the accuracy and completeness of user documentation.
This testing is done to verify whether the documented functionality matches the software functionality.
The documentation is easy to follow, comprehensive and well edited.
If the application under test has context sensitive help, it must be verified as part of documentation testing .
|
Written on 3:09 AM by MURALI KRISHNA
UNIT TESTING :
By knowing the inner logic the program the test what you conduct is Unit Testing. or Testing the piece/unit of a program
Unit testing is a procedure used to validate that a particular module of source code is working properly. The procedure is to write test cases for all functions and methods so that whenever a change causes a regression, it can be quickly identified and fixed.
Benefits:
The goal of unit testing is to isolate each part of the program and show that the individual parts are correct. Unit testing provides a strict, written contract that the piece of code must satisfy. As a result, it affords several benefits.
1) Facilitates Change
2) Simplifies Integration
3) Documentation
4) Separation of Interface from Implementation
Integrated Systems Testing
Integrated System Testing (IST) is a systematic technique for validating the construction of the overall Software structure while at the same time conducting tests to uncover errors associated with interfacing. The objective is to take unit tested modules and test the overall Software structure that has been dictated by design. IST can be done either as Top down integration or Bottom up Integration.
System Testing:
System testing is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of Black box testing, and as such, should require no knowledge of the inner design of the code
System testing is actually done to the entire system against the Functional Requirement Specifications (FRS) and/or the System Requirement Specification (SRS). Moreover, the System testing is an investigatory testing phase, where the focus is to have almost a destructive attitude and test not only the design, but also the behavior and even the believed expectations of the customer. It is also intended to test up to and beyond the bounds defined in the software/hardware requirements specifications.Remaining All Testing Models comes under System Testing.
User Acceptance Testing:
User Acceptance Testing (UAT) is performed by Users or on behalf of the users to ensure that the Software functions in accordance with the Business Requirement Document. UAT focuses on the following aspects:
• All functional requirements are satisfied
• All performance requirements are achieved
• Other requirements like transportability, compatibility, error recovery etc. are satisfied
• Acceptance criteria specified by the user is met.
Sample Entry and Exit Criteria for User Acceptance Testing
Entry Criteria
♦ Integration testing sign off was obtained
♦ Business requirements have been met or renegotiated with the Business Sponsor or representative
♦ UAT test scripts are ready for execution
♦ The testing environment is established
♦ Security requirements have been documented and necessary user access obtained
Exit Criteria♦ UAT has been completed and approved by the user community in a transition meeting
♦ Change control is managing requested modifications and enhancements
♦ Business sponsor agrees that known defects do not impact a production release—no remaining defects are rated 3, 2, or 1
|
Written on 3:05 AM by MURALI KRISHNA
Bug life cycle
Bug Life Cycle starts with an unintentional software bug/behavior and ends when the assigned developer fixes the bug. A bug when found should be communicated and assigned to a developer that can fix it. Once fixed, the problem area should be re-tested. Also, confirmation should be made to verify if the fix did not create problems elsewhere. In most of the cases, the life cycle gets very complicated and difficult to track making it imperative to have a bug/defect tracking system in place.
Following are the different phases of a Bug Life Cycle:
Open: A bug is in Open state when a tester identifies a problem area
Accepted: The bug is then assigned to a developer for a fix. The developer then accepts if valid.
Not Accepted/Won’t fix: If the developer considers the bug as low level or does not accept it as a bug, thus pushing it into Not Accepted/Won’t fix state.
Such bugs will be assigned to the project manager who will decide if the bug needs a fix. If it needs, then assigns it back to the developer, and if it doesn’t, then assigns it back to the tester who will have to close the bug.
Pending: A bug accepted by the developer may not be fixed immediately. In such cases, it can be put under Pending state.
Fixed: Programmer will fix the bug and resolves it as Fixed.
Close: The fixed bug will be assigned to the tester who will put it in the Close state.
Re-Open: Fixed bugs can be re-opened by the testers in case the fix produces problems elsewhere.
1. New: When bug rises then it is in the New State.
2. Open: Developer Check the Bug Then it is in the Open state
3.Fixed: Developer Fixes the Bug, Then State is fixed
4.Close:Tester Checks again, if bug is not raised then it is Closed State.
5. Reopen: Again It is raised then it is in Reopen State.
|
