11810 python lines counted using lizard
How to:
> pip install lizard
> lizard -l python # -l chooses the lines of the language lizard should count
How to:
> pip install coverage
> coverage run -m pytest # in tests folder
> coverage report # or "coverage html" for a nice representation
Link to commit for coverage instrumentation

Link to commit for coverage instrumentation
)
Link to the commit with coverage measurement
Edited the print_coverage later on
[Screenshot of the coverage measurement]
Link to the commit with coverage measurement
[Screenshot of the coverage measurement]
For bucket sort, the coverage should be the same for all lists except for the empty one, because all the possible inputs trigger all the branches except for the one checking for an empty list. Due to an error whenever I am attempting to input an empty list which could be fixed only by editing the code of the authors of this repo, I am unable to present that one in the screenshot.
[Link to the commit for gnome_sort.py] [Added more coverage]
[Link to the commit for jump_search.py]
Link to the commit with coverage measurement

Link to the commit with coverage measurement

Link to a commit the new test tree depth tests
The coverage goes straight to 96% as it had no previous tests covering it. So by creating tests covering each branch of the depth_of_tree function, we could already cover 96% of it without needing to enchance anything, just making new tests.
Link to a commit the new test tree depth tests
The coverage goes straight to 97% as it had no previous tests covering it. So by creating tests covering each branch of the is_full_binary function, we could already cover 97% of it without needing to enchance anything, just making new tests.
The overall coverage for the project went lower because there are functions inside of the binary_search.py file which are not being covered by any other tests than mine. The coverage for the whole binary_search.py file is 41% due to the fact that there are multiple functions within it, and I have improved the coverage only for one of them. Furthermore, the code doesn't have any tests to cover for those missing it. Below I will provide a screenshot of the coverage html with my binary_search function.
Here, the overall coverage for the project increases due to the fact that within bucket_sort.py, the only function in it is bucket_sort, which is 95% covered by the tests I've added. It's 95% because it lacks the case for an empty list, which doesn't work (mentioned above why).
There were no previous tests for jump_search, and therefore the coverage is at 94% for test_jump_search.py. As we can see, the overall coverage has increased from 92% to 93%. This has been achieved by creating tests for each branch of the jump_sort function.
There were no previous tests for gnome_sort and hence, the coverage for test_gnome_sort.py is 97%. As we can observe, the overall coverage has jumped from 93% to 94%. This has been achieved by creating tests for each branch of the gnome_sort function.
The overall coverage goes down a bit from 92% to 86% because bubble_sort is also included in the report and it's percentage is 56% because not all the functions are tested in the file bubble_sort.py, just the main function bubble_sort(), as we can see in the html report down below the coverage for the function bubble_sort is at 100%. But we can see the coverage of the function with the test file test_bubble_sort() being at 95% this contributing to the higher overall coverage.
We can see here the same things happening as with bubble_sort. The overall coverage goes down from 86% to 84% because the coverage report is also considering the merge_sort.py file and all of it's functions, but from the html report we can see that the coverage for merge_sort is at 100%. Adding the test to the coverage improves it, but becuase it considers also the merge_sort.py file the overall coverage is reduced
- Made README until coverage html + individual parts + overall
- Own 2 function coverage instrumentation
- Test files for chosen functions
- Wrote my individual part on the README
- Own 2 function coverage instrumentation
- Test files for chosen functions
- Wrote my own part of the README
- Do 2 function coverage instrumentations
- Test files for the two functions mentioned above
- Wrote my own part of the README
- Chose 2 functions and instrumented them
- Made test files for the two functions





