Week 4

Question 1

What is Polling?

Answer 1

A method where a program repeatedly checks for new data or status at regular intervals

Question 2

What are Events?

Answer 2

A method where a program waits for a signal or notification that something has happened

An object that contains information about a state change in a source

Question 3

What is a quick comparison between Polling and Events?

Answer 3

Polling = Asking regularly.

Events = Waiting for a signal.

Question 4

When would you use Events and Listeners?

Answer 4

Any situation where your program is waiting for something to happen but you cannot make it happen

Question 5

What is a Source?

Answer 5

An object that generates an event

Question 6

What is a Listener?

Answer 6

An object that is notified of an event occuring

An event listener has a different method for each type of event notification it is interested in

Question 7

What is a Listener Interface?

Answer 7

To be notified of events a class must implement a Listener Interface

Question 8

What is Integration Testing?

Answer 8

Where multiple components are grouped together (integrated) to form final system and tested

Unexpected behaviour arise at this point, which is checked for here

Question 9

What is System Testing?

Answer 9

Testing the entire system as a whole

Question 10

What is User Acceptance Testing?

Answer 10

UAT plans developed during requirements analysis phase and composed by users

UAT performed in user environment that resembles production environment and uses realistic data

UAT ensures that the delivered system meets the users requirements and system is ready for use in real time

Validation activity rather than a verifiction activity

Question 11

What are advantages of the V model?

Answer 11

Highly structure, phases completed one at a time

Works well where all requirements are understood

Simple to understand

Easy to manage - each phase has a definite end with a review

Question 12

What are disadvantages of the V model?

Answer 12

Once project is in the testing phase it is difficult to go back and change functionality

Not suitable for projects where requirements might change

No working software created until later in the cycle

Question 13

What is Static Testing?

Answer 13

Assessing documents (review, walkthroughs, …)

Question 14

What is Dynamic Testing?

Answer 14

Testing that involves executing program code

eg. White box testing, black box testing etc.

Question 15

What is White Box Testing?

Answer 15

Testing where the internals of the program are known, so can test explicit paths through the system (code coverage)

Question 16

What is Black Box Testing?

Answer 16

Treats code as “black box”, and therefore is only concerned with functionality

Question 17

What is Grey Box Testing?

Answer 17

Know both the required functionality and also some of the implementation concepts (and/ or access to data stores not user accessible in the live system) which can be used in test design, but not code base exposed)

Question 18

What are the advantages of White Box?

Answer 18

Code can be seen so tests can be designed to test many paths through the program

Question 19

What are disadvantages of White Box?

Answer 19

Knowledge of the internals will influence the testing - can lead to bias in test design

Question 20

What are advantages of Black Box?

Answer 20

No knowledge of internals so no “programmer bias” - more likely to result in tests no expected by the programmer

Question 21

What are disadvantages of Black Box?

Answer 21

High probability that tests will only test small number of paths through the program