medikent
What should be first, `Test.AppName` or `AppName.Test` for test modules?
If we are to include the label Test Anywhere in a test module name like
MyApp.Test.MyTestFileorMyAppWeb.Test.MyTestFile,
which is the default, and since the test files are typically located under the test/ root level folder should we not begin all module names with Test?
This would mean:
Test.MyApp.MyTestFileandTest.MyAppWeb.MyTestfile
Is the main argument for putting everything with app name first just to namespace all the test modules?
It is inconsistent to not follow the directory structure convention while also including the .Test. text in the middle a module name. The tests can already be identified by the ...Test ad the end of the file name.
Thoughts?
Most Liked
NobbZ
As far as I remember, the filename has to match the glob *_test.exs, while the module names need to end in Test, so placing it anywhere else would be redundant.
The way ex unit discovers the tests answers your question.
kokolegorille
If You use to_string, You will see the real nature of module’s name.
This is one of mine…
to_string Pr3f.Application
"Elixir.Pr3f.Application"
There is no correspondance with the name You give and related file system. It is very flexible and You could give any name, in any directory, that would be just fine. Convention is to do what You prefer 
But for test, convention is to not use Test as a directory, but as MyApp/MyFileTest. And don’t forget they are just scripts… as they have exs extension. They are not compiled.
kokolegorille
I was not very explicit, I follow the convention to put test files in test directory.
What I meant is I don’t use Test inside the test module name, but as a suffix.
Popular in Discussions
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
Real-time error tracking, performance insights, and observability for devs.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Real-time error tracking, performance insights, and observability for devs.
Develop your skills with books, videos, and courses.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
Courses that'll move you from confusion to "Aha, now I get it!"