How to test: - Enable the feature flag: tuleap config-set feature_flag_cross_tracker_search_duck_typed_fields 1 - Set up two or three trackers with int or float fields. The fields must have the same shortname, for example "initial_effort". - No functional change for duck-typed numeric fields. Why? We will write other test files for other types of duck-typed fields. Instantiation of the Factory object takes 300 lines, and does not vary. It makes sense to have it in a dedicated file. Since the data for each comparison was very similar, we can do it once in the setUp() and then have each test run its own query and make its own assertions. It should be a bit more readable. part of story #10710 search on fields with duck typing Change-Id: Iebd6ae4a35ee9145ce8b89f255ea138d09cd0bc0

+474 −465

Author

Joris MASSON (jmasson) 2024-01-29 16:58

Committer

Joris MASSON (jmasson) 2024-01-30 11:29

Hash df9157afcc79e7314e15928bba9228ecb12f7a4e

Parent c8367db36e2c27d9264e024d7f79e9debb0b01bf

Reference git #tuleap/stable/df9157afcc79e7314e15928bba9228ecb12f7a4e