Skip to content

New test to port (done with test_chaining_distance_piscine_caen.py but maybe too complex) #38

Closed

Description

@LionelZoubritzky-IGN

On geocontext, PR ignfab/geocontext#207 added a new behavior and e2e test:

testName: "should find that Sivom swimming pool in Mondeville is the nearest pool to the LUX cinema in Caen, and that the walking distance is 29 minutes",
userInput: "Quel est le temps de marche exact entre le cinéma LUX, situé au sud-est de Caen, et la piscine la plus proche ?",
toolMode: "mcp",
requiredToolCalls: ["geocode", "gpf_search_types", "gpf_describe_type", "gpf_get_features", "distance"],
expectedResponseFragments: ["Sivom", "Mondeville"],
assertScenarioResult: ({ normalizedFinalMessage }) => {
  expect(containsNumberInRange(normalizedFinalMessage, 25, 35)).toBe(true);
},

Can it be ported in geocontext-test?

Activity

  1. mborne commented on Oct 5, 2026

    @mborne
    Contributor

    Proposal: close this issue in favour of the new, more focused issues on 0.10.x test coverage:

    Any objection?

  2. mborne commented on Oct 5, 2026

    @mborne
    Contributor

    The scenario is ported in #47 (test_chaining_distance_piscine_caen.py), but it is too complex for the goal of these tests: checking that the tools work properly with different models, not testing the models' reasoning capabilities.

    To pass it, the model has to resolve an ambiguous place ("cinéma LUX", where geocode returns a tram station), discover the right WFS table, search for the nearest pool, then call distance. A failure therefore says more about the model's reasoning than about the tools. For example, claude-haiku-4-5 fails because it takes the first pool returned by geocode (Campus 1, 52 min), while claude-sonnet-4-6 passes (Sivom, Mondeville, 29.5 min).

    The simpler geocode → distance test (test_chaining_geocode_distance.py) fits the purpose of this repository better.

  3. changed the title [-]New test to port[/-] [+]New test to port (done with test_chaining_distance_piscine_caen.py but maybe too complex)[/+] on Oct 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions