Page MenuHomePhabricator

UsageTracking: create integration test for usage tracking updates
Closed, ResolvedPublic1 Estimated Story Points


The integration test should save a page using different entities in different ways, and the verify that the respective usages are accessible via the UsageLookup service.

The integration test should further verify that entity usages included via a template are tracked, and are updated when the template is changed (once T99510 is implemented).

Once T99512 is implemented, the integration test should also verify that label usage is tracked for all languages the page has been rendered (and cached) in.

Finally, the integration test should check whether usage trackign info is correctly removed when a page is deleted.

Event Timeline

daniel claimed this task.
daniel raised the priority of this task from to High.
daniel updated the task description. (Show Details)
daniel set Security to None.
daniel added subscribers: daniel, Aklapper, Rical and 5 others.

Change 212293 had a related patch set uploaded (by Daniel Kinzler):
Integration test for usage tracking.

When we move a task in a Sprint workboard, the email put it in [Changed Project Column] which seems not enough descriptive. Perhaps [scheduling] could be better ?

Change 212293 merged by jenkins-bot:
Integration test for usage tracking.