[
https://issues.apache.org/jira/browse/FLINK-7554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-7554:
----------------------------------
Labels: auto-unassigned pull-request-available stale-major starter (was:
auto-unassigned pull-request-available starter)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Add a testing RuntimeContext to test utilities
> ----------------------------------------------
>
> Key: FLINK-7554
> URL: https://issues.apache.org/jira/browse/FLINK-7554
> Project: Flink
> Issue Type: New Feature
> Components: API / DataStream, Tests
> Reporter: Timo Walther
> Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-major,
> starter
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When unit testing user-defined functions it would be useful to have an
> official testing {{RuntimeContext}} that uses Java collections for storing
> state, metrics, etc.
> After executing the business logic, the user could then verify how the state
> of the UDF changed or which metrics have been collected.
> This issue includes documentation for the "Testing" section.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
