There's currently a /test/event schema in primary repository for simple testing of "production" events, but not for testing "analytics" events.
Specifically, it's missing client_dt field (from /fragments/analytics/common schema fragment in secondary repo) that Event Platform Clients (e.g. EventLogging on MediaWiki) include in events. In case of Event Platform Client for iOS in the Wikipedia app, that also attaches a device_id and a session_id to all events, which are fields that are being added (along with a pageview_id field) in the /fragments/analytics/identifiers schema fragment, currently in code review)
This came up in a conversation between @mpopov and @Tsevener about adding calls to test event logging using the new client library in the Wikipedia app for iOS. Those events would be sent, sure, but they wouldn't be valid against the existing test schema.
So, we need a /analytics/test schema in the secondary repo that will ref /fragments/analytics/common and /fragments/analytics/identifiers and – just like the /test/event schema in primary repo – it would just have these fields:
test: type: string default: default value test_map: description: > We want to support 'map' types using additionalProperties to specify the value types. (Keys are always strings.) type: object additionalProperties: type: string
We would also need to deploy a stream that uses that schema – "analytics.test" or "test.analytics"?