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

[FEATURE] Flow Emulator Test Environment #287

Open
tombeckenham opened this issue Dec 13, 2024 · 0 comments
Open

[FEATURE] Flow Emulator Test Environment #287

tombeckenham opened this issue Dec 13, 2024 · 0 comments
Assignees

Comments

@tombeckenham
Copy link
Collaborator

Issue to be solved

Currently we are performing testing manually on testnet and mainnet. As we start to introduce automated testing, we need a way of creating and using accounts (wallets) that have specific conditions such as specific balances, coins, or nfts. We then need to be able to move and send nfts and tokens repeatedly and expect the same result.

Whatever solution we come up with has to work both with unit tests (using vitest) and with e2e testing (using playwright). Unit tests are run automatically using vitest as part of the ci process.

We have just setup e2e testing using playwright, but the branch / PR is yet to be merged (as of when this issue has been created).

Suggest A Solution

There are several ways we can approach a solution.

I'd suggest one of these solutions:

  1. Use the Flow emulator to run the tests, or
  2. Create a set of mock data that can be loaded used by tests. You may be able to use flow emulator to generate this data

Please work with @Peppermint1020 to come up with the data sets and conditions.

It would be ideal if we can avoid having to create a separate test build but it may be unavoidable. If so, this build should be created in parallel on ci to the main build.

The solution should work on CI, AND locally so that engineers can run tests in watch mode locally.

@tombeckenham tombeckenham self-assigned this Dec 13, 2024
@tombeckenham tombeckenham moved this to Todo in Flow Wallet Dec 13, 2024
@tombeckenham tombeckenham moved this from Todo to In Progress in Flow Wallet Dec 23, 2024
tombeckenham added a commit that referenced this issue Dec 23, 2024
@tombeckenham tombeckenham linked a pull request Dec 23, 2024 that will close this issue
5 tasks
This was referenced Dec 23, 2024
tombeckenham added a commit that referenced this issue Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

1 participant