-
-
Notifications
You must be signed in to change notification settings - Fork 41
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 Test Cases for UploadToCloudStorage
#53
Comments
Hey @Shofiya2003 |
Sure |
Thanksss, Assigning it to you right away!! |
@uzaxirr @abhi-shek-raj apologies for the delay |
Not a problem at all! |
I am using the documentation of every cloud service provider to mock the service in the unit test. |
I started with aws and am using mock client and created logs for the process to test the service. |
Yes, in this way it will be better to segregate the services and have individual customisation for each if or whenever required
Checkout this comment, see if you can do something similar.
I didn't got this one, can you mention the function name please. |
hey! @uzaxirr |
The |
@uzaxirr @abhishekraj272 can we divide this into three issues each for the three cloud storage platform. I completed implementing the tests for aws upload. |
Yes works, just create the tickets, give some description and assign those
on which you are working
…On Mon, 6 Feb 2023 at 1:08 AM, Shofiya ***@***.***> wrote:
@uzaxirr <https://github.com/uzaxirr> @abhishekraj272
<https://github.com/abhishekraj272> can we divide this into three issues
each for the three cloud storage platform. I completed implementing the
tests for aws upload.
—
Reply to this email directly, view it on GitHub
<#53 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGO7IBQXPHFCS76JXOQ6NSLWV76SNANCNFSM6AAAAAATRTV6ZU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Add Test cases for the function
UploadToCloudStorage
and all possible functions inutils/upload.go
The cloud provider services needs to be mocked over here (Eg: AWS, GCP and Azure)
The text was updated successfully, but these errors were encountered: