Uploaded image for project: 'Node.js Driver'
  1. Node.js Driver
  2. NODE-5377

Spike: Identify blockers in getting mocha tests to run on Deno

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Unknown Unknown
    • None
    • Affects Version/s: None
    • Component/s: Deno

      Use Case

      As a... Javascript or Typescript Developer using Deno
      I want... Some degree of confidence that the MongoDB Node Driver works from my selected runtime
      So that... I can successfully interact with MongoDB from Deno via the Node.js Driver

      User Impact

      *What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

      Dependencies

      • upstream and/or downstream requirements and timelines to bear in mind

      Unknowns

      • Can the current mocha test suite be run in Deno with node compatibility enabled?

      Acceptance Criteria

      Implementation Requirements

      • Document gaps in getting test suite to run on Deno
        • Document behaviours that Deno has that the driver can't support and vice versa
        • Document driver test coverage if running inside Deno and identify blockers for the missing test coverage

      Testing Requirements

      • unit test, spec test sync, etc

      Documentation Requirements

      • DOCSP ticket, API docs, etc

      Follow Up Requirements

      • additional tickets to file, required releases, etc

            Assignee:
            neal.beeken@mongodb.com Neal Beeken
            Reporter:
            jessica.sigafoos@mongodb.com Jessica Sigafoos
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: