ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Component/s: Cross Spec Consistency
    • None

      Summary

      What is the problem or use case, what are we trying to achieve?
      Ensure all specification tests are compliant with the specification standards defined in CONTRIBUTING.md

      Motivation

      Who is the affected end user?

      Who are the stakeholders?

      Specification maintainers.

      How does this affect the end user?

      Are they blocked? Are they annoyed? Are they confused?

      Annoyance and confusion.

      How likely is it that this problem or use case will occur?

      Main path? Edge case?

      Multiple specifications (bson-corpus, load-balancers).

      If the problem does occur, what are the consequences and how severe are they?

      Minor annoyance at a log message? Performance concern? Outage/unavailability? Failover can't complete?

      Specification inconsistency.

      Is this issue urgent?

      Does this ticket have a required timeline? What is it?

      No.

      Is this ticket required by a downstream team?

      Needed by e.g. Atlas, Shell, Compass?

      No.

      Is this ticket only for tests?

      Does this ticket have any functional impact, or is it just test improvements?

      Neither.

      Acceptance Criteria

      What specific requirements must be met to consider the design phase complete?

      All specification tests comply with the specification standards.

            Assignee:
            Unassigned
            Reporter:
            Noah Stapp
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: