Testing Terms and Terminology

(Source: Anonymous)

A

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

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

Ad Hoc Testing

Similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software before testing it. Also, we can call it Monkey Testing.

Agile Testing

Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm.

Alpha Testing
Testing of an application when development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.

Application Binary Interface (ABI)
A specification defining requirements for portability of applications in binary forms across different system platforms and environments.

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

Automated Software Quality (ASQ)
The use of software tools, such as automated testing tools, to improve software quality.

Automated Testing
Testing employing software tools that execute tests without manual intervention. Can be applied in GUI, performance, API, etc. testing.
The use of software to control the execution of tests, the comparision of actual outcomes to predicted outcomes, the setting up of test perconditions, and other test control and test reporting functions.

B

Backus-Naur Form
A Meta language used to formally describe the syntax of a language.

Basic Block
A sequence of one or more consecutive, executable statements containing no branches.

Basis Path Testing
A white box test case design technique that uses the algorithmic flow of the program to design tests.

Basis Set
The set of tests derived using basis path testing.

Baseline
The point at which some deliverable produced during the software engineering process is put under formal change control.

Beta Testing
Testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers.

Binary Portability Testing
Testing an executable application for portablity across system platforms and environments, usually for confrormation to an ABI specification.

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

• Testing the features and operational behavior of a product to ensure they correspond to its specifications.
• Testing that ignores the internal mechanism of a system or component and focuses solely on the outpurs generated in response to selected inputs and execution conditions.

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

For further terms and terminology - Click Here (Thankful to ISTQB)

SQL

SQL (Structured Query Language) is simply a language that is used to access the database. Ultimately, by accessing the database we can also manipulate data (information) over there.

In the market we have so many types of databases. Such as Oracle, DB2, Informix, Microsoft SQL Server, Sybase, MS Access, and other database systems.

SQL (Structured Query Language) is the only one language that we use to access and manipulate data in these database systems.

Test Director Overview

Application Testing is a complex process. Test Director helps organize and manage all phases of the testing process that encompasses the following steps:

• Organize and manage testing requirements [SPECIFYING REQUIREMENTS]; where we define testing scope, create requirements, detail requirements, and analyze requirements.
• Planning test; where we define test strategy, define test subjects, define tests, create requirement coverage, design test steps, automate tests, and analyze test plan.
• Executing test [RUNNING TESTS]; where we create test sets, schedule runs, run tests, and analyze test results.
• Tracking Defects, where we find defects, review new defects, repair open defects, test new build, and analyze defect data.

Q. How do you create tests from requirements in TD?

Once you have created the requirements tree, you use the requirement as a basis for defining the tests in your test plan tree and running tests in a test set.

There are 2 ways: (1) Convert requirement to tests, and (2) Generate a Test from requirements.

(1) Tools > Convert to Test > Convert All/ Convert Selected

(2) Right Click any requirement on Tree View ==> Generate Test.

Q. What are Test Director Projects?

TD projects are repositories that contain requirements, tests, testsets, test runs, defects, project documentation and customization information.

Q. What database application are used to store and manage TD information?

MS Access, Sybase, MS SQL, Oracle

Q. What are the 4 modules of Test Director?

1. Requirements
2. Test Plan
3. Test Lab
4. Defects

Q. How do you clear 'History' in TD?

1. Click TOOLs on the Upper right corner --> Clear History
2. Select the entity whose history you want to delete
3. Select the field whose history you want to delete
4. Upto '...date', select a date.

SCHEDULING, REQUIREMENT, TEST PLANNING

1. How do you schedule a test in Test Director?
2. How do you specify requirements?
3. How do you plan the tests?
4. How do you run the tests?
5. How do you do defect tracking?
6. How do you filter records in TD?
7. What information you put in requirements?
8. How do you view requirement history?
9. How do you view associated defects for a test requirement?
10. How do you attach or open WR script from TD?
11. How do you E-mail test?
12. What is Test Management Process in Test Director?
13. What is a Test Grid?
14. What data column is displayed by Test Grid?
15. What does Test Planning Involve?
16. What is a Test Plan Tree?
17. How do you associate defect with a Test?
18. What is the relationship of requirement and tests?
19. How do you design test steps in Test Plan module?
20. How do you generate an automated test template?
21. How do you add system test to a test plan tree?

TEST EXECUTION

1. What are the stages of Test Execution?
2. What are the elements of Execution Flow Diagram?
3. How do you set the Test Set on Failure Rules?
4. How do you add a Test Set in Test Lab Module?
5. What is scheduling test runs?
6. How do you run an automated test in TD?
7. What considerations should be considered when running tests on remote host?

DEFECT TRACKING

1. How do you track Defects?
2. How do you add defects?
3. What information do you include in Defect Reporting/ Tracking?
4. What are the status of defects?
5. How do you find matching defects?
6. How do you update defects?

TEST DIRECTOR ANALYSIS

