Added Manual testing classic tutorial and screenshots to it#655
Added Manual testing classic tutorial and screenshots to it#655catpetrychenko-rgb wants to merge 2 commits into
Conversation
Co-authored-by: Copilot <copilot@github.com>
Deploying docs with
|
| Latest commit: |
3e617c9
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://8bd8f50c.docs-c7r.pages.dev |
| Branch Preview URL: | https://issue-372.docs-c7r.pages.dev |
| { label: 'Playwright', link: '/tutorials/playwright'}, | ||
| { label: 'Java Integration', link: '/tutorials/java'}, | ||
| { label: 'WebdriverIO', link: '/tutorials/webdriver'}, | ||
| { label: 'Manual Testing Classic', link: '/tutorials/manual-testing-classic'}, |
There was a problem hiding this comment.
move this section above the Playwright
There was a problem hiding this comment.
agreed. i will put it above, and others (bdd, jira, etc) too
|
|
||
| What you will do: | ||
|
|
||
| 1. Create a Classical project. |
There was a problem hiding this comment.
Since we'll have a separate "Manual Testing – BDD" section coming up, add a short note, explaining the difference between Classic and BDD, so users understand why this tutorial covers Classic?
That way readers can immediately tell if this is the right tutorial for them, or switch to the BDD version.
There was a problem hiding this comment.
This particular tutorial is focused only on classic testing. bbd tutorial is in bbd tutorial. they are cross-linked
moreover, it is separately described in the getting started pagege. also it is described in the manual bdd, also it is described in the tutorial bdd.
the article should not mess the user. user should follow only one way. Classic way here.
for the bdd - user should follow bddd tutorial only, not classic tutorial
|
|
||
| You do not need any automated tests or code for this. If you are brand new to Testomat.io, this is the right place to start. | ||
|
|
||
| What you will do: |
There was a problem hiding this comment.
I suggest making a diagram of these 5 steps or adding links for quick navigation.
There was a problem hiding this comment.
This is too much for the tutorial. I can add whatever information, lots and lots of text and screenshots, but will it help the user to do the simple steps, or will it mess the user up?
|
|
||
| ## Create a suite | ||
|
|
||
| Test cases always live inside a suite, so you make a suite first. A suite is just a group of related tests, like all the tests for your login page. |
There was a problem hiding this comment.
I suggest making a diagram of tree structure.
There was a problem hiding this comment.
how many diagrans there should be per 1 article and will it be useful for the user?
3 participants
Added the Manual testing classic tutorial and screenshots to it
Task
Create Tutorials for Key Workflows
#372