Add keystroke timing tracking

[sweep-mine[bot]]

Description

This pull request adds keystroke timing tracking to the project.

Summary

• Added tests/test_keystroke.py to test keystroke timing tracking
• Added tests/test_statistics.py to test statistics with zero total and get keystrokes
• Added tests/test_view.py to test user input and keystroke timestamps
• Added ultra_type/keystroke.py to implement keystroke timing tracking
• Updated ultra_type/statistics.py to include keystrokes list
• Updated ultra_type/view.py to include keystroke class

Fixes #25.

---

🎉 Latest improvements to Sweep:

• Sweep now uses the rope library to refactor Python! Check out Large Language Models are Bad at Refactoring Code. To have Sweep refactor your code, try sweep: Refactor <your_file>.py!
• Sweep finds and fixes bugs in your code by writing unit tests! Check out Having GPT-4 Iterate on Unit Tests like a Human.

---

💡 To get Sweep to edit this pull request, you can:

• Comment below, and Sweep can edit the entire PR
• Comment on a file, Sweep will only modify the commented file
• Edit the original issue to get Sweep to recreate the PR from scratch

[sweep-mine[bot]]

Sandbox Executions

[sweep-mine[bot]]

Apply Sweep Rules to your PR?

• [ ] Apply: All docstrings and comments should be up to date.
• [ ] Apply: Code should not contain commented out code blocks.
• [ ] Apply: Variable and function names should be descriptive and follow a consistent naming convention.
• [ ] Apply: Avoid redundant or unused imports and variables.
• [ ] Apply: Import modules using absolute imports.
• [ ] Apply: All new business logic should have corresponding unit tests in the tests/ directory.
• [ ] Apply: For unit tests we use pytest. If we have class.py, we should have class_test.py in the tests directory.
• [ ] Apply: Any clearly inefficient or repeated code should be optimized or refactored.
• [ ] Apply: Update the README.md file whenever a new feature is added. Make sure to include a description of the feature and any new commands.

[sweep-mine[bot]]

The command: Run # stop the build if there are Python syntax errors or undefined names yielded the following error: ##[error]Process completed with exit code 1. Here are the logs:

./tests/test_statistics.py:45:26: F821 undefined name 'expected_stats'
self.assertEqual(expected_stats, actual_stats)
^
./ultra_type/statistics.py:18:10: E999 SyntaxError: unmatched '}'
1     E999 SyntaxError: unmatched '}'
1     F821 undefined name 'expected_stats'
2

[sweep-mine[bot]]

The command: Run # stop the build if there are Python syntax errors or undefined names yielded the following error:

[error]Process completed with exit code 1.

Here are the logs: ./tests/test_statistics.py:45:26: F821 undefined name 'expected_stats' self.assertEqual(expected_stats, actual_stats) ^ ./ultra_type/statistics.py:18:10: E999 SyntaxError: unmatched '}' 1 E999 SyntaxError: unmatched '}' 1 F821 undefined name 'expected_stats' 2

Hi @sweep-mine[bot],

I am making the following changes:

File Path	Proposed Changes
tests/test_statistics.py	Modify tests/test_statistics.py with contents: • Locate the test method test_get_stats_with_zero_total around line 43. • Define the variable expected_stats before it is used in the assertion on line 45. The definition should be expected_stats = {'success_rate': 0} to match the expected output when the total count is zero. • Remove the duplicate test method test_get_stats_with_zero_total that starts on line 43, as there is already a correctly implemented method with the same name starting on line 47.
tests/test_statistics.py	Run tests/test_statistics.py through the sandbox.
ultra_type/statistics.py	Modify ultra_type/statistics.py with contents: • Locate the get_stats method within the Statistics class. • Remove the unmatched '}' at the end of the get_stats method, which is currently on line 18. • Ensure that the closing brace for the get_stats method is correctly placed after the return statement, with proper indentation.
ultra_type/statistics.py	Run ultra_type/statistics.py through the sandbox.