Skip to content
This repository has been archived by the owner on Jun 6, 2024. It is now read-only.

Improve test command coverage for demo flow #381

Closed
noaabarki opened this issue Jan 17, 2022 · 11 comments
Closed

Improve test command coverage for demo flow #381

noaabarki opened this issue Jan 17, 2022 · 11 comments
Labels
enhancement New feature or request good first issue Good for newcomers testing This issue or pull request is related to testing up for grabs Looking for a contributor to take this task

Comments

@noaabarki
Copy link
Contributor

Describe the solution you'd like
Add tests for demo flow in test command datree test ~/.datree/k8s-demo.yaml.

Requirements
Golang basic level.

“How to implement” Suggestion

In cmd/test/main_test.go, add new test case:: run test with demo-path without/with additional args → should print expected output.

@noaabarki noaabarki added enhancement New feature or request testing This issue or pull request is related to testing good first issue Good for newcomers up for grabs Looking for a contributor to take this task labels Jan 17, 2022
@Kanika637
Copy link

Hey, @noaabarki I m a beginner, can u please guide me to work on this issue

@noaabarki
Copy link
Contributor Author

Hi @Kanika637, that's awesome, and of course! Do you have any specific questions that I can help you with in order to get started? Also, feel free to use our community slack channel for raising any questions. Specifically, I highly recommend you to assist @Abhra303, since he understands our project and wonderful contributor 👑

@Kanika637
Copy link

Sure @noaabarki I will be doing that...

@Abhra303
Copy link
Contributor

Abhra303 commented Feb 8, 2022

@Kanika637 good to know you're working on this :)

Could you please wait for my PR (#410 ) to get merged? Because, the fixes for these issues ( #382, #383 and this issue itself) are related mainly to main_test.go file. So, if you make a PR before my PR is merged, it can create conflict problems for the reviewers.

Let's see what @noaabarki says on this.

@Kanika637
Copy link

Sure @Abhra303 I will wait for your PR to get merged first.

@Kanika637
Copy link

I have made the changes in my local system...@Abhra303 did your PR get merged?

@Abhra303
Copy link
Contributor

Hi @Kanika637, no my PR is still waiting for review ( it may take two or three days to review it).

But if you think you did all the required changes - feel free to make a PR. One of us (you and me) will do a force update on our branches if another's PR get merged :)

@Kanika637
Copy link

Yeah, I think this can create some conflicts...So I will wait for your PR

@Kanika637
Copy link

@noaabarki what would you say on this?

@noaabarki
Copy link
Contributor Author

Hey @Kanika637, continue our conversation in the Slack channel, I wouldn't wait, I believe the update will go smooth. To speed up the process, I'll try my best to review @Abhra303 PR today.

@Kanika637
Copy link

I have made the PR for issue #381...Thank you soo much @noaabarki @Abhra303 @royhadad for being such supportive.

@noaabarki noaabarki added the WIP Working in progress (will be deployed soon) label Feb 24, 2022
@adifayer adifayer removed the WIP Working in progress (will be deployed soon) label Apr 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request good first issue Good for newcomers testing This issue or pull request is related to testing up for grabs Looking for a contributor to take this task
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants