Chapter 1 Flashcards

Keywords

1
Q

Coverage

A

Amount of testing performed by a set of test cases is called Test Coverage. … In other words, test coverage is defined as a technique which determines whether our test cases are actually covering the application code and how much code is exercised when we run those test cases

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Debugging

A

Debugging is the process of finding and resolving defects or problems within a computer program that prevent correct operation of computer software or a system. Debugging tactics can involve interactive debugging, control flow analysis, unit testing, integration testing, log file analysis, monitoring at the application or system level, memory dumps, and profiling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Defect

A

A defect is an error or a bug, in the application which is created. … These mistakes or errors mean that there are flaws in the software. These are called defects. When actual result deviates from the expected result while testing a software application or product then it results into a defect.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Error

A

“A mistake in code is called Error . ” Error found by tester is called defect , Defect accepted by development team is called Bug . And build does not meet the requirements then it is Failure

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

failure

A

A failure is when the build does not meet the requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Quality

A

quality: The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations. software quality: The totality of functionality and features of a software product that bear on its ability to satisfy stated or implied needs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Quality Assurance

A

Software Quality Assurance is about engineering process that ensures quality. Software Testing is to test a product for problems before the product goes live. Involves activities related to the implementation of processes, procedures, and standards

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

root cause

A

Root Cause Analysis is a systematic approach to identifying the underlying causes of an incident. It helps in taking appropriate steps, so the problem is addressed. In an ideal world, the software should have Zero defects, and it should not show any failure. Practically, it’s never possible. By effective QA processes, we can ensure that software has minimum defects. We can also ensure that there are the right techniques that can be followed to find the underlying cause of any defect. This process of identifying WHY the problem has occurred in the software is called Root Cause Analysis (RCA).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

test analysis

A

Test Analysis is the process of looking into test artifacts to base your test conditions/test cases. Hence, it is also called Test Basis. Testers can create Test Conditions by looking into the Application Under Test or use their experience. But mostly, test cases are derived from test artifacts

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

test basis

A

Test basis is defined as the source of information or the document that is needed to write test cases and also for test analysis. Test basis should be well defined and adequately structured so that one can easily identify test conditions from which test cases can be derived

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

test case

A

A TEST CASE is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly. The process of developing test cases can also help find problems in the requirements or design of an application

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

test completion

A

Test Completion is the last stage of the software testing life cycle. It results in a report that is a Test manager or a Test lead prepares that showcases the completed data from the test execution.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

test condition

A

Test conditions are the constraints that you should follow to test an application. …
Test conditions can be a piece of functionality or anything you want to verify. …
It is an item or event of a system that could be verified by one or more test cases. …
Good test conditions ensure a system is bug free.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

test control

A

Test Control is an activity of guiding and taking corrective action based on some metrics or information to improve efficiency and quality. Test Monitoring activity includes: … Finding and tracking the Test Metrics. Planning and Estimation, for deciding the future course of action, based on the metrics calculated

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

test data

A

Test data is data which has been specifically identified for use in tests, typically of a computer program. Some data may be used in a confirmatory way, typically to verify that a given set of input to a given function produces some expected result.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

test design

A

Test design is a process that describes “how” testing should be done. It includes processes for the identifying test cases by enumerating steps of the defined test conditions. The testing techniques defined in test strategy or plan is used for enumerating the steps.

17
Q

test execution

A

Test execution is the process of executing the code and comparing the expected and actual results. Following factors are to be considered for a test execution process: Based on a risk, select a subset of test suite to be executed for this cycle. Assign the test cases in each test suite to testers for execution.

18
Q

test implementation

A

Search Results
Featured snippet from the web
Test implementation is the practice of organizing and prioritizing tests. This is carried out by Test Analysts who implement the test designs as real test cases, test processes and test data. If you are observing the IEEE 829 standard, you must define these parameters as well : Test inputs

19
Q

test monitoring

A

Test Monitoring is a process of evaluating and providing feedback on the “currently in progress” testing phase. Test Control is an activity of guiding and taking corrective action based on some metrics or information to improve efficiency and quality.

20
Q

test object

A

A test object is an object that QuickTest creates in the test to represent the actual object in your application. QuickTest stores information on the object that will help it identify and check the object during the run session

21
Q

test objective

A

Test Objective is the overall goal and achievement of the test execution. The objective of the testing is finding as many software defects as possible; ensure that the software under test is bug free before release. List all the software features (functionality, performance, GUI…) which may need to test

22
Q

test oracle

A

A source to determine expected results to compare with the actual result of the software under test. An oracle may be the existing system (for a benchmark), other software, a user manual, or an individual’s specialized knowledge, but should not be the code.

23
Q

test planning

A

A TEST PLAN is a document describing software testing scope and activities. It is the basis for formally testing any software/product in a project. test plan: A document describing the scope, approach, resources and schedule of intended test activities.

24
Q

test procedure

A

A test procedure is a formal specification of test cases to be applied to one or more target program modules. Test procedures are executable. A process called the VERIFIER applies a test procedure to its target modules and produces an exception report indicating which test cases, if any, failed.

25
Q

test process

A

Search Results
Featured snippet from the web
Testing is the process of executing a program or part of a program with the intention of finding errors. The different phases of a test life cycle are Test Planning and Control, Test Analysis and Design, Test Implementation and Execution, Evaluating Exit Criteria and Reporting, and Test Closure.

26
Q

test suite

A

a test suite, less commonly known as a ‘validation suite’, is a collection of test cases that are intended to be used to test a software program to show that it has some specified set of behaviours.

27
Q

testware

A

Search Results
Featured snippet from the web
“Testware” is a term used to describe all of the materials used to perform a test. Testware includes test plans, test cases, test scripts, and any other items needed to design and perform a test.

28
Q

traceability

A

Traceability in software testing is the ability to trace tests forward and backward through the development lifecycle. Test cases are traced forward to test runs. … Test cases and test runs can also be traced backward to requirements. Traceability in software testing is often done using a traceability matrix.

29
Q

Validation

A

The process of evaluating software during the development process or at the end of the development process to determine whether it satisfies specified business requirements. Validation Testing ensures that the product actually meets the client’s needs.

30
Q

Verification

A

Verification is the process of evaluating work-products of a development phase to determine whether they meet the specified requirements. verification ensures that the product is built according to the requirements and design specifications.