The screenshot you provided is not a Testcase but a bug report.
You cannot consider a personal blog as final point of truth , it can be the authors mistake or a unnoticed mistake while uploading file to that web page.
Now coming to your actual question, there is no much difference between writing testcase in a Test Case management Tool and a Excel file. Excel is just another tool.
A tabular test case looks like :
This template was got from the same website ( https://www.softwaretestinghelp.com/test-case-template-examples/ )
There are both merits and demerits for every approach . Its hard to suggest merits and demerits unless you states the following things like :
- What methodology you work in (Agile or waterfall ?)
- What is your sprint length
- How much time you gets for testing
- What is your responsibility ( Is it only manual , is it automation or is it both)
- What is the Team size
- What is the release plan
But i would recommend following things as best practice
- Adapt a TDD where you create test cases parallel to the development. So when the development sprint starts , start your test sprint in parallel and use the time to create the tabular testcases
- Don't wait till you get the actual product to write the testcase and start testing it
- Demand more time for documenting test case in tabular format if current sprint size is insufficient
- First start with just writing down all the use cases that comes to your mind ( means just the title ) . Else you will feel the work tedious . First write down all use cases and once you are satisfied with the use cases you have decided, start writing the test steps and other details in tabular format
- Split features between team members , give each team member the responsibility of testing a particular feature. This will give you more time to focus and document test scenarios for that specific feature than getting nervous about entire product.
- Keep initial few days for test documentation , and start execution only after it is completely done. Don't do it in parallel else you lose focus while testing
- If you are a single QA in a small sprint size team , this will be really hectic tasks and you might lose focus on actual testing and affect test quality
- If you are single QA responsible for both automation and manual , then this will be a really waste of time and effort . It should be a complete no for this approach . Just copy paste the test script title if anyone really want to know what use cases are being tested . If they still insist demand more members into team
Please read : https://sqa.stackexchange.com/a/46008/40022 which explains a general recommendation of any type of documentation