It's fair to say that high code coverage and high performance are not needed for a well-designed unit test?

Question

When developing unit tests, from what I read, you should try to adhere to these principles:

• Isolate your tests from each other
• Check only one behavior at a time
• Make sure the test repeats.

On the other hand, these functions do not always correlate with a good test:

• High code coverage
• High performance

Is this a fair approach?

Answer 1

. . . () .

Answer 2

, , , , .

, , "", , , , .

Answer 3

- , , , .. , .

, , , . . , ( ), , , -, , . , .

Answer 4

() . , . , ( ) , , .

. , - . , - ; ; . ( ). , - , , , , : ; ; . , , . , , . ; . . . , . .

Answer 5

unit test , unit test . , , .

.

, . , . , Clean Code , . , , assertTrue(hw.heaterState()), assertEquals("HBchL", hw.getState()), , - . - , , .

, , ( 1 ). . , , , , . , , . , , .

/ , . , , ( ). .

Answer 6

:

, . unit test , . , , , , .

Answer 7

, , . , .

Answer 8

, . "" , .

, , "ba".

Answer 9

: unit test 100% . , , . 1%, 100%, , , .

70% -80%, , .

: , unit test, , . , . , . , .

, , 2 . --.