12. Software Testing

Question 1

Reasons for testing

Answer 1

1. detect defects
2. support design and implementation
3. prevent introduction of defects
4. document behaviour of system
5. demonstrate system meets specification

Question 2

testing concepts

Answer 2

interface
- expected service of a system

failures
- deviation from expected system behaviour

defects
- causes failure of system

slips
- actions by programmers that introduces defects

Question 3

scales of test

Answer 3

1. unit test
2. integration test
3. acceptance test

Question 4

test terminologies

Answer 4

test case
- set of actions to be performed on software with an expected outcome

test
- execution of a test case

testing
- practice of creating, maintaining, evaluating test cases

Question 5

defects testing

Answer 5

goal
- discover defects to be rectified

derived from
- architecture and design documents

Question 6

acceptance testing

Answer 6

goals
- demonstrate system meets requirements

derived from
- requirement specification

Question 7

behavioural driven development

Answer 7

derive test cases from a collection of user stories and scenarios

user story
scenario
steps
step functions
API
implementation

Question 8

mapping steps in test case

Answer 8

scenario
GIVEN –> how to setup test

WHEN –> actions to take during test

THEN –> assertions to be made and output at the end of the test

Question 9

Good practices for BDD

Answer 9

1. keep scenarios short
2. have individual step short
3. comply with GWT pattern
4. write features in user domain language
5. use frameworks sot reduce redundancy
6. develop feature and implementation gradually
7. work with customers to validate features

Question 10

limitation of BDD

Answer 10

1. specification by example which needs many examples
2. philosophy makes abstraction difficult
3. need to maintain steps definitions as features changes
4. hard coding of dependencies
5. only one level of abstraction possible with gherkin
6. gherkin steps sequential so all combinations have to be expressed

Question 11

smoke test (Define)

Answer 11

A smoke test is a quick automated test to make sure that there arent’t any visable signs of problems with the system.

Question 12

What is a pull request (Define)

Answer 12

A pull request – also referred to as a merge request – is an event that takes place in software development when a contributor/developer is ready to begin the process of merging new code changes with the main project repository.

Question 13

When do developers merge code?

Answer 13

When do developers merge code?

Question 14

Development and testing is done in 4 servers.
In what order does the work flow through them?

Answer 14

1. DEV/Development Server - Dev work
2. SIT /system integration testing server - Functional and regression testing
3. UAT/ User acceptance testing server - Where customers test it and we fix any errors.
4. PROD/production server - Published and live for the public to use.

Question 15

What is an (system) integration test, and a unit test?

Answer 15

An integration test is a test that including a function that will run all the way to the database and back so make sure all of the components are functioning together. A unit test is a test that tests business logic. It is done by the developers. It is best practice but not always done.