getUser(userId, function(error, user) {
    if (error) {
      callback(error);
      return;
    }
    callback(null, user.name)
  })
}```

"Random tests are quite predictable" or "Random tests are not really random"

Either of those?

Random tests aren't random enough. - That is the worst insult towards random tests I've ever heard on this platform :D

random success test 1: should load generated orders for userId 603
userId 603: expected callback(null, orders): expected [ null, 'text' ] to deeply equal [ null, [ { id: 60300, …(2) }, …(3) ] ]
Completed in 79ms

Missing chai.config.truncateThreshold = 0 ( or another reasonable value )

Random tests aren't random enough.

There should randomly be testing for missing user, missing orders, empty orders, or good orders.

function processLatestOrder(userId) {
  getUser(userId).then(user => null)
  return new Promise(() => 0)
}

This should not pass the test suite

See comments in my solution:

• needs tests with getOrders().id is falsy but not undefined

my code would bug out on id = 0.

• needs tests with getOrderDetails() returns error
• needs tests with sendEmail() returns error

other calls have to handle destructuring a missing parameter; these don't.

• getUser()'s result is not used

OK, we call it in case it returns error, but it still seems useless. isn't there something useful it could do?

chargePayment(orderId, callback) takes its orderId from getOrderDetails, not getOrders.

This is inadequately specified. The example doesn't help.

Example and Submit tests are missing chai.config.truncateThreshold = 0, leading to failure messages such as userId 154: expected full workflow helper chain: expected [ 'details:3666', …(3) ] to deeply equal [ 'details:3666', …(3) ].

This issue probably applies to the whole series.

The failure message should probably also state these are the arguments the callback was called with, but I don't know, because the message isn't telling me. The list might also be composed of other things.

Truncated actual and expected values often are the same, the tests should use chai.config.truncateThreshold = 0

Fixed

https://www.codewars.com/kata/reviews/6a2c53c40a539b58bb305d03/groups/6a2d962db368c8f84da5d9c2

(Node 12)

There's something to be said for specifying and strictly testing that contract. The error message could be better though. You're testing the number of arguments of the callback. I'd suggest to explicitly show exactly that.

Got the concern. Let me few time, I'll improve it.
I'll let know when finish it