…eb#1619)

This PR simplifies the names of the existing tests with descriptions.

Issue: gpuweb#1618

…lear_value (gpuweb#1640)

If depthLoadOp of depthStencilAttachment is "clear", depthClearValue
must be between 0.0 and 1.0. So, this PR adds a test to check if
depthClearValue is invalid if the value is out of the range.

Issue: gpuweb#1618

…b#1630)

No two entries in timestampWrites have the same location. So,
this PR adds a test to ensure that two timestampWrite don't
have the same location.

Issue: gpuweb#1618

…eb#1639)

This is the second PR to simplify the names of the existing tests
with descriptions.

Issue: gpuweb#1618

…eb#1651)

This is the last PR to simplify the names of the existing tests
with descriptions.

Issue: gpuweb#1618

…#1652)

If occlusionQuerySet is not null, the type should be occlusion.
So, this PR adds a test to check if the type is invalid if the
type is not occlusion.

Issue: gpuweb#1618

…eb#1654)

The count of the querySet should be greater than the queryIndex
of timestampWrite. So, this PR adds a test to check if a validation
error is generated when the query index is greater than the count of
the query set.

Issue: gpuweb#1618

…puweb#1653)

The queryType of each timestampWrite in timestampWrites should be
`timestamp`. So, this PR adds a test to check if a validation error
is generated if all query set types aren't `timestamp`.

Issue: gpuweb#1618

…puweb#1656)

Each timestampWrite of the timestampWrites should not have the same
queiryIndex if each timestampWrite has the same querySet. So, this
PR adds a test to check if a validation error is generated when
queryIndexes are equal in the timestampWrites.

Issue: gpuweb#1618

…ogether (gpuweb#1660)

The `resolveTarget,usage` test has only tested an invalid case
(COPY_SRC | COPY_DST). So this PR adds more cases to check if
the resolveTarget usage is valid.

Issue: gpuweb#1618

…ar_value (gpuweb#1674)

This PR updates render_pass_descriptor:depth_stencil_attachment_depth_clear_value
to check if out of range of depthClearValue is only invalid when depthLoadOp is
`clear'. If depthLoadOp is not `clear`, depthClearValue should be valid even
though the value is out of range.

Issue: gpuweb#1618