Unified CRUD tests should use isClientError where appropriate

XMLWordPrintableJSON

    • Type: Spec Change
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Component/s: CRUD
    • None
    • Needed

      Summary

      The ported v2 CRUD tests do not make use of isClientError, since there was no equivalent in the legacy format (tests typically relied on APM to assert that no commands were issued). That will likely be the case when v1 tests are ported as well.

      Once all of the CRUD tests are ported, we should replace isError with isClientError where appropriate.

      Motivation

      Who is the affected end user?

      Internal to drivers.

      Is this issue urgent?

      No.

      Is this ticket required by a downstream team?

      No.

      Is this ticket only for tests?

      Yes.

            Assignee:
            Unassigned
            Reporter:
            Jeremy Mikola (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: