Issue: @test decorator adds to pytest output an extra test as well as a warning

[mobiware]

Issue you'd like to raise.

If we decorate one of our tests with the @test decorator, we notice in pytest output several issues:

1. there is an extra test. For instance pytest output says collected 10 items even though we only have 9 test cases
   When looking at verbose pytest output (using the -vv flag) we see this extra test:

project/integration_tests/test_chain.py::test <- ../../../../../../Library/Caches/pypoetry/virtualenvs/darwin-ai-langchain-b0bmgt7a-py3.10/lib/python3.10/site-packages/langsmith/_testing.py PASSED [ 10%]

2. this extra test seems to trigger a pytest warning:

================================================================================================================ warnings summary =================================================================================================================
project/integration_tests/test_chain.py::test
  /Users/name/Library/Caches/pypoetry/virtualenvs/darwin-ai-langchain-b0bmgt7a-py3.10/lib/python3.10/site-packages/_pytest/python.py:166: PytestReturnNotNoneWarning: Expected None, but project/integration_tests/test_chain.py::test returned <function test.<locals>.decorator at 0x101922b00>, which will be an error in a future version of pytest.  Did you mean to use `assert` instead of `return`?
    warnings.warn(

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html

Suggestion:

Might be due to the decorator name, since pytest collects test function by matching with the test prefix in their names ?

[mobiware]

An easy way to remove the warning and extra test is by renaming langsmith.test import so that it doesn't start with test, i.e.:

from langsmith import test as ls_test

@ls_test
def test_chain(input, output):
    assert ...

[hinthornw]

good catch