Temporal "branding" tests are imprecise

[jugglinmike]

Many of the tests intended to verify the "this value" (a.k.a "receiver") of the proposal's methods invoke those methods without providing the required arguments. In some cases, this omission would cause the expected TypeError when the implementation incorrectly tolerated an invalid receiver.

The test for Temporal.Duration.prototype.total currently demonstrates this hazard:

const total = Temporal.Duration.prototype.total;

assert.sameValue(typeof total, "function");

assert.throws(TypeError, () => total.call(undefined), "undefined");

If an implementation incorrectly accepted "undefined" as a receiver, it could still spuriously pass this test by throwing a TypeError for the omission of the required "options" argument (that is, by correctly implementing the subsequent step in the algorithm).

These tests should be modified to provide valid values where they are required. Although not all cases of argument omission is susceptible to this problem, the pattern is consistently misleading for human readers, so it should be addressed in all cases.