From Fedora Project Wiki
(Created page with "{{QA/Test_Case |description= tokei is a tool that analyzes code in a project and offers project statistics. It shows you exactly how many code, comments, or blank lines you ha...") |
No edit summary |
||
Line 1: | Line 1: | ||
{{QA/Test_Case | {{QA/Test_Case | ||
|description= tokei is a tool that analyzes code in a project and offers project statistics. It shows you exactly how many code, comments, or blank lines you have. | |description= tokei is a tool that analyzes code in a project and offers project statistics. It shows you exactly how many code, comments, or blank lines you have. | ||
|setup= | |setup= | ||
|actions= | |actions= | ||
# Execute <code> dnf install tokei </code> | |||
# | # Reports on the code in <code>./foo</code> and all subfolders. <code> $ tokei ./foo </code> | ||
# | # Report on multiple folders in the same call simply add a comma, or a space followed by another path <code> tokei ./foo, ./bar, ./baz </code> | ||
# | # Report on each file by using <code> $ tokei ./foo --files</code> | ||
|results= | |results= | ||
The following must be true to consider this a successful test run. Be brief ... but explicit. | The following must be true to consider this a successful test run. Be brief ... but explicit. | ||
# Step #1 completes without error | # Step #1 completes without error | ||
# | # Step #2 Reports back with all the code in the folder | ||
# | # Step #3 Reports aggregated sum of all the code report | ||
# Step #4 Reports about each file and then a summary at the end | |||
|optional=Optionally provide hints for exploratory testing. | |optional=Optionally provide hints for exploratory testing. | ||
}} | }} |
Latest revision as of 18:22, 3 April 2018
Description
tokei is a tool that analyzes code in a project and offers project statistics. It shows you exactly how many code, comments, or blank lines you have.
How to test
- Execute
dnf install tokei
- Reports on the code in
./foo
and all subfolders.$ tokei ./foo
- Report on multiple folders in the same call simply add a comma, or a space followed by another path
tokei ./foo, ./bar, ./baz
- Report on each file by using
$ tokei ./foo --files
Expected Results
The following must be true to consider this a successful test run. Be brief ... but explicit.
- Step #1 completes without error
- Step #2 Reports back with all the code in the folder
- Step #3 Reports aggregated sum of all the code report
- Step #4 Reports about each file and then a summary at the end
Optional
Optionally provide hints for exploratory testing.