Skip to content
Snippets Groups Projects
Commit 96a66ad4 authored by Dominik Zobel's avatar Dominik Zobel
Browse files

Add exercise for debugging strategies

parent e0752166
No related branches found
No related tags found
1 merge request!56Debugging Strategies lecture notes
Pipeline #67057 passed
......@@ -47,7 +47,7 @@ website:
- "exercises/programming_paradigms.qmd"
- "exercises/data_structures.qmd"
- "exercises/complexity.qmd"
# - "exercises/debugging-strategies.qmd"
- "exercises/debugging-strategies.qmd"
# - "exercises/good_scientific_practice.qmd"
# - "exercises/user_experience.qmd"
# - "exercises/testing.qmd"
......
---
title: "Debugging strategies"
---
### Explain your approach on locating bugs
_The tasks should be done using the test repository <https://github.com/gweis/isodate>,
specifically commit 8856fdf0 (HEAD of `master` branch at the moment of writing this)._
_It is a Python library to parse date and times according to the ISO 8601 standard.
Although it works great in many use cases, there are some documented bugs in the code.
But the linked repository was not chosen to cast a bad light on it in any way.
In fact, it does a good job providing tests and stating which problems still occur in the code._
**Tasks**
1. Check out the code and run the test suite. This can typically be done by issueing
`python -m unittest` in the `src/isodate` directory (not within the `tests` directory).
You should find that it reports two failures and one error.
Document the actual output stating that.
2. Pick one of the three issues and investigate it. Narrow down the code area, where the issue occurs.
Document your strategy of narrowing it down step by step.
**This task is NOT about fixing any of the issues^[You can try, if you want. But this is NOT part of the homework]!**
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment