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

Substrate Swift Api milestone 2 #926

Merged
merged 1 commit into from
Jul 26, 2023
Merged

Conversation

dileping
Copy link
Contributor

Milestone Delivery Checklist

  • The milestone-delivery-template.md has been copied and updated.
  • The invoice form 📝 has been filled out for this milestone.
  • This pull request is being made by the same account as the accepted application.
  • I have disclosed any and all sources of reused code in the submitted repositories and have done my due diligence to meet its license requirements.
  • In case of acceptance, the payment will be transferred to the BTC/ETH/fiat account provided in the application.
  • The delivery is according to the Guidelines for Milestone Deliverables.

Link to the application pull request: w3f/General-Grants-Program#333

@dastansam
Copy link
Contributor

hey @dileping,

here's the external evaluation of your milestone delivery. It looks good in general, with the except of few failing integration tests. Let me know if there is bug in tests or if I am not running them correctly.

@ypopovych
Copy link
Contributor

hey @dileping,

here's the external evaluation of your milestone delivery. It looks good in general, with the except of few failing integration tests. Let me know if there is bug in tests or if I am not running them correctly.

Integration tests need an environment variable TEST_MNEMONIC set with a 12-word mnemonic(one from the test application can be used). Inside our repo, it's set in the GitHub Action as a secret. We will move tests to the local test node for milestone 3, but for now, they are running on the Westend test net.

The simplest way is to run tests from console as TEST_MNEMONIC="<mnemonic-from-testapp>" swift test

@dastansam
Copy link
Contributor

hey @dileping,
here's the external evaluation of your milestone delivery. It looks good in general, with the except of few failing integration tests. Let me know if there is bug in tests or if I am not running them correctly.

Integration tests need an environment variable TEST_MNEMONIC set with a 12-word mnemonic(one from the test application can be used). Inside our repo, it's set in the GitHub Action as a secret. We will move tests to the local test node for milestone 3, but for now, they are running on the Westend test net.

The simplest way is to run tests from console as TEST_MNEMONIC="<mnemonic-from-testapp>" swift test

thank you for swift response! Indeed, integration tests are passing now with a mnemonic from the test app. I think it would be nice if it was documented in the testing guide or in the README. In any case, all issues are addressed and this delivery lgtm

@ypopovych
Copy link
Contributor

hey @dileping,
here's the external evaluation of your milestone delivery. It looks good in general, with the except of few failing integration tests. Let me know if there is bug in tests or if I am not running them correctly.

Integration tests need an environment variable TEST_MNEMONIC set with a 12-word mnemonic(one from the test application can be used). Inside our repo, it's set in the GitHub Action as a secret. We will move tests to the local test node for milestone 3, but for now, they are running on the Westend test net.
The simplest way is to run tests from console as TEST_MNEMONIC="<mnemonic-from-testapp>" swift test

thank you for swift response! Indeed, integration tests are passing now with a mnemonic from the test app. I think it would be nice if it was documented in the testing guide or in the README. In any case, all issues are addressed and this delivery lgtm

Yeah. My bad. I was too focused on the test app and forgot to add instructions on how to run integration tests from the repo

@keeganquigley keeganquigley self-assigned this Jul 24, 2023
@keeganquigley
Copy link
Contributor

Hi @dileping thanks for the delivery. The external evaluation has been accepted. Before I merge the milestone, can you update this line of your license file to replace the boilerplate brackets with your copyright owner information date, in order to apply the license? Thanks!

@dileping
Copy link
Contributor Author

dileping commented Jul 26, 2023

Hi @dileping thanks for the delivery. The external evaluation has been accepted. Before I merge the milestone, can you update this line of your license file to replace the boilerplate brackets with your copyright owner information date, in order to apply the license? Thanks!

Hi @keeganquigley, thanks for accepting the milestone! It was a long one :)

Just added a NOTICE file like we did on our other repositories. I think this way it should be even better.

@keeganquigley
Copy link
Contributor

Thanks @dileping happy to accept the milestone. Yes so glad to see it completed!

@keeganquigley keeganquigley merged commit 3869c57 into w3f:master Jul 26, 2023
4 of 6 checks passed
@ypopovych ypopovych deleted the swift_api branch September 16, 2023 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants