Dependency Testing: Examines an application's requirements for pre-existing software, initial states and configuration in order to maintain proper functionality.
Depth Testing: A test that exercises a feature of a product in full detail. Dynamic Testing: Testing software through executing it. See also Static Testing.
Emulator: A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system. Endurance Testing: Checks for memory leaks or other problems that may occur with prolonged execution.
End-to-End testing: Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
Equivalence Class: A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification.
Equivalence Partitioning: A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes. Error: A mistake in the system under test; usually but not always a coding mistake on the part of the developer. Exhaustive Testing: Testing which covers all combinations of input values and preconditions for an element of the software under test. Functional Decomposition: A technique used during planning, analysis and design; creates a functional hierarchy for the software.
Functional Specification: A document that describes in detail the characteristics of the product with regard to its intended features. Gorilla Testing: Testing one particular module, functionality heavily. Gray Box Testing: A combination of Black Box and White Box testing methodologies: testing a piece of software against its specification but using some knowledge of its internal workings.
High Order Tests: Black-box tests conducted once the software has been integrated. 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. Integration Testing: Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. Installation Testing: Confirms that the application under test recovers from expected or unexpected events without loss of data or functionality.
Events can include shortage of disk space, unexpected loss of communication, or power out conditions. Load Testing: See Performance Testing. Localization Testing: This term refers to making software specifically designed for a specific locality. Loop Testing: A white box testing technique that exercises program loops. Metric: A standard of measurement.
Software metrics are the statistics describing the structure or content of a program. A metric should be a real objective measurement of something such as number of bugs per lines of code. Monkey Testing: Testing a system or an Application on the fly, i. Mutation Testing: Testing done on the application where bugs are purposely added to it. Negative Testing: Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing. The cycles are typically repeated until the solution reaches a steady state and there are no errors.
See also Regression Testing. Path Testing: Testing in which all paths in the program source code are tested at least once. Performance Testing: Testing conducted to evaluate the compliance of a system or component with specified performance requirements.
Often this is performed using an automated test tool to simulate large number of users. Also know as "Load Testing". Positive Testing: Testing aimed at showing software works. Also known as "test to pass". See also Negative Testing. Quality Assurance: All those planned or systematic actions necessary to provide adequate confidence that a product or service is of the type and quality needed and expected by the customer. Quality Audit: A systematic and independent examination to determine whether quality activities and related results comply with planned arrangements and whether these arrangements are implemented effectively and are suitable to achieve objectives.
Quality Circle: A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality.
Quality Control: The operational techniques and the activities used to fulfill and verify requirements of quality. Quality Management: That aspect of the overall management function that determines and implements the quality policy. Quality Policy: The overall intentions and direction of an organization as regards quality as formally expressed by top management. Quality System: The organizational structure, responsibilities, procedures, processes, and resources for implementing quality management.
Race Condition: A cause of concurrency problems. Multiple accesses to a shared resource, at least one of which is a write, with no mechanism used by either to moderate simultaneous access. Ramp Testing: Continuously raising an input signal until the system breaks down. Recovery Testing: Confirms that the program recovers from expected or unexpected events without loss of data or functionality.
Regression Testing: Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made. Release Candidate: A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs which ideally should be removed before the final version is released.
Sanity Testing: Brief test of major functional elements of a piece of software to determine if its basically operational. See also Smoke Testing. You can send suggestions at www-qa w3. The glossary is given to fix the terms used at W3C for the Quality Assurance and Conformance activity. It should be used as a definition for working groups to define their terms in Technical Reports and documentation issued inside and outside W3C.
W3C liability , trademark , document use and software licensing rules apply. Your interactions with this site are in accordance with our public and Member privacy statements. Quality Assurance glossary This document has been created to define the use of vocabulary among our specifications and Quality Assurance activity.
This is in contrast to some test cases that may test a combination of rules. C Certification Acknowledgement that a validation was completed and criteria established by the certifying organization for issuing a certificate or branding has been met. Class of Products The generic name for the group of products or services that would implement, for the same purpose, the specification, i. A specification may identify several classes of products. Compliance This term is deprecated.
See Conformance. Conformance Fulfillment by a product, process, systems, or service of a specified set of requirements. Conformance clause A section of the specification that defines the requirements, criteria, or conditions to be satisfied by an implementation in order to claim conformance.
Conformance Degree Part of a nested hierarchy of multiple types of conformance allowed within a specification. Conforming Document Document that obeys the rules defined in the recommendation it was written for. Computer Network. Compiler Design.
Computer Organization. Discrete Mathematics. Ethical Hacking. Computer Graphics. Web Technology. Cyber Security. C Programming. Control System. Data Mining. Data Warehouse. Javatpoint Services JavaTpoint offers too many high quality services. There are two kinds of Quality: Quality of Design: Quality of Design refers to the characteristics that designers specify for an item.
Importance of Quality We would expect the quality to be a concern of all producers of goods and services. Software Quality Assurance Software quality assurance is a planned and systematic plan of all actions necessary to provide adequate confidence that an item or product conforms to establish technical requirements.
SQA Encompasses A quality management approach Effective Software engineering technology methods and tools Formal technical reviews that are tested throughout the software process A multitier testing strategy Control of software documentation and the changes made to it. A procedure to ensure compliances with software development standards Measuring and reporting mechanisms.
SQA Activities Software quality assurance is composed of a variety of functions associated with two different constituencies? Following activities are performed by an independent SQA group: Prepares an SQA plan for a project: The program is developed during project planning and is reviewed by all stakeholders. The plan governs quality assurance activities performed by the software engineering team and the SQA group. The plan identifies calculation to be performed, audits and reviews to be performed, standards that apply to the project, techniques for error reporting and tracking, documents to be produced by the SQA team, and amount of feedback provided to the software project team.
Participates in the development of the project's software process description: The software team selects a process for the work to be performed. The SQA group reviews the process description for compliance with organizational policy, internal software standards, externally imposed standards e. ISO , and other parts of the software project plan. Reviews software engineering activities to verify compliance with the defined software process: The SQA group identifies, reports, and tracks deviations from the process and verifies that corrections have been made.
0コメント