What Do You Know About Test Driven Development (Tdd)?

Explanation
Kent Beck is the correct answer because he is a renowned software engineer and one of the pioneers of Test Driven Development (TDD). He is known for his contributions to the Agile software development methodology and for authoring the book "Test-Driven Development: By Example," which popularized the concept of TDD. Beck has been actively involved in promoting and practicing TDD, making him a significant figure in the development of this approach.

Explanation
TDD, or Test-Driven Development, was discovered in 2003. This development technique involves writing tests before writing the actual code, helping to ensure the code is functional and meets the desired requirements. It is a popular practice in software development, as it promotes better code quality and maintainability.

Explanation
In Test-Driven Development (TDD), the process involves writing tests before writing the actual code. Writing a test is a fundamental step in TDD, as it helps define the desired behavior of the code. Adding a test is also a common practice when new functionality needs to be implemented or existing functionality needs to be expanded. Running the test is essential to ensure that the code passes the test and behaves as expected. However, deleting a test is considered odd in TDD because tests are meant to provide a safety net and ensure the code's correctness. Deleting a test removes this safety net and can lead to potential issues and regressions in the code.

Explanation
The commonly applied structure for test cases usually includes validation, clean up, and execution. However, deleting test cases is not typically part of the structure. Test cases are usually created to test specific functionality or scenarios, and once they have served their purpose, they are not deleted but rather archived or kept for future reference. Deleting test cases may result in loss of valuable information and make it difficult to track the history of testing efforts.

Explanation
The odd one out in this list is "Total testing". The other options, software testing, compliance testing, and integration testing, are all specific types of testing that are commonly used in the context of Test-Driven Development (TDD). "Total testing" is not a recognized term in TDD or software testing practices, making it the odd one out.

Explanation
The study that found that using TDD meant writing more tests was conducted in 2005. This suggests that in the year 2005, a study was conducted to investigate the relationship between Test-Driven Development (TDD) and the number of tests written. The study likely found that practitioners of TDD tend to write more tests compared to those who do not use TDD. This finding could have implications for software development practices and highlight the importance of TDD in ensuring comprehensive test coverage.

Explanation
Keeping test oracles focused is one of the individual best practices in TDD. Test oracles refer to the expected outcomes or results of the tests. By keeping them focused, it means that the test cases should only focus on verifying a single specific behavior or functionality of the code. This helps in making the tests more clear, concise, and easier to understand. It also allows for easier maintenance and debugging of the tests, as any failures can be easily pinpointed to a specific oracle.

Explanation
In Test-Driven Development (TDD), separating common set-up and teardown logic is actually a best practice. This allows for reusability and maintainability of the test code, as common logic can be easily shared across multiple tests. Designing time related tests is also a best practice, as it ensures that the behavior of the code under different time conditions is properly tested. Testing test codes is another best practice, as it ensures that the test code itself is functioning correctly. However, assigning test codes is not a best practice in TDD, as it is not clear what is meant by "assigning" in this context.

Explanation
In Test-driven development (TDD), the sequence typically involves writing a failing test, then writing the code to make the test pass, and finally refactoring the code. The given sequence of numbers (5, 6, 4, 3) suggests that there are four tests involved in the TDD process. However, the correct answer is 6, which implies that there are six tests involved in TDD. This suggests that there might be additional tests or steps involved in the TDD sequence that are not mentioned in the given sequence of numbers.

Explanation
Building all knowing oracles is a practice to avoid in Test-Driven Development (TDD). An all knowing oracle is a test that checks the correctness of a system by comparing its output with the expected output, instead of focusing on the behavior of the system. This approach can lead to brittle tests that are tightly coupled to the implementation details, making it difficult to refactor or modify the code without breaking the tests. TDD encourages writing tests that focus on the behavior and functionality of the system, rather than relying on specific expected outputs.