Validation (Testing code)

Question 1

What are the 4 different branches of testing?

Answer 1

Open box testing
Closed box testing
Automated testing
Manual testing

Question 2

What is open box testing?

Answer 2

Tester know the code when testing

Question 3

What is closed box testing?

Answer 3

Tester does not know the code when testing (compiled version)

Question 4

What is automated testing?

Answer 4

Large amounts of coded tests which are automated

Question 5

What is manual tetsing?

Answer 5

Tests which require user interaction

Question 6

What are the advantages of test-driven development?

Answer 6

• Integrates aspects of specifications, coding and testing
• ‘Plan’ before you ‘Write’ code
• Check you haven’t broke something when implementing something new

Question 7

What are the qualities of a good test?

Answer 7

Line coverage
Function coverage
Condition coverage
Path coverage
Entry/Exit coverage

Question 8

What is unit testing?

Answer 8

Testing individual pieces
Input: functional specifications of unit
Output: Pass/Fail
Performed by: Developer
Frequency: Multiple times a day

Question 9

What is integration testing?

Answer 9

Testing a combination of pieces
Input: functional specifications of subsystem
Output: Bug report
Performed by: Dev team (open box)
Frequency: Periodically

Question 10

What is release testing?

Answer 10

Testing the whole system works together
Input: Functional and non-functional specifications of system
Output: Bug report, sign off for acceptance testing
Performed by: Testing team (closed box)
Frequency: Prior to showing client

Question 11

What is acceptance testing?

Answer 11

Testing the system is accepted for active use
Input: User requirements
Output: Bug report, end of contract
Performed by: Quality Assurance Team
Frequency: End of each stage (agile) prior to release of software

Question 12

What is user testing?

Answer 12

Testing the system with real world users
Input: Actual users
Output: Bug report
Performed by: Real users
Frequency: After release

Question 13

What are the two types of user testing?

Answer 13

Alpha
- A few specific users (acceptance test with real users)
Beta
- Released for limited general use

Question 14

What is continuous integration?

Answer 14

Automatic building, testing and deployment of code once it is committed to a repository

Question 15

What is the process of continuous integration?

Answer 15

1. Version control
2. Automatic testing
3. Build configurations
4. Automatic deployment

Question 16

When would we use continuous integration?

Answer 16

When there is no client

Question 17

How can configuration management be used to generate different versions of software?

Answer 17

• Create build scripts that work for different platforms
• Each build script might pull in different libraries at build time that work for different platforms
• These build scripts get automatically triggered and deployed in the continuous integration process

Question 18

What is release management strategy?

Answer 18

Preparing periodic releases/updates for end users when there is no client

Question 19

What is version control?

Answer 19

Branch for release versions, so we can maintain past versions

Question 20

What is the process of version controlling?

Answer 20

Developer submits merge request
- If merge request passes test it is automatically build
- Code is reviewed by team members
- If approved, merge into version