1. What reports are available in Requirement Module?
2. What reports are available in Test Plan Module?
3. What reports are available in TEST Lab Module?
4. What reports are available in Defects Module?
5. How do you create a Report?
6. Tell about generating graphs in TD.
7. What are the different types of Graph in Requirement Module?
8. What are the different types of Graph in Test Plan Module?
9. What are the different types of Graph in Test Lab Module?
10. What are the different types of Graph in Defects Module?
11. What is Project Documents in TD?
12. How do you launch Document Generator?

Answers

How do you schedule a test in Test Director?

Go to TEST LAB --> Execution Flow --> Right Click on any Test --> Test Run Schedule --> Time Dependency --> Run at any time /or/ Run at a specified time []Date e.g.5/8/2005

How do you specify requirements?

Defining Testing Scope ==> Create Requirements ==> Detail Requirements ==> Analyze Requirements

How do you plan the tests?

Create a Test Plan based on Testing Requirements

Define Testing Strategy (How? What?) ==> Define Test Subjects ==> Define Tests ==> Create Requirment Coverage (Link each test with requirement) ==> Design Test Steps ==> Automate Tests ==> Analyze Test Plan

How do you run the tests?

Create Test Sets ==> Schedule Runs ==> Run Tests Manually/or/Automatedly ==> Analyze Test Results

How do you do defect tracking?

Add Defects ==> Review New Defects ==> Repair Open Defects ==> Test New Build ==> Analyze Defect Data

How do you filter records in TD?

1. Click Set Filter/Sort button => Filter dialog box opens and displays filter tab
2. Set a filter condition for a specific column
3. Define the filter condition
4. Ok [To add cross filters click Advanced Link]

What information you put in requirements?

Attachment, Author, Cover Status (Pass, Fail), Creation time/date, Modified, Name (Requirement Name), Priority, Product, Requirement ID, Reviewed, Type (hardware/software)

How do you view requirement history?

1. Select a Requirement in the tree
2. Click the History Tab

How do you view associated defects for a test requirement?

Select View >>> Associated Defect

OR, Right click a requirement >>> Associated Defect

How do you attach or open WR script from TD?

For attaching -> Go to TEST PLAN --> Attach ==> Open the script and the script gets attached. [You can attach file, URL, snapshot, and system info]

For opening WR script ==> From tree ==> Go to expand and find a WR script ==> copy from ==> browse to the script and open

Now, you can run the script from TD ==> by LAUNCH button

How do you E-mail test?

Right click any test on TREE VIEW ==> MAIL TESTS in TEST PLAN Module

What is Test Management Process in Test Director?

SPECIFY REQUIREMENTS (Analyze your application and determine your testing requirement) ==> PLAN TESTS (Create a test plan based on testing requirements) ==> EXECUTE TESTS (Create testsets and perform test runs) ==> TRACK DEFECTS (Report defects detected in your application and track how repqirs are progressing)

What is a Test Grid?

A Test Grid desplays all the tests in a TD Project. Each row diplays a separate test record. Each column represents a separate data-item.

To view the test grid, choose VIEW--> TEST GRID

Test Grid contains

1. Test Grid Toolbar (Copy, Paste, Set Filter, Sort, Select Column, Find etc.)
2. Grid Filter
3. Description tab
4. History tab

What data column is displayed by Test Grid?

Creation Data, Description, designer, estimated development time, execution status, modified, path, status, steps, subject, template, Test Name, Type.

What does Test Planning Involve? (What can you do in Test Plan Module?)

1. Creating a Test Plan Tree
2. Adding tests to a test plan tree
3. Viewing the test plan tree
4. Associating defects with a test
5. Mailing test
6. Finding tests in the test tree
7. Sorting
8. Modifying

What is a Test Plan Tree?

The typical application is too large to test as a whole. The Test Plan module enables you to divide your application according to functionality. You divide your application into units, or subjects, by creating a plan tree.

How do you associate defect with a Test?

View >>> Associate Defects

OR, right click the test and choose Associated Defects

What is the relationship of requirement and tests ?

It could be:

1. 1 to 1
2. 1 to many
3. many to 1

You can do it both ways Requirement ==> to ==> Tests; OR, Test ==>to==> Requirements

How do you design test steps in Test Plan module?

You add steps to a test using Design Step Editor. To create a test step;

1. Choose a test and click DESIGN STEPS tab
2. Click NEW STEP button or Right Click DESIGN STEP TAB and choose NEW STEP
3. Type a description and expected results
4. To insert a PARAMETER, click INSERT PARAMETER button
5. Click CLOSE to close Design Step Editor

How do you generate an automated test template?

1. In the test plan tree, choose the mannual test that you want to automate
2. Click the Design STEPS tab and click the GENERATE SCRIPT button
3. Choose an automated test type to convert to: WR-automated, LR-scenario or Quick Test -test.
4. Click the TEST SCRIPT tab to view the test template
5. Click LAUNCH button

How do you add system test to a test plan tree?

1. Choose Subject Folder in the Test Plan Tree
2. New Test Button OR Planning > NEW TEST
3. In the Test Type: Select SYSTEM TEST
4. In the TEST NAME Box, type a name of the test and OK

How does it look? Screen Shot View! (Source:Prakash Nepal's www.qaquestions.com)

Ref -HP/Mercury Interactive