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

Test "Build & Deploy" in Web IDE #239

Open
40 tasks
xpyctumo opened this issue Feb 4, 2025 · 0 comments
Open
40 tasks

Test "Build & Deploy" in Web IDE #239

xpyctumo opened this issue Feb 4, 2025 · 0 comments

Comments

@xpyctumo
Copy link

xpyctumo commented Feb 4, 2025

Also to verify that the user can build his project and deploy it is necessary to check the following

  • User can select Environment
    • Sandbox
      • User will immediately have a contract address
    • Testnet
      • User will be prompted to connect a wallet in the Testnet network (TON Connect will be shown)
      • After connecting the wallet (e.g. via Tonkeeper) the addresses must be identical (Web IDE will show bounced of connected wallet address)
      • The "Disconnect Wallet" button appears
        • Wallet can be disconnected from Web IDE
    • Mainnet
      • User will be prompted to connect a wallet in the Testnet network (TON Connect will be shown)
      • After connecting the wallet (e.g. via Tonkeeper) the addresses must be identical (Web IDE will show bounced of connected wallet address)
      • The "Disconnect Wallet" button appears
        • Wallet can be disconnected from Web IDE
  • User must select in dropdown the contract file to deposit
    • Only .tact files supported (?)
    • If the files are missing, there should be a label "Required files not found"
    • After building the file, the user can select which contract to deploy
      • The list of contracts must be identical to the contract names from the builded file
    • Deploy must working
      • In the sandbox, this should happen almost instantly, without confirming in any wallets and using TON Connect
      • In Mainnet/Testnet env user should confirm his action in connected wallet via TON Connect
        • There should be a corresponding error in the log when the user cancels the confirmation
        • After confirmation, the contract should be deployed in the selected user environment
          • There should be a message in the log with contract address about success deploy
      • After the deployment the corresponding getters, receivers should appear according to the contract code
        • The “View Deployed Contract” button should appear
      • User can call any getter contract in the selected environment
        • Calling getter in the environment of which contract is not deployed should be error (?)
          • Buttons (getters/receivers) should't be available
      • Any receiver in Testnet/Mainnet env must be called using TON Connect
      • Calling any receiver in the Sandbox env should work immediately
      • Receiver with name “empty” must be present if there is an empty receive in the contract code
      • If the receiver in the contract code has arguments, they must also be in the form
        • Arguments must be locally validated in the Web IDE form before being sent
        • Cannot use characters in the uint* field type
      • If user change the contract code: add new receiver, getter and redeploy, the form should display the new changes
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

No branches or pull requests

1 participant