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

fix(test): move integration test out from unit tests #603

Merged
merged 2 commits into from
Jun 21, 2023
Merged

Conversation

mvadari
Copy link
Collaborator

@mvadari mvadari commented Jun 20, 2023

High Level Overview of Change

There was an integration test that was in the unit test section. This PR moves that over.

Context of Change

The test was added in #520. I noticed that unit tests were suddenly taking much longer to run.

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • Tests (You added tests for code that already exists, or your new feature included in this PR)

Test Plan

CI passes.

@mvadari mvadari marked this pull request as ready for review June 20, 2023 21:19
@justinr1234
Copy link
Collaborator

@mvadari the diff seems weird?

@mvadari
Copy link
Collaborator Author

mvadari commented Jun 21, 2023

@mvadari the diff seems weird?

The diff is fine - I'm mainly moving the file from one folder to another, and moving a file doesn't have any diff. This is just a quick fix, so I didn't assimilate the tests into the existing ones (hence the TODO).

@mvadari mvadari merged commit 34325df into master Jun 21, 2023
12 checks passed
@mvadari mvadari deleted the move-integ-test branch June 21, 2023 13:46
@dangell7
Copy link
Contributor

@mvadari These test are written to specific networks to get a specific network id response. Therefore we cannot use the IntegrationTestCase and must use an active network. This also means we cannot use WALLET because we need a wallet active on that specific network.

So I would like your opinion on what we should do?

@pdp2121 If you can elaborate at all please share. I tried to implement IntegrationTestCase without success.

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.

None yet

4 participants