Shouldn't you have the actual types written down in this test? See, for example, the tests in AboutBinding or AboutTuples.

Remove the excess brackets. You don't need them. Remember, a tuple is created by the , operator, not by brackets. Brackets only need to be used for grouping. A similar thing holds true for tuple patterns: see the syntax of these in your notes.

Why are you opening System.Threading.Tasks at the top?

You can avoid a warning about incomplete pattern matches by not using a constant pattern in your answer.

You don't need to match the Author field at all in the pattern. Remember, fields that are left out are implicitly wildcarded.

There's no need for brackets in the tuple patterns.

The tests originally look like sprintf __ "perfect" and sprintf __ 9. You're supposed to replace the __ with a single item, rather than replacing it with two items (e.g. "%s %s" "Practice makes" in one of the cases).

For the ``without surrounding space``, there's a C# method to do that instead of using .Substring. Also, as a matter of style, remove the brackets in the calls wherever you can.

Why are you opening System.Reflection?

By doing an open MushroomKingdom at the top, you've missed out on what module 22 was trying to teach you. Remove that line and see if you can get the tests to pass?

You don't need brackets here. The only reason that they're used in the next lines is because functions bind tightly — and without the brackets, should equal (4, 5, 5) would get interpreted as ((should) (equal) 4)), 5, 5

Remove extraneous brackets; you don't need them. You can say Some a, for example, without brackets.