-
Notifications
You must be signed in to change notification settings - Fork 8
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
Automating the new playground and dashboard tests #1285
Comments
we have to discuss if we will use the portal or the tf-extension it will be the starting part of every test. |
playground tests should include deployments and checking contracts and if the solutions are working correctly. |
dashboard tests should include portal part,explorer and calculator (both simulator and pricing calc.) |
work in progress (WIP) |
Is this still blocked? |
Not Blocked |
what is the status here? |
will move it to 3.14 |
no update? |
I updated the Homepage, Profile Manager, Twin, Transfer, and Bridge test pages with new UI changes, closed the old PR #2552, and created a new PR #2552 as all the tests were deleted when the dashboard and weblets directories were removed. The PR is drifted as the new directory has not been confirmed yet, but the tests for the pages mentioned above are ready for review. |
Lets merge this asap. |
I have updated PR #2552 with new changes as requested: #2552 (comment). And I'm working on the other three pages and will create a separate PR for them. The estimated time is 2 days after finishing the current test run 2.4.0 on testnet. |
Done fixed, approved, and merged. I fixed all the portal page tests in the new UI and added new cases for new features. When the workflow runs the tests, it will keep failing in some tests: All the farm tests will fail until these issues are fixed.
Other than that, this issue could be closed. |
Description
Designing automated tests for:
Using the designed test cases in testlodge for the playground test suite and the dashboard test suite
The text was updated successfully, but these errors were encountered: