Testing Flashcards

1
Q

What is a syntax error?

A

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.

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

What is a logic error?

A

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

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

How can syntax errors be diagnosed?

A

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.

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

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

A
  • compilers and interpreters won’t pick them up

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

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

Why is functionally testing worth doing?

A
  • essential part of development process

- good way to spot logic errors

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

What is the main aim of testing?

A
  • if the program actually meets initial requirements

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

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

When should functionality testing be used?

A
  • throughout writing your program

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

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

What is a performance test?

A

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

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

What is a usability test?

A

Tests how user friendly the interface and features are.

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

What is a security test?

A

Tests vulnerability to attacks and how securely data is stored.

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

What is a load/stress test?

A

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

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

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

A
  • 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)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Testing is a key part of what?

A

Software Development Cycle

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

The type type of testing will impact what?

A

Software Development Cycle

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

What is final testing?

A
  • 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.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What is iterative testing?

A
  • 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)
17
Q

What will a test plan do?

A

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.

18
Q

What will a good test plan do?

A

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

19
Q

Test data could be what categories?

A
  • normal data
  • erroneous data
  • extreme (boundary) data
20
Q

What is normal data?

A

Things a user is likely to input into a program.

21
Q

What is extreme (boundary) data?

A

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

22
Q

What is erroneous data?

A

Inputs that the program should not accept.