test: new formatting and screenshots addition #231
Conversation
Adding initial scope of Docusaurus project for testing docs
Updating dependencies
# What ❔ fix npm issues ## Why ❔ Conflict in react packages: To resolve build with latest deps first. ## Checklist - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated.
# What ❔ Removing extra symbols that prevents page from loading. After the test cases were imported from Allure project - some of the pages didn't load because of the different symbols. ## Why ❔ <!-- Why are these changes done? What goal do they contribute to? What are the principles behind them? --> <!-- Example: PR templates ensure PR reviewers, observers, and future iterators are in context about the evolution of repos. --> ## Checklist <!-- Check your PR fulfills the following items. --> <!-- For draft PRs check the boxes as you complete them. --> - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated.
# What ❔ - Removed obsolete Blogs and Tutorials docs - fixing folders structure for BE docs (docusaurus project) - cleaned index page ## Why ❔ ## Checklist - [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs). - [ ] Tests for the changes have been added / updated. - [ ] Documentation comments have been added / updated. --------- Co-authored-by: pcheremu <pavel.cheremushkin@gmail.com>
…om/matter-labs/block-explorer into QA-613-add-docusaurus-docs-project
olehbairak
changed the base branch from
main
to
QA-613-add-docusaurus-docs-project
This reverts commit 9c09efe.
…-789-docusaurus-add-screenshots-and-check-test-case-correctness2 Merge main
| @@ -0,0 +1,17 @@ | |||
| --- | |||
| tags: ['Full test', 'manual', 'Navigation', 'Network', 'regression', 'To Automate', 'ZKF-2507', 'Active'] | |||
There was a problem hiding this comment.
@olehbairak Do we decide to remove all ZKF-**** tags?
There was a problem hiding this comment.
Yes, fixed.
Thank you!
| @@ -0,0 +1,17 @@ | |||
| --- | |||
| tags: ['Full test', 'manual', 'Navigation', 'Network', 'Smoke test', 'ZKF-2507', 'Automated'] | |||
There was a problem hiding this comment.
Finally, can you please sort/select/take attention is the test case 'manual' or 'automated'? We have to keep only one of this tags.
There was a problem hiding this comment.
Yes, fixed.
Thank you!
|
|
||
| ## Scenario | ||
| - Prepare a custom token on L2 | ||
| - Make a request to show the balance | ||
| - ?module=account&action=tokenlist&address=\{hash\} | ||
| - You can see the token with its balance | ||
| - ; |
|
@olehbairak Please create a task to clean extra ZKF tags and check if test case contains only one (manual or automated tag). feel free to merge this PR to the initial and create another one based on linear task or make this fix in the same PR. @amelnytskyi fyi |
Yes, totally agree. We need to define whether these is the same, cause in fact they are partly automated, or to have only one identifier. |
Let's have only 'Active Partly Manual' for such cases - WDYT? |
|
Yep, Lets keep only one tag the will describe the status. And be careful with signing that we unexpectedly see here. |
pcheremu
changed the base branch from
QA-613-add-docusaurus-docs-project
to
main
pcheremu
changed the base branch from
main
to
QA-613-add-docusaurus-docs-project
What ❔
Why ❔
Checklist