Best Python code snippet using pytest
test_pathlib.py
Source: test_pathlib.py
...246 importlib.util, "spec_from_file_location", lambda *args: None247 )248 with pytest.raises(ImportError):249 import_path(simple_module, mode="importlib")250def test_resolve_package_path(tmp_path):251 pkg = tmp_path / "pkg1"252 pkg.mkdir()253 (pkg / "__init__.py").touch()254 (pkg / "subdir").mkdir()255 (pkg / "subdir/__init__.py").touch()256 assert resolve_package_path(pkg) == pkg257 assert resolve_package_path(pkg.joinpath("subdir", "__init__.py")) == pkg258def test_package_unimportable(tmp_path):259 pkg = tmp_path / "pkg1-1"260 pkg.mkdir()261 pkg.joinpath("__init__.py").touch()262 subdir = pkg.joinpath("subdir")263 subdir.mkdir()264 pkg.joinpath("subdir/__init__.py").touch()265 assert resolve_package_path(subdir) == subdir266 xyz = subdir.joinpath("xyz.py")267 xyz.touch()268 assert resolve_package_path(xyz) == subdir269 assert not resolve_package_path(pkg)270def test_access_denied_during_cleanup(tmp_path, monkeypatch):271 """Ensure that deleting a numbered dir does not fail because of OSErrors (#4262)."""272 path = tmp_path / "temp-1"273 path.mkdir()274 def renamed_failed(*args):275 raise OSError("access denied")276 monkeypatch.setattr(Path, "rename", renamed_failed)277 lock_path = get_lock_path(path)278 maybe_delete_a_numbered_dir(path)279 assert not lock_path.is_file()280def test_long_path_during_cleanup(tmp_path):281 """Ensure that deleting long path works (particularly on Windows (#6775))."""282 path = (tmp_path / ("a" * 250)).resolve()283 if sys.platform == "win32":...
ansible_pytest_collections.py
Source: ansible_pytest_collections.py
...5# set by ansible-test to a single directory, rather than a list of directories as supported by Ansible itself6ANSIBLE_COLLECTIONS_PATH = os.path.join(os.environ['ANSIBLE_COLLECTIONS_PATH'], 'ansible_collections')7# this monkeypatch to _pytest.pathlib.resolve_package_path fixes PEP420 resolution for collections in pytest >= 6.0.08# NB: this code should never run under py29def collection_resolve_package_path(path):10 """Configure the Python package path so that pytest can find our collections."""11 for parent in path.parents:12 if str(parent) == ANSIBLE_COLLECTIONS_PATH:13 return parent14 raise Exception('File "%s" not found in collection path "%s".' % (path, ANSIBLE_COLLECTIONS_PATH))15# this monkeypatch to py.path.local.LocalPath.pypkgpath fixes PEP420 resolution for collections in pytest < 6.0.016def collection_pypkgpath(self):17 """Configure the Python package path so that pytest can find our collections."""18 for parent in self.parts(reverse=True):19 if str(parent) == ANSIBLE_COLLECTIONS_PATH:20 return parent21 raise Exception('File "%s" not found in collection path "%s".' % (self.strpath, ANSIBLE_COLLECTIONS_PATH))22def pytest_configure():23 """Configure this pytest plugin."""...
pytest_collection_loader.py
Source: pytest_collection_loader.py
...5import os.path6import sys7ANSIBLE_COLLECTIONS_PATH = os.path.abspath(os.path.join(__file__, '..', '..', '..', '..', '..', '..'))8# this monkeypatch to _pytest.pathlib.resolve_package_path fixes PEP420 resolution for collections in pytest >= 6.0.09def collection_resolve_package_path(path):10 """Configure the Python package path so that pytest can find our collections."""11 for parent in path.parents:12 if str(parent) == ANSIBLE_COLLECTIONS_PATH:13 return parent14 raise Exception('File "%s" not found in collection path "%s".' % (path, ANSIBLE_COLLECTIONS_PATH))15def pytest_configure():16 """Configure this pytest plugin."""17 try:18 if pytest_configure.executed:19 return20 except AttributeError:21 pytest_configure.executed = True22 # If ANSIBLE_HOME is set make sure we add it to the PYTHONPATH to ensure it is picked up. Not all env vars are23 # picked up by vscode (.bashrc is a notable one) so a user can define it manually in their .env file....
namespace_modules_patch.py
Source: namespace_modules_patch.py
...19# we consider all dirs in tests/ to be namespace packages20rootdir = pathlib.Path(__file__).parent.resolve()21namespace_pkg_dirs = [str(d) for d in rootdir.iterdir() if d.is_dir()]22# patched method23def resolve_package_path(path):24 # call original lookup25 result = resolve_pkg_path_orig(path)26 if result is not None:27 return result28 # original lookup failed, check if we are subdir of a namespace package29 # if yes, return the namespace package we belong to30 for parent in path.parents:31 if str(parent) in namespace_pkg_dirs:32 return parent33 return None34def apply_patch():...
How do I check whether a file exists without exceptions?
Overlapping charts in `matplotlib.animation.FuncAnimation` overwrite the alpha parameter
Python `invoke` not printing with multiline commands on Windows
Logging within pytest tests
Disable individual Python unit tests temporarily
How to get message by id discord.py
Determine if variable is defined in Python
pytest does not find tests when structlog is configured
@Patch decorator is not compatible with pytest fixture
What are metaclasses in Python?
If the reason you're checking is so you can do something like if file_exists: open_it()
, it's safer to use a try
around the attempt to open it. Checking and then opening risks the file being deleted or moved or something between when you check and when you try to open it.
If you're not planning to open the file immediately, you can use os.path.isfile
Return
True
if path is an existing regular file. This follows symbolic links, so both islink() and isfile() can be true for the same path.
import os.path
os.path.isfile(fname)
if you need to be sure it's a file.
Starting with Python 3.4, the pathlib
module offers an object-oriented approach (backported to pathlib2
in Python 2.7):
from pathlib import Path
my_file = Path("/path/to/file")
if my_file.is_file():
# file exists
To check a directory, do:
if my_file.is_dir():
# directory exists
To check whether a Path
object exists independently of whether is it a file or directory, use exists()
:
if my_file.exists():
# path exists
You can also use resolve(strict=True)
in a try
block:
try:
my_abs_path = my_file.resolve(strict=True)
except FileNotFoundError:
# doesn't exist
else:
# exists
Check out the latest blogs from LambdaTest on this topic:
This article is a part of our Content Hub. For more in-depth resources, check out our content hub on Selenium pytest Tutorial.
The primary intent of Selenium test automation is to expedite the testing process. In the majority of the cases, automation tests using Selenium perform exceptionally better than the manual counterparts. However, there might be possibilities to speed up Selenium tests using Selenium test automation best practices to its truest potential. I have come across umpteen cases in my career where there was potential to speed up selenium tests.
Automation testing at first may sound like a nightmare especially when you have been into the manual testing business for quite long. Looking at the pace with which the need for automation testing is arising, it has become inevitable for website testers to deep dive into the automation river and starts swimming. To become a pro swimmer it takes time, similar is the case with becoming a successful automation tester. It requires knowledge & deep understanding of numerous automation tools & frameworks. As a beginner in automation testing, you may be looking forward to grabbing your hands on an open-source testing framework. After doing so the question that arises is what next? How do I go about using the open-source tool, framework, or platform, & I am here to help you out in that regard. Today, we will be looking at one of the most renowned open-source automation testing frameworks known as Selenium. In this Selenium Java tutorial, I will demonstrate a Selenium login example with Java to help you automate the login process.
This article is a part of our Content Hub. For more in-depth resources, check out our content hub on Selenium Python Tutorial and Selenium pytest Tutorial.
Looking for an in-depth tutorial around pytest? LambdaTest covers the detailed pytest tutorial that has everything related to the pytest, from setting up the pytest framework to automation testing. Delve deeper into pytest testing by exploring advanced use cases like parallel testing, pytest fixtures, parameterization, executing multiple test cases from a single file, and more.
Skim our below pytest tutorial playlist to get started with automation testing using the pytest framework.
https://www.youtube.com/playlist?list=PLZMWkkQEwOPlcGgDmHl8KkXKeLF83XlrP
Get 100 minutes of automation test minutes FREE!!