TDD Workshop

1.

1 point

What benefits can TDD bring to a project?

Unit tests can be used as a safety net for regression.

Leaves room for interpretation on how to develop a component.

Reduced time for debugging.

Constant feedback from each component.

2.

1 point

What is considered to be a problem for unit tests?

The unit test is too short.

The unit test refers to just one requirement.

The unit test takes too long to execute.

The unit test covers just one functionality / task.

3.

1 point

What does TDD stands for?

Technical Driven Development

Test Driven Development

Test Deriving Development

Test Design Development

4.

1 point

What tests are build and run in D-TDD?

Functional tests

Unit tests

Acceptance tests

User tests

5.

1 point

Which is a property of acceptance tests?

They focus on the “what” and not on the “how”.

They are owned by the testing team.

They contain as much details as possible to cover all UACs.

They are formal.

6.

1 point

Who is identifying the acceptance tests?

The project manager.

The client or the PO.

The tester with the client or PO.

The whole developing team.

7.

1 point

What is the A-TDD cycle?

c. Select story – develop functionality - write acceptance tests – write unit tests – refactor functionality – repeat

b. Select story – write unit tests – write acceptance tests – develop functionality – repeat

d. Select story – develop functionality - write acceptance tests – write unit tests – repeat

Select story – write acceptance tests – write unit tests – develop functionality – repeat

8.

1 point

Which are the TDD levels?

Acceptance TDD and Developer TDD (A-TDD and D-TDD)

Acceptance TDD and Developing TDD (A-TDD and D-TDD)

Accepting TDD and Developer TDD (A-TDD and D-TDD)

Accepting TDD and Developing TDD (A-TDD and D-TDD)

9.

1 point

The TDD motto “red, green, refactor” has the following explanation:

Red: Write a test that fails. Green: Write just enough code to pass the failing test. Refactor: Change the code to remove duplication and redundancy.

Red: Write a test that fails. Green: Re-write the test to make it pass. Refactor: Change the code to remove duplication and redundancy.

Red: Write a piece of code that fails. Green: Write the code in order for it to pass. Refactor: Change the code to remove duplication and redundancy.

Red: Write a test that fails. Green: Write just enough code to pass the failing test. Refactor: You re-write the code.

10.

1 point

When starting the work on a new story, then:

The developer can start writing the code without other tasks.

The unit tests and code implementation need to be done.

None of the above.

The acceptance test, the unit tests and code implementation need to be done.