Skip to content

Conversation

@usefhamed
Copy link

I uncommented the always fail test case, that I'm pretty sure is used to test if the test package is operating correctly.

@abarcomb-work
Copy link
Collaborator

The PR should have been made to the ensf400-ws24 branch, not to main.

@growlf growlf self-assigned this Feb 25, 2024
Copy link
Owner

@growlf growlf left a 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


# def test_always_fails():
# assert False
def test_always_fails():
Copy link
Owner

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,
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants