-
Notifications
You must be signed in to change notification settings - Fork 5
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
Test names case (in)sensitivity #93
Comments
Not sure what the solution is for this. I would feel tempted to add the test number to each image cache. |
This example runs just fine for me in Linux. I get files like |
* Renaming file and changing thumbnail * Small fix to doc build * Activating plots * Removing duplicated plots. Removing skip_if_no_xserver * Increasing time build * Fixing mesh color bug * Using pytest-pyvista action for cache. Activating more tests. Improving some * Changing function name * Removing unneeded eplot and prints in fixture * Grouping tests. Cosmetic changes * Reorg tests. Plotting some returned plotter objects. Removing unnecessary plots in fixtures. * Small fix to test * Updating image cache * Updating cache * Using a higher tolerance in bc legend tests * Updating image cache * Adding pytest-pyvista configuration to fixture. * Updating image cache * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * Updating cache image * Update image cache * Testing adding the files to the PR * Commenting out assertion * commenting unused variable * fixing yaml * empty commit to trigger cicd * empty commit to reset the plotting.py file * Revent changes * fixing plot bug * reventing ci.yml file * reverting to main * Adding files to PR * removing 'local' tag from git config * Fixing link in wsl * Updating image cache and removing PR part * Making sure the theme is applied at the beginning. * Improvement to bug template * Resetting image cache to main * recache some tests * removing dedundant tests * removing codacy warning * Removing some start imports * Adding automatically missing images * Adding back useful stuff * Recache some test case senstive * Adding more fields to test to avoid pytest.pyvista names collision. See pyvista/pytest-pyvista#93 * adding missing image cache --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Yes. |
In Pytest you can do:
Pytest won't be able to generate
"mechanical"
and"meCHANICAL"
. Nor"UX"
.Reference:
The text was updated successfully, but these errors were encountered: