Issue 67: Find the students who improved in every successive test #66

The problem

Write a program that accepts classroom marks from multiple tests and identifies students whose marks increased in every successive test.

The file

python-open-source-challenge/issue-67.py

That is the only file you need to open, and the only one you should change.

The function you are fixing is steadily_improving(). There are 2 # TODO: comments in it. Each one sits next to something that is wrong or missing — they are clues, not answers.

What to do

1. Comment /claim below. A bot assigns this issue to you.
2. Fork the repository and create a branch: git checkout -b fix/issue-67
3. Run the file first, so you can see what failing looks like:

   python3 python-open-source-challenge/issue-67.py

   You will get an AssertionError. That is expected — it is the work waiting for you.
4. Work through the # TODO: comments and repair the code.
5. Run it again until it prints All checks passed!
6. Open a pull request whose description contains Closes #66.

How you know you are done

python3 python-open-source-challenge/issue-67.py

Nothing else counts as finished.

Rules

• Do not rewrite the program from scratch. Reading somebody else's code and making a small, careful change is the skill this is teaching.
• Do not edit check_solution(). That is the marking scheme. Changing the test so it agrees with your code is not a fix.
• Change only python-open-source-challenge/issue-67.py. One issue, one file, one pull request.

What you will practise

• building a new list by filtering or transforming an existing one
• working out an approach on paper before writing the code

What to expect: a few moving parts — building up a dictionary, returning more than one value, or a function that calls itself. Take it slowly and run the file after every small change.

No prior open source experience is assumed. This repository exists so that this can be your first pull request.

Stuck?

Read check_solution() at the bottom of the file first. The assert lines spell out exactly what the function should return for a given input, and that is often clearer than the description above.

Still stuck? Comment here saying what you have tried. Asking is not failing.