Computing F452: Testing Key Terms

Just a few key terms for the Testing Unit of F452...

HideShow resource information
Testing
Checking the success and reliability of a system under a number of different circumstances. Because it is impossible to test everything that could happen, a testing plan is created to carefully ensure the areas most likely to go wrong are tested
1 of 23
Syntax Error
When code cannot be understood because because they do not follow the rules of programming. E.g. Spelling mistake
2 of 23
Logic Error
Mistakes in the design of the code that lead to wrong results or incorrect display. E.g. Code doesn't do what it is supposed to do
3 of 23
Run-time Error
Detected while the program is running. The errors, such as overflow or dividing by 0, are made by mistake or when not catering for external effects
4 of 23
Compiler
Software that translates a code in high level language into low level language such as machine code
5 of 23
Type Mismatch
Occurs when the program attempts to assign, operate or compare a value that is not a compatible data type. E.g. assigning a string to an integer variable
6 of 23
Overflow Error
Occurs during an arithmetic operation when the result of a calculation is too big for the space it has been reserved
7 of 23
Stack Overflow Error
Occurs usually during recursion, when the stacks exceeds the stack space reserved for a program or data structure
8 of 23
Test Data
Inputs used during testing and specified in the test plan
9 of 23
Black Box Testing
Testing by using inputs to ensure the expected output occurs. Not concerned with how the program works, just that it produces the desired outcomes
10 of 23
White Box Testing
Testing the logic of the code in a program. Testing the different routes of executions through a program to ensure all conditions work as expected
11 of 23
Valid Data
Inputs used during testing which the system should be able to process. Checks that the system works under normal conditions. E.g. 11/07/12
12 of 23
Borderline Data
Inputs used during testing that are on top or bottom of a range and that the system should process. E.g. 29/02/12 (Leap Day)
13 of 23
Invalid Data
Inputs used during testing which the system should reject or create an error message. Checks that the system validations work correctly. E.g. 67/32/12
14 of 23
Alpha Testing
Testing carried out by a restricted group within the company acting as though they were potential users
15 of 23
Beta Testing
Program is nearly complete and is released to potential users outside the company to test it in normal operating conditions
16 of 23
Acceptance Testing
Program is now complete and it is demonstrated to the end user. The purpose is to show that it works correctly and that all desired features are implemented
17 of 23
Debugging
Facilities that enable the programmer to investigate and locate errors in the code
18 of 23
Compiler Diagnostics
Messages generated by the compiler when converting code into executable
19 of 23
Breakpoints
Stopping the program at a specified point to check on the value of variables or to step through the code one line at a time
20 of 23
Variable Checks
Lists the contents of variables at specific points in the program. Allows the programmer to compare the contents to what is expected
21 of 23
Dry Runs
Working through parts manually to locate errors. Particularly useful for run-time errors
22 of 23
Trace Table
Created when recording a dry run to record the values of variables at different stages. A column is used for the instruction being executed and another for the value of the variables. New line indicates another instruction
23 of 23

Other cards in this set

Card 2

Front

When code cannot be understood because because they do not follow the rules of programming. E.g. Spelling mistake

Back

Syntax Error

Card 3

Front

Mistakes in the design of the code that lead to wrong results or incorrect display. E.g. Code doesn't do what it is supposed to do

Back

Preview of the back of card 3

Card 4

Front

Detected while the program is running. The errors, such as overflow or dividing by 0, are made by mistake or when not catering for external effects

Back

Preview of the back of card 4

Card 5

Front

Software that translates a code in high level language into low level language such as machine code

Back

Preview of the back of card 5
View more cards

Comments

No comments have yet been made

Similar Computing resources:

See all Computing resources »See all resources »