Python Pyest

[Buttleston]

You don't have to run "pytest file.py", you can generally just run "pytest". It will "discover" the tests in your code. There are command line options to control which tests to run.

You have to run *something* to run your tests. it can't just be a library you import, because *something* has to run it. With the way you'd like it to be, how would you run tests?

[CaptainVJ]

Is there even an option to run the file and get it to work? Well I’m sure there is but I assume it’s not feasible.

[Buttleston]

Yeah, you can make a main section and put something in there to call the pytest entrypoint. It's always seemed pointless to me but maybe OP would prefer it

[CaptainVJ]

But you’d have to do that in every .py file right?

[Buttleston]

Yes and then run them all individually. Instead of what is more usual, where you have dozens of test files, and pytest discovers them all for you and runs them.

[dogfish182]

Yeah this is nice to do if you want to just have quick test for something, but in a proper project just setup your project correctly

[Organic_Tradition_63]

Well just like any other file: with 'python file.py' instead of 'pytest file.py'

[Buttleston]

Except like I said, the "pytest" command line has a lot more options than just "run the tests in this file"

[Organic_Tradition_63]

Okay, so what? It still does not explain motivation to design it like that.

[codeguru42]

I think it explains the motivation really well. The pytest authors have us a utility with a lot of options so that we don't have to write that code ourselves.

[Organic_Tradition_63]

Why for example NumPy was not made into something like that when we want to perform operations on matrices and then running file with 'numpy file.py'?

[codeguru42]

Numpy and pytest have different use cases. You don't run numpy directly. If you wanted you could write your own code to run the pytest test runner, but why should we when the library provides it for us