-
Notifications
You must be signed in to change notification settings - Fork 266
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
re-added a removed testcase #51
base: main
Are you sure you want to change the base?
Conversation
utilizing a removed test that tests proper testing functionality
The PR should have been made to the ensf400-ws24 branch, not to main. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Select one of the two testing options
@@ -3,5 +3,5 @@ | |||
def test_always_passes(): | |||
assert True | |||
|
|||
# def test_always_fails(): | |||
# assert False | |||
def test_always_fails(): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change will cause the CI/CD workflow to always fail, and cannot be accepted as-is. There are valid reasons to use such, but additional code that uses assert
to allow for false failures would also be required and is not represented in this commit.
"editor.fontFamily": "'MesloLGS NF', 'Droid Sans Mono', 'monospace', monospace", | ||
"python.testing.pytestArgs": ["tests"], | ||
"python.testing.unittestEnabled": false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Usually, we use only one of these.
I uncommented the always fail test case, that I'm pretty sure is used to test if the test package is operating correctly.