You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Salva (Jira)" <ji...@apache.org> on 2022/03/24 09:46:00 UTC

[jira] [Created] (FLINK-26845) Document testing guidelines

Salva created FLINK-26845:
-----------------------------

             Summary: Document testing guidelines
                 Key: FLINK-26845
                 URL: https://issues.apache.org/jira/browse/FLINK-26845
             Project: Flink
          Issue Type: Improvement
          Components: Stateful Functions
            Reporter: Salva


As of now, there seems to be not much guidance on how to approach testing. Although it's true [~sjwiesman] that 
{quote}Unlike other flink apis, the sdk doesn’t pull in the runtime so testing should really look like any other code. There isn’t much statefun specific.
{quote}
I think that at the very least testing should be mentioned as part of the docs, even if is only to stress the above fact. Indeed, as reported by [~trohrmann], there seems that there are already some test utilities in place but they are not well-documented, plus some potential ideas on how to improve on that front:
{quote}Testing tools is definitely one area where we want to improve  significantly. Also the documentation for how to do things needs to be updated. There are some testing utils that you can already use today: [https://github.com/apache/flink-statefun/blob/master/statefun-sdk-java/src/main/java/org/apache/flink/statefun/sdk/java/testing/TestContext.java…|https://t.co/WGjyMA510b]. However, it is not well documented.  
{quote}
Once the overall guidelines are in place we can extend the examples to include some tests (also in the playground repository).

{_}Note{_}: Issue originally reported in Twitter: https://twitter.com/salvalcantara/status/1505834101026267136?s=20&t=Go2IHP6iP4ZmIyVLmIeD3g



--
This message was sent by Atlassian Jira
(v8.20.1#820001)