Testing

Question 1

What is a syntax error?

Answer 1

When the compiler or interpreter doesn’t understand something you’ve typed because it doesn’t follow the rules or grammar of the programming language.

Question 2

What is a logic error?

Answer 2

When the compiler or interpreter is able to run the program, but the program does something unexpected.

Question 3

How can syntax errors be diagnosed?

Answer 3

By compilers or interpreters - they’ll be unable to turn the source code into machine code and a syntax error (with its location) will be returned.

Question 4

Why are logic errors more difficult to diagnose and track down?

Answer 4

• compilers and interpreters won’t pick them up

- found through general use of the program and by systematically testing it using a test plan.

Question 5

Why is functionally testing worth doing?

Answer 5

• essential part of development process

- good way to spot logic errors

Question 6

What is the main aim of testing?

Answer 6

• if the program actually meets initial requirements

- i.e. it does exactly what you want without breaking or producing errors

Question 7

When should functionality testing be used?

Answer 7

• throughout writing your program

- better to spot errors and fix them as early as possible

Question 8

What is a performance test?

Answer 8

Tests how quickly certain features run and their impact on computer resources.

Question 9

What is a usability test?

Answer 9

Tests how user friendly the interface and features are.

Question 10

What is a security test?

Answer 10

Tests vulnerability to attacks and how securely data is stored.

Question 11

What is a load/stress test?

Answer 11

Tests how it copes under extreme conditions e.g. lots of users at the same time.

Question 12

A traditional diagram to follow when testing is the software developing cycle which is what?

Answer 12

• Requirements (what does the customer want the program to do?)
• Design (How will the program meet the requirements?)
• Implementation (writing the program to be specified design)
• Testing (Does the program meet the requirements?)
• Maintenance (Program output but continued updated needed)

Question 13

Testing is a key part of what?

Answer 13

Software Development Cycle

Question 14

The type type of testing will impact what?

Answer 14

Software Development Cycle

Question 15

What is final testing?

Answer 15

• the program goes through the development cycle once
• all required features are added at the same time
• program is tested against initial requirements of the customer if it meets them the program is signed off.
• customer will get what they asked for but maybe not what they really want.

Question 16

What is iterative testing?

Answer 16

• the program will go through the development a few times.
• idea is to try and get the program to match what the customer really wants
• the requirements in the first cycle might only include the main features of the program
• at the start of each cycle the requirements will be adjusted (e.g. by adding new details and features)

Question 17

What will a test plan do?

Answer 17

Outline exactly what you’re going to test and how you’re going to test it. It should cover all the possible paths through a program.

Question 18

What will a good test plan do?

Answer 18

Anticipate all the possible issues with the program and select appropriate test data to test for these issues.

Question 19

Test data could be what categories?

Answer 19

• normal data
• erroneous data
• extreme (boundary) data

Question 20

What is normal data?

Answer 20

Things a user is likely to input into a program.

Question 21

What is extreme (boundary) data?

Answer 21

Values at the limit of what the program should be able to handle.

Question 22

What is erroneous data?

Answer 22

Inputs that the program should not accept.