<@U0N6C2Q9F>: i’m attempting to use `@pytest.mark....
# development
w
@fast-nail-55400: i’m attempting to use
@pytest.mark.jvm_lockfile
in a test, and have successfully generated the lockfile via
internal-generate-test-lockfile-fixtures
(afaict). but then running the test reports:
Copy code
@pytest.mark.jvm_lockfile(
      path="scala-library-2.13.test.lock", requirements=["org.scala-lang:scala-library:2.13.8"]
  )
  def test_intellij_test(jvm_rule_runner: RuleRunner, jvm_lockfile: JVMLockfileFixture) -> None:
E       fixture 'jvm_lockfile' not found
>       available fixtures: cache, capfd, capfdbinary, caplog, capsys, capsysbinary, cov, doctest_namespace, extra, include_metadata_in_junit_xml, jvm_rule_runner, metadata, monkeypatch, no_cover, pytestconfig, record_property, record_testsuite_property, record_xml_attribute, recwarn, tmp_path, tmp_path_factory, tmpdir, tmpdir_factory
>       use 'pytest --fixtures [testpath]' for help on them.
any ideas?
f
You also need to register the pytest plug-in in a conftest.py.
w
mm.
thanks!
f
Scala and Kotlin already do so.
w
this ended up working really well: thank you!
f
Glad you found it useful!
w