Pipeline Testing Introduced #819
yoonspark
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The user may want to check if the generated pipeline files are valid and reliable before actually using them. As a first step to support this (more work in progress/planning), we implemented generation of simple scaffold/template that the user can customize to suit their unique testing needs. The feature is yet to be included in our next release, but you can give it a quick try now if you want:
Overview
Consider the following development code:
Now, if we run
we would get a pipeline module file looking as follows:
As shown, the module file includes a transformed version of the original development code where
print()
statements in this example) have been removedget_url1_for_artifact_iris_model_and_downstream()
in this example)With such changes, the user may want to ensure that the transformed code is valid and reliable before actually using it. To support this, the new feature generates simple testing scaffold/template looking as follows:
As shown, the scaffold contains placeholders for testing each function in the module file, which are meant to be fleshed out by the user to suit their needs. Though very simple, this bare-bones templating still delivers value to the user as it provides a concrete structure for thinking about pipeline testing; and the user can quickly focus on the testing logic itself.
References
Beta Was this translation helpful? Give feedback.
All reactions