[Two Bucket]: Update Test Generation Template To Accommodate New Tests

[BethanyG]

Recently, we updated the Two Bucket exercise to incorporate new tests from the problem-specifications repo. Unfortunately, these new tests have broken test generation for the exercise, and had to be skipped in the tests.toml file.

We need to:

1. Figure out why running bin/generate_tests.py is failing for two-bucket when the three tests are included.
   The three tests are:

   • [449be72d-b10a-4f4b-a959-ca741e333b72]
     description = "Not possible to reach the goal"
     include = false

   • [aac38b7a-77f4-4d62-9b91-8846d533b054]
     description = "With the same buckets but a different goal, then it is possible"
     include = false

   • [74633132-0ccf-49de-8450-af4ab2e3b299]
     description = "Goal larger than both buckets is impossible"
     include = false

2. Make the appropriate edits to the two-bucket JinJa2 template
3. Regenerate the test file for two-bucket by running bin/generate_tests.py two-bucket
4. Test that the code in the two-bucket example.py file passes all the re-generated tests.
5. Make any necessary edits to example.py if there are any test failures.

This task requires knowledge of (or interest in learning):

JinJa2 templating
JinJa2 docs (the version we use)
The Python Test Generator

[mhorod]

I think I have solved the issue. Is there any formatter for template files that I should use before committing my changes?

[BethanyG]

Excellent, @mhorod. Thank you so much for taking this on! 🌟

Is there any formatter for template files that I should use before committing my changes?

No - we don't yet have a JinJa formatter in place. 😅 I'll have to eyeball it. If you have experience with JinJa, and have recommendations on formatters, I'd love to hear them. We have an issue open here on JinJa templating and linting: issue 2698

When you do check in, please include the following in your PR:

1. The edited tests.toml file.
2. The new JinJa2 template
3. The regenerated tests file created from the new template.
4. Any changes needed to the two bucket example code, after running it against the newly regenerated file.
5. An edited config.json for two-bucket, adding your GH handle to the contributors key. 😄

Again -- many thanks for working on this!! 🌈

[BethanyG]

Closing now that #2929 has been merged.