You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Use the Flow emulator to run the tests, or
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: