Skip to content
This repository has been archived by the owner on Apr 6, 2023. It is now read-only.

Refresh Kinto Suggestion Data On Demand In Merino Contract Tests #391

Open
data-sync-user opened this issue Jun 17, 2022 · 2 comments
Open

Comments

@data-sync-user
Copy link
Collaborator

data-sync-user commented Jun 17, 2022

The current contract test design supports, loading suggestion data during initialization. In production, suggestion data is updated at a configured interval. Add functionality to the contract test framework to simulate the refresh of suggestion data.

┆Issue is synchronized with this Jira Task
┆epic: Develop contract tests for suggestion data changes in RS

@data-sync-user
Copy link
Collaborator Author

➤ Nan Jiang commented:

Katrina Anderson Thanks for recording this!

To add a bit more color, I think this functionality is still relevant for us as Remote Settings will continue serving as the main suggestion provider for Merino for the foreseeable future, and we have a few use cases in which Merino is expected to reload suggestions or other data from RS on demand. Having some contract tests to cover those scenarios would be great.

@data-sync-user
Copy link
Collaborator Author

➤ Taddes Korris commented:

Hello Katrina Anderson and Nan Jiang ! Kat brought this to my attention, as a part of https://mozilla-hub.atlassian.net/browse/CONSVC-1641 ( https://mozilla-hub.atlassian.net/browse/CONSVC-1641|smart-link ) , I have been investigating this very problem. Much of the contract test ticket for suggestion data there is based on the ability to do this very thing, which is tricky! I think it’ll be good to brainstorm some possible solutions, as I had some ideas, like loading in additional JSON files into Kinto that could be used to represent updated data. Anyway, let’s connect sometime next week and discuss some possible options and how we want to set up the work flow.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant