search

reconsumeralization / CodeCurse

CodeCurse AI IDE
MIT License
2 stars 0 forks source link

Sweep: Write unit tests for workstation and all files in the directory #14

Closed reconsumeralization closed 1 year ago

reconsumeralization commented 1 year ago

Details

Unit Tests: Write unit tests to test all the features in the workstation directory.

Then Write unit tests for everything else!

Checklist - [X] Create `workbench/features/workstation/workstation.test.ts` ✓ https://github.com/reconsumeralization/CodeCurse/commit/a1ee020934308f1d5331372240ed238089886b52 - [X] Check `workbench/features/workstation/workstation.test.ts` ✓ https://github.com/reconsumeralization/CodeCurse/commit/9b926dd7928ce9249f6cee89c59bd3778688360c ![Flowchart](http://24.199.78.105:8082/public/69a14d2be552b3ecb1564f3df38a362bf6127efa99e09539cfdde61a3900a99b_14_flowchart.svg)
sweep-ai[bot] commented 1 year ago

Here's the PR! https://github.com/reconsumeralization/CodeCurse/pull/17.

⚡ Sweep Basic Tier: I'm using GPT-3.5. You have 0 GPT-4 tickets left for the month and 0 for the day.

For more GPT-4 tickets, visit our payment portal. For a one week free trial, try Sweep Pro (unlimited GPT-4 tickets).

Actions (click)

Step 1: 🔎 Searching

I found the following snippets in your repository. I will now analyze these snippets and come up with a plan.

Some code snippets I looked at (click to expand). If some file is missing from here, you can mention the path in the ticket description. https://github.com/reconsumeralization/CodeCurse/blob/0768d18976c91ec297aaf26d99ec817848ca6bbd/workbench/libraries/reselect-master/reselect-master/README.md#L515-L685 https://github.com/reconsumeralization/CodeCurse/blob/0768d18976c91ec297aaf26d99ec817848ca6bbd/workbench/features/extensions/comments.ts#L68-L169

Step 2: ⌨️ Coding

Write unit tests in the `workbench/features/extensions/comments.test.ts` file to cover all the features in the `workbench/features/extensions/comments.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/codemirror/codemirror.test.ts` file to cover all the features in the `workbench/features/codemirror/codemirrorSelectors.ts` and `workbench/features/codemirror/codemirrorSlice.ts` files. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/comment/comment.test.ts` file to cover all the features in the `workbench/features/comment/commentSelectors.ts` and `workbench/features/comment/commentSlice.ts` files. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/extensions/activeLineGutter.test.ts` file to cover all the features in the `workbench/features/extensions/activeLineGutter.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/extensions/autocomplete.test.ts` file to cover all the features in the `workbench/features/extensions/autocomplete.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/extensions/cmdZBar.test.ts` file to cover all the features in the `workbench/features/extensions/cmdZBar.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/extensions/diff.test.ts` file to cover all the features in the `workbench/features/extensions/diff.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/extensions/ghostText.test.ts` file to cover all the features in the `workbench/features/extensions/ghostText.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/extensions/hackDiff.test.ts` file to cover all the features in the `workbench/features/extensions/hackDiff.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/extensions/indentLines.test.ts` file to cover all the features in the `workbench/features/extensions/indentLines.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/extensions/lsp.test.ts` file to cover all the features in the `workbench/features/extensions/lsp.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/extensions/minimap.test.ts` file to cover all the features in the `workbench/features/extensions/minimap.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/extensions/newLineText.test.ts` file to cover all the features in the `workbench/features/extensions/newLineText.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/extensions/selectionTooltip.test.ts` file to cover all the features in the `workbench/features/extensions/selectionTooltip.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/extensions/storePane.test.ts` file to cover all the features in the `workbench/features/extensions/storePane.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/extensions/syntax.test.ts` file to cover all the features in the `workbench/features/extensions/syntax.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/fixLSP/fixLSP.test.ts` file to cover all the features in the `workbench/features/fixLSP/fixLSPSelectors.ts` and `workbench/features/fixLSP/fixLSPSlice.ts` files. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/generation/generate.test.ts` file to cover all the features in the `workbench/features/generation/generate.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/linter/extension.test.ts` file to cover all the features in the `workbench/features/linter/extension.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/linter/fixLSPExtension.test.ts` file to cover all the features in the `workbench/features/linter/fixLSPExtension.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/linter/lint.test.ts` file to cover all the features in the `workbench/features/linter/lint.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/logging/logging.test.ts` file to cover all the features in the `workbench/features/logging/loggingSelectors.ts` and `workbench/features/logging/loggingSlice.ts` files. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/lsp/languageServer.test.ts` file to cover all the features in the `workbench/features/lsp/languageServerSelector.ts` and `workbench/features/lsp/languageServerSlice.ts` files. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/lsp/lspPlugin.test.ts` file to cover all the features in the `workbench/features/lsp/lspPlugin.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/lsp/stdioClient.test.ts` file to cover all the features in the `workbench/features/lsp/stdioClient.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/window/fileUtils.test.ts` file to cover all the features in the `workbench/features/window/fileUtils.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. Write unit tests in the `workbench/features/window/state.test.ts` file to cover all the features in the `workbench/features/window/state.ts` file. Ensure that each feature is thoroughly tested and that the tests cover all possible scenarios and edge cases. ## Update relevant files to import and use the newly created unit test files: Import the necessary functions and classes from `workbench/features/workstation/workstation.test.ts` in the `workbench/features/workstation/workstation.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/extensions/comments.test.ts` in the `workbench/features/extensions/comments.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/codemirror/codemirror.test.ts` in the `workbench/features/codemirror/codemirrorSelectors.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/codemirror/codemirror.test.ts` in the `workbench/features/codemirror/codemirrorSlice.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/comment/comment.test.ts` in the `workbench/features/comment/commentSelectors.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/comment/comment.test.ts` in the `workbench/features/comment/commentSlice.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/extensions/activeLineGutter.test.ts` in the `workbench/features/extensions/activeLineGutter.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/extensions/autocomplete.test.ts` in the `workbench/features/extensions/autocomplete.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/extensions/cmdZBar.test.ts` in the `workbench/features/extensions/cmdZBar.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/extensions/diff.test.ts` in the `workbench/features/extensions/diff.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/extensions/ghostText.test.ts` in the `workbench/features/extensions/ghostText.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/extensions/hackDiff.test.ts` in the `workbench/features/extensions/hackDiff.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/extensions/indentLines.test.ts` in the `workbench/features/extensions/indentLines.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/extensions/lsp.test.ts` in the `workbench/features/extensions/lsp.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/extensions/minimap.test.ts` in the `workbench/features/extensions/minimap.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/extensions/newLineText.test.ts` in the `workbench/features/extensions/newLineText.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/extensions/selectionTooltip.test.ts` in the `workbench/features/extensions/selectionTooltip.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/extensions/storePane.test.ts` in the `workbench/features/extensions/storePane.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/extensions/syntax.test.ts` in the `workbench/features/extensions/syntax.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/fixLSP/fixLSP.test.ts` in the `workbench/features/fixLSP/fixLSPSelectors.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/fixLSP/fixLSP.test.ts` in the `workbench/features/fixLSP/fixLSPSlice.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/generation/generate.test.ts` in the `workbench/features/generation/generate.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/linter/extension.test.ts` in the `workbench/features/linter/extension.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/linter/fixLSPExtension.test.ts` in the `workbench/features/linter/fixLSPExtension.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/linter/lint.test.ts` in the `workbench/features/linter/lint.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/logging/logging.test.ts` in the `workbench/features/logging/loggingSelectors.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/logging/logging.test.ts` in the `workbench/features/logging/loggingSlice.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/lsp/languageServer.test.ts` in the `workbench/features/lsp/languageServerSelector.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/lsp/languageServer.test.ts` in the `workbench/features/lsp/languageServerSlice.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/lsp/lspPlugin.test.ts` in the `workbench/features/lsp/lspPlugin.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/lsp/stdioClient.test.ts` in the `workbench/features/lsp/stdioClient.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/window/fileUtils.test.ts` in the `workbench/features/window/fileUtils.ts` file to use the newly created unit test files for testing the features. Import the necessary functions and classes from `workbench/features/window/state.test.ts` in the `workbench/features/window/state.ts` file to use the newly created unit test files for testing the features. - [X] Check `workbench/features/workstation/workstation.test.ts` ✓ https://github.com/reconsumeralization/CodeCurse/commit/9b926dd7928ce9249f6cee89c59bd3778688360c
Sandbox logs for https://github.com/reconsumeralization/CodeCurse/commit/9b926dd7928ce9249f6cee89c59bd3778688360c
trunk init 1/3 ✓ 
⡿ Downloading Trunk 1.17.1...
⡿ Downloading Trunk 1.17.1...
⢿ Downloading Trunk 1.17.1...
⣻ Downloading Trunk 1.17.1...
⣽ Downloading Trunk 1.17.1...
⣾ Downloading Trunk 1.17.1...
⣷ Downloading Trunk 1.17.1...
✔ Downloading Trunk 1.17.1... done
⡿ Verifying Trunk sha256...
✔ Verifying Trunk sha256... done
⡿ Unpacking Trunk...
✔ Unpacking Trunk... done

✔ 15 linters were enabled (.trunk/trunk.yaml)
  actionlint 1.6.26 (2 github-workflow files)
  checkov 3.0.19 (1 docker, 8 json, 11 yaml files)
  git-diff-check (188 files)
  hadolint 2.12.0 (1 docker file) (created .hadolint.yaml)
  markdownlint 0.37.0 (12 markdown files) (created .markdownlint.yaml)
  osv-scanner 1.4.3 (1 lockfile file)
  oxipng 9.0.0 (3 png files)
  prettier 3.0.3 (2 javascript, 8 json, 12 markdown, 68 typescript, 11 yaml files)
  shellcheck 0.9.0 (55 shell files) (created .shellcheckrc)
  shfmt 3.6.0 (55 shell files)
  svgo 3.0.2 (11 svg files) (created svgo.config.js)
  terrascan 1.18.3 (1 docker file)
  trivy 0.46.1 (1 docker, 11 yaml files)
  trufflehog 3.62.1 (189 files)
  yamllint 1.32.0 (11 yaml files) (created .yamllint.yaml)
Next Steps
 1. Read documentation
    Our documentation can be found at https://docs.trunk.io
 2. Get help and give feedback
    Join the Trunk community at https://slack.trunk.io
trunk fmt workbench/features/workstation/workstation.test.ts || exit 0 2/3 ✓ 
 ✔ Formatted workbench/features/workstation/workstation.test.ts
Re-checking autofixed files...

Checked 1 file
✔ No issues
trunk check --fix --print-failures workbench/features/workstation/workstation.test.ts 3/3 ✓ 
Checked 1 file
✔ No issues
--- ## Step 3: 🔁 Code Review I have finished reviewing the code for completeness. I did not find errors for [`sweep/add-unit-tests`](https://github.com/reconsumeralization/CodeCurse/commits/sweep/add-unit-tests). --- ### 🎉 Latest improvements to Sweep: * Sweep now uses the `rope` library to refactor Python! Check out [Large Language Models are Bad at Refactoring Code](https://docs.sweep.dev/blogs/refactor-python). To have Sweep refactor your code, try `sweep: Refactor .py to be more modular`! * Sweep finds and fixes bugs in your code by writing unit tests! Check out [Having GPT-4 Iterate on Unit Tests like a Human](https://docs.sweep.dev/blogs/ai-unit-tests). --- 💡 To recreate the pull request edit the issue title or description. To tweak the pull request, leave a comment on the pull request. [Join Our Discord](https://discord.com/invite/sweep)
reconsumeralization commented 1 year ago

Sweep: keep going!