-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace pytest with flask test and improve testing setup #105
base: master
Are you sure you want to change the base?
Conversation
GitHub actions yielded the following error. The command that failed is
Please note that the error message indicates that the module This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests. I'm getting the same errors 3 times in a row, so I will stop working on fixing this PR. |
(myvenv) nchohan slack-bot % FLASK_APP=src/index.py flask test Traceback (most recent call last): Usage: flask [OPTIONS] COMMAND [ARGS]... Error: No such command 'test'. |
Sweep: test build failed with the following errors: 2023-09-25T23:45:01.8827513Z ##[group]Run export FLASK_APP=src/index.py && flask test |
GitHub actions yielded the following error. The command that failed is
Please note that the lines have been wrapped in triple backticks for better readability. This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests. |
🚀 Wrote Changes
Hi @upmortem-sweep[bot], I decided to make the following changes:
|
GitHub actions yielded the following error. The command that failed is
Please note that the lines have been wrapped in triple backticks for better readability. This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests. |
🚀 Wrote Changes
Hi @upmortem-sweep[bot], I decided to make the following changes:
|
GitHub actions yielded the following error. The command that failed is
Please note that the lines have been wrapped in triple backticks for better readability. This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests. |
🚀 Wrote Changes
Hi @upmortem-sweep[bot], I decided to make the following changes:
|
GitHub actions yielded the following error. The command that failed is
Please note that the lines have been wrapped in triple backticks for better readability. This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests. |
🚀 Wrote Changes
Hi @upmortem-sweep[bot], I decided to make the following changes:
|
GitHub actions yielded the following error. The command that failed is
Please note that the lines have been wrapped in triple backticks for better readability. This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests. |
🚀 Wrote Changes
Hi @upmortem-sweep[bot], I decided to make the following changes:
|
GitHub actions yielded the following error. The command that failed is
Please note that the lines have been wrapped in triple backticks for better readability. This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests. |
🚀 Wrote Changes
Hi @upmortem-sweep[bot], I decided to make the following changes:
|
GitHub actions yielded the following error. The command that failed is
Please note that the lines have been wrapped in triple backticks for better readability. This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests. |
GitHub actions yielded the following error.
The command that failed is This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests. |
🚀 Wrote Changes
Hi @upmortem-sweep[bot], I decided to make the following changes:
|
GitHub actions yielded the following error.
The command that failed is This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests. |
🚀 Wrote Changes
Hi @upmortem-sweep[bot], I decided to make the following changes:
|
GitHub actions yielded the following error.
The command that failed is This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests. |
🚀 Wrote Changes
Hi @upmortem-sweep[bot], I decided to make the following changes:
|
GitHub actions yielded the following error.
The command that failed is This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests. |
🚀 Wrote Changes
Hi @upmortem-sweep[bot], I decided to make the following changes:
|
Traceback (most recent call last): |
GitHub actions yielded the following error. The command that failed is
Please note that the error message indicates that the module This is likely a linting or type-checking issue with the source code. Update the code changed by the PR. Don't modify the existing tests. |
Working on it... |
Description
This PR addresses the issue #103 by replacing pytest with flask test and improving the testing setup. The goal is to allow running tests using the "flask test" command and avoid the need for the OPENAI_API_KEY environment variable during testing.
Summary of Changes
Please review and merge these changes to improve the testing experience and prevent the mentioned errors.
Fixes #103.
🎉 Latest improvements to Sweep:
💡 To get Sweep to edit this pull request, you can: