Refactor editable tests

Author: stefanv

spin/tests/test_build_cmds.py

@@ -48,17 +48,6 @@ def test_run_stdout():
     ), f"`spin run` stdout did not yield version, but {stdout(p)}"
 
 
-def test_editable_conflict():
-    """Do we warn when a conflicting editable install is present?"""
-    try:
-        run(["pip", "install", "--quiet", "-e", "."])
-        assert "Warning! An editable installation" in stdout(
-            spin("run", "ls")
-        ), "Failed to detect and warn about editable install"
-    finally:
-        run(["pip", "uninstall", "--quiet", "-y", "example_pkg"])
-
-
 # Detecting whether a file is executable is not that easy on Windows,
 # as it seems to take into consideration whether that file is associated as an executable.
 @skip_on_windows

spin/tests/test_editable.py

@@ -0,0 +1,21 @@
+import pytest
+from testutil import spin, stdout
+
+from spin.cmds.util import run
+
+
+@pytest.fixture
+def editable_install():
+    run(["pip", "install", "--quiet", "--no-build-isolation", "-e", "."])
+    yield
+    run(["pip", "uninstall", "--quiet", "-y", "example_pkg"])
+
+
+def test_detect_editable(editable_install):
+    assert "Editable install of same source detected" in stdout(
+        spin("build")
+    ), "Failed to detect and warn about editable install"
+
+
+def test_editable_tests(editable_install):
+    spin("test")