Testing

Question 1

Testing levels

Answer 1

• Unit testing
• Integration testing
• System testing
• Acceptance testing
• Regression testing

Question 2

Unit testing

Answer 2

• A unit test targets a small unit of code (method or class)
• Percentage of unit tests known as test coverage
• Ensure the code works as intended or whether any modifications are required
• High test covered of your code allows you to develop features without lots of manual testing

Question 3

Integration testing

Answer 3

• Accessing the interface between the software components
  read more on this…

Question 4

System testing

Answer 4

Overall testing of the system
- after components are developed and working together

Question 5

User acceptance testing (UAT)

Answer 5

• Performed by customers
• Includes Alpha and Beta testing
• Alpha is early on in development and limited group, lacks non functional attributes like performance
• Beta is closer to final product and

Question 6

Regression testing

Answer 6

• Checking that after a defect has been fixed, we havent broken something new

Question 7

Testing with j unit

Answer 7

• Within a test class
• Using @Test
• Normally each class has a seperate unit test class

Question 8

Characteristics of a good unit test

Answer 8

• Runs fast
• Separates or simulates environmental dependencies, such as databases, file systems, networks, queues and so on
• Is limited in scope
• Clearly reveals intention
• Should run an pass in isolation
• Often uses stubs and mock objects