Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add guidance on how to approach the framework for a new pipeline #36

Closed
Tracked by #37
ydaponte opened this issue Dec 11, 2023 · 2 comments
Closed
Tracked by #37

Add guidance on how to approach the framework for a new pipeline #36

ydaponte opened this issue Dec 11, 2023 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@ydaponte
Copy link
Collaborator

Goal: improve the guidance, by adding a step-by-step on the things that need to be considered when starting to test a new pipeline.

Success criteria:

  • Add guidance (might include visuals) on how to approach the framework for new pipelines (that are not in the examples)
  • Add more examples to include often used tasks like the Copy activity for example
@ydaponte
Copy link
Collaborator Author

@sreedhar-guda - one of the aspects of this item was the order of the activities in the pipelines vs the order in which the tests were written. Can you clarify if you find the answer to that on our next meeting or offline in the chat?

@ydaponte ydaponte mentioned this issue Dec 14, 2023
@ydaponte ydaponte added the documentation Improvements or additions to documentation label Dec 14, 2023
@arjendev arjendev self-assigned this Feb 7, 2024
@arjendev
Copy link
Collaborator

Fixed in #72

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Development

No branches or pull requests

2 participants