Currently points to dthm4kaiako website, which is now outdated.

The fourth test case for "Total of evens" (total-evens) is currently print(total_of_even_numbers()) which creates a TypeError because the function requires 1 argument. This question cannot be answered because the function definition is locked so it cannot be modified so that the list numbers has a default value.

Python code
def double_even(number):
if number % 2 == 0:
number = number * 2
print(number)

getting an extra line that is printing None in the unit tests

Include video or animation

This could have gratification implications.

The question driver-speed uses an example of check_speed(70), but it should really be check_speed(75) to match the requirements of the question

Showing how much the codewof website is being used, similar to parkrun.
Total hours run: 0Years 210Days 18Hrs 42Min 29Secs - Total distance run: 40,730km

Having the homepage showing ?? questions, ?? users, ?? submissions.

The code below was submitted as an answer to the Days to Target function question.

def days_to_target(starting_population, target_population):
    if starting_population - target_population >= 0 :
        return 0
    else:
        keep_going = True
        day_count = 0
        current_population  = starting_population
        
        while keep_going:
            current_population *= 2
            day_count += 1
            if current_population >= target_population:
               	keep_going = False
                return day_count

When the code is run locally (I ran it in Wing), the function runs without an error being thrown and all of the test cases pass, but when it is run in codeWOF, I get the following error:

IndentationError: unindent does not match any outer indentation level on line 14
                return day_count

                ^

I have not been able to figure out why the behaviour is different when the same function is run in these two different environments.

If the user submits this code as their answer:

def print_score(points, total_possible):
    print(str(points / total_possible * 100) + '%')

It contains the correct amount of decimal places in the answer. However, if they submit this code:

def print_score(points, total_possible):
    print("{}%".format(points / total_possible * 100))

Then it is marked as incorrect. When the two answers are run in a normal IDE, both are marked as correct. I assume that this rounding problem is to do with Skulpt, which would mean that this question should be removed, or modified.

Add application for managing research studies on codeWOF.

Todo

• Add models
• Add views
• Add forms
• Email copy of study and consent form to user
• Filter questions for user
• Require login for all questions pages
• Prevent user registering for study more than once
• Add information how to leave study in enrolled
• List questions with types

Phase 2 (tasks to do later)

• Handle multiple studies (limit to one study at a time)
• Add researcher relationship for study
• Add admin view for study researcher

This seems to have been introduced in #83

On the first run of sampledata after a fresh build/start/update the error pasted at the bottom of this issue occurs.

This happens when we try to create a batch of question attempts (error in AttemptFactory.py). so far I am unsure what the exact issue is. But as this is only a local error and the sampledata command runs fine on a second run this is low priority.

Research studies loaded.
Traceback (most recent call last):
  File "./manage.py", line 27, in <module>
    execute_from_command_line(sys.argv)
  File "/docker_venv/lib/python3.6/site-packages/django/core/management/__init__.py", line 381, in execute_from_command_line
    utility.execute()
  File "/docker_venv/lib/python3.6/site-packages/django/core/management/__init__.py", line 375, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/docker_venv/lib/python3.6/site-packages/django/core/management/base.py", line 316, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/docker_venv/lib/python3.6/site-packages/django/core/management/base.py", line 353, in execute
    output = self.handle(*args, **options)
  File "/codewof/codewof/general/management/commands/sampledata.py", line 83, in handle
    AttemptFactory.create_batch(size=50)
  File "/docker_venv/lib/python3.6/site-packages/factory/base.py", line 576, in create_batch
    return [cls.create(**kwargs) for _ in range(size)]
  File "/docker_venv/lib/python3.6/site-packages/factory/base.py", line 576, in <listcomp>
    return [cls.create(**kwargs) for _ in range(size)]
  File "/docker_venv/lib/python3.6/site-packages/factory/base.py", line 564, in create
    return cls._generate(enums.CREATE_STRATEGY, kwargs)
  File "/docker_venv/lib/python3.6/site-packages/factory/django.py", line 141, in _generate
    return super(DjangoModelFactory, cls)._generate(strategy, params)
  File "/docker_venv/lib/python3.6/site-packages/factory/base.py", line 501, in _generate
    return step.build()
  File "/docker_venv/lib/python3.6/site-packages/factory/builder.py", line 272, in build
    step.resolve(pre)
  File "/docker_venv/lib/python3.6/site-packages/factory/builder.py", line 221, in resolve
    self.attributes[field_name] = getattr(self.stub, field_name)
  File "/docker_venv/lib/python3.6/site-packages/factory/builder.py", line 375, in __getattr__
    extra=context,
  File "/docker_venv/lib/python3.6/site-packages/factory/declarations.py", line 196, in evaluate
    value = next(iter(self.iterator))
StopIteration```

We need to create roughly 3 to 6 questions to populate the question bank. Questions should be at a beginner programming level (for team members: think of questions at the end of a 121 lab) and focus only on this concept.

We need to create roughly 3 to 6 questions to populate the question bank. Questions should be at a beginner programming level (for team members: think of questions at the end of a 121 lab) and focus only on this concept.

We need to create roughly 3 to 6 questions to populate the question bank. Questions should be at a beginner programming level (for team members: think of questions at the end of a 121 lab) and focus only on this concept.

Can achieve this by using user.pk with date to create seed.

We need to create roughly 3 to 6 questions to populate the question bank. Questions should be at a beginner programming level (for team members: think of questions at the end of a 121 lab) and focus only on this concept.

These questions must be of the program type, as these are the only ones that take input.

When the tests are run for the "Add 10" question they fail with the error message:

ExternalError: TypeError: t.test_input_list is undefined on line 1

This seems to only happen when the code includes input(), if it just prints 34 then the first test passes, and when there is no code written it gives the expected "No Python code provided." output.

We need to create roughly 3 to 6 questions to populate the question bank. Questions should be at a beginner programming level (for team members: think of questions at the end of a 121 lab) and focus only on this concept.

Two features in #75 (activity graph and badge card) weren't quite finished.

• Activity graph is intended to be similar to the github activity graph, and will track each day either (not sure which one) if the user has achieved their goal number of questions per day or just solved a question on that day.

• Badge card was a template to make the badges appear in a similar fashion to the questions. Maree can't quite remember the end goal but there might be some further information on it in her final report.

Activity graph code

Badge card template

Change the layout of the list of questions to be similar to that shown in the image attached.

• They could be ordered alphabetically, and would rearrange themselves to fit to the screen size.

• Unsure of what the best colours would be to accommodate for a range of colour-blindness.

• Questions that have been completed would be filled with the colour of that question type, and questions that have not been completed would have the colour of the question type as their border.

We need to create roughly 30 questions to fill the question bank. Questions should be at a beginner programming level and focus on one concept.

Should provide links to

• Questions to do
• Research studies
• Profile updates

Create a debugging question type (like parsons is a question type).

Sometimes questions that a user has already answered (on another day) show up under their questions for the day on their dashboard. If we are going to show them questions they have already answered after some minimum time limit (e.g. one or two months) then they should not be formatted as a question that has been answered, i.e. there should be no tick in the checkbox and the background should not be highlighted.

It would also be nice if the questions shown for the questions of the day could change over at midnight.

We need to create roughly 3 to 6 questions to populate the question bank. Questions should be at a beginner programming level (for team members: think of questions at the end of a 121 lab) and focus only on this concept.

Replace with more established and supported https://github.com/vintasoftware/django-templated-email

Options should include:

• Student
• Teacher

Currently having a Django application with the same name as the Django project, as the same name as the repository is confusing.

Currently on user update form, they can remove their user type.

When I wrote the question I didn't consider that 0! === 1.

If x is less than 1 or greater than 10 your function should return None.

This sentence in the question itself should better reflect that these values should not be worried about, rather than that they are invalid – because 0 and all values greater than 10 are valid

We need to create roughly 3 to 6 questions to populate the question bank. Questions should be at a beginner programming level (for team members: think of questions at the end of a 121 lab) and focus only on this concept.

It appears users are struggling with understanding the test case nature of codeWOF questions. A tutorial should help ease them into the system, possibly interactive for a question.

See https://introjs.com/

Allow study researchers (#30) to access the data they require.

Currently a mix of spaces and tabs will cause Python to crash.

Should contain the following information:

• Number of questions per type.
• Types which require questions (based off user submissions).
• Information about planned feature to submit questions.

Go through and bold all of the prints and returns in the text of the questions.
Made this an issue so I could make a branch to fix this on.