• Type: Icon: Epic Epic
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 1.6.0alpha1, 1.6.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Done
    • PHPC test suite
    • Hide

      2018-07-31 : Initial target 2018-08-21 (3weeks)

      2018-08-14 : Updated target 2018-08-28 (4weeks)
      Ran into issues with X509 error messages so adding additional week to target date.

      2018-08-28 : Updated target 2018-09-07 (5weeks)
      Adding a week as code reviews are blocked and waiting for team member to return from vacation.

      Show
      2018-07-31 : Initial target 2018-08-21 (3weeks) 2018-08-14 : Updated target 2018-08-28 (4weeks) Ran into issues with X509 error messages so adding additional week to target date. 2018-08-28 : Updated target 2018-09-07 (5weeks) Adding a week as code reviews are blocked and waiting for team member to return from vacation.

      The current PHPC test suite depends on a number of standalone and replica set topologies deployed by mongo-orchestration running within a Vagrant box. There are a few issues with this:

      • Each test, if it communicates with a server at all, uses only a single URI. This means that a generic query test likely only runs against the STANDALONE environment (latest MongoDB version) instead of multiple topologies.
      • We have several tests that are quite fragile. Some depend on a second VM, which hosts an LDAP server. Others are cluster tests that attempt to create their own replica sets on the same mongo-orchestration instance to test failovers and the like.
      • Outside of the cluster tests, we have no shard cluster test coverage.

      Ideally, the PHPC test suite should function more like PHPLIB (and libmongoc), in that each test attempts to run on some generic URI environment variable. Tests can then decide if the topology is suitable and skip if not.

            Assignee:
            derick Derick Rethans
            Reporter:
            jmikola@mongodb.com Jeremy Mikola
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              5 weeks, 3 days