Skip to content

Commit 47f386d

Browse files
committed
added file naming convention for unit test cases
1 parent a82dab5 commit 47f386d

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

README.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,10 +18,11 @@ Conventions
1818
+ Submissions should follow this directory structure
1919

2020
Algorithm_Name/Language_Name/username_filename.extension
21+
Algorithm_Name/Language_Name/username_filename_unittest.extension
2122

2223
+ It is preferred that you prepend or append your files with your Github username or some identifier to avoid overwriting others' implementations. `git blame` is cool, and has many more appropriate applications, but in this context I'd rather pull a flat list of files and be able to check out everyone's contributions that way than have to look through the revisions.
2324

24-
+ Each algorithm should have its corresppnding unit test cases which covers the corner cases, happy/unhappy paths.
25+
+ Each algorithm should have its corresppnding unit test cases (as directory structure suggested above) which covers the corner cases, happy/unhappy paths.
2526
Advantage of doing so is to assert that every thing is covered and algorithm is not broken between code change.
2627
It also helps newbies to have a quick look at the unit test cases and understand the basic usecase of the algorithm.
2728

0 commit comments

Comments
 (0)