mozilla
Increase the exhaustiveness of audience targeting in integration tests
We recently added integration tests using the SDK to validate jexl expressions. Now we can test each of the 'advanced' targeting options for each desktop and mobile client. However we should probably also test each of the built in audience fields as well, so we should add additional tests where we set each field on the audience page individually and validate the expression in the respective client.
┆Issue is synchronized with this Jira Task
➤ Benjamin Forehand Jr. commented:
Christopher Knowles did you get assigned to this by mistake?
➤ Christopher Knowles commented:
Yes, I’m not aware of ever visiting this - but history shows that I assigned myself. I’m assuming some bizarre mis-key event. Apologies for the noise.
➤ Benjamin Forehand Jr. commented:
Jared Kerim since you are removing graphQL should I wait on this?
➤ Jared Kerim commented:
Oh interesting point. We should be able to do this on desktop where it uses the UI now regardless of whether the API is GraphQL or REST. And yeah we can update the SDK integration tests to REST after it lands and do this for them then.
➤ Benjamin Forehand Jr. commented:
A bit held up with some other more urgent things but this is still on my TODO.
➤ Benjamin Forehand Jr. commented:
Going to turn this into an epic and divide the desktop and mobile work