Cover testnet scenarios that need external services
codingone21 opened this issue · comments
Cypress testnet coverage is kept minimal at the moment due to the complexity involved with external services.
Cypress testnet tests - https://github.com/onflow/kitty-items/blob/master/cypress/e2e/testnet.cy.js
Some of these external services we have to interact with include
- Faucet (account funding is required for purchasing, which then allows listing, selling, etc.)
- Blocto (forces a popup instead of iframes, which makes it very difficult for cypress to test)
There are other discussions related to this topic like
- Should we create a singular test account to be shared internally in the team? If we keep this account fully funded all the time, we won't need to worry about the Faucet.
- How do we manage/control the testing account?