Use Git submodules for spec tests

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Done
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Go Drivers
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Context

      Currently there are copies of the JSON and YAML files for every spec test that the Go Driver runs. That means that PRs frequently include thousands of lines of spec test files, which make reviewing PRs difficult. Additionally, it's easy to lose track of what revision of each spec the Go Driver tests against.

      Instead, we should use Git submodules for each spec test directory. We previously stopped doing that because Evergreen didn't support cloning Git submodules (see GODRIVER-106), but it now supports a recurse_submodules option for the git.get_project command.

      Definition of done

      Pitfalls

      • We don't keep track of what revision we sync each spec test dir at, so updating the submodules may require a bunch of Git or code archaeology to figure it out.

            Assignee:
            Preston Vasquez
            Reporter:
            Matt Dale
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 2 weeks
                2w
                Logged:
                Time Spent - Not Specified
                Not Specified