The following tests:

https://github.com/unicode-org/message-format-wg/blob/main/test/test-functions.json#L93

  {
      "src": ".match {$foo :integer} 1.2 {{=1.2}} one {{one}} * {{other}}",
      "params": { "foo": 1.2 },
      "exp": "=1.2"
    },

and

https://github.com/unicode-org/message-format-wg/blob/main/test/test-functions.json#L98

  {
      "src": ".match {$foo :integer} 1.2 {{=1.2}} |1,2| {{=1,2}} * {{other}}",
      "locale": "fr",
      "params": { "foo": 1.2 },
      "exp": "=1.2"
    }

I read through the spec for number selection and there's a note saying that only integer exact matching is required for the tech preview. I'm not sure how to make this work in general, since the spec refers to "the JSON string representation of the numeric value of resolvedSelector" and numbers don't have unique JSON representations. I see that #675 has the goal of discussing this.

But for now, shouldn't these tests be omitted, since, as the spec says, "The exact behavior of exact literal match is only defined for non-zero-filled integer values"?