I would argue that the use cases for dealing with files in unit tests might be too diverse for a catch all implementation. Additionally, file usage in unit tests should be avoided, if possible (by using mocking/faking or so instead) since it requires dependencies in a unit test that usually should not be needed. Except of course you have to test an utility that manages files.
Manfred > Am 27.06.2020 um 13:01 schrieb José Valim <[email protected]>: > > If we are going in this direction, I would rather have @tag tmp_path: true. > It automatically generates a path based on the test name and updates the > context with said path. > > A string can also be given, we create it and clean it before the test. > > -- > You received this message because you are subscribed to the Google Groups > "elixir-lang-core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elixir-lang-core/CAGnRm4%2B44eW9GeJOwmMbr1RbOp_4k1x9s4b%3DyR3n6SQeDMQUnQ%40mail.gmail.com. -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/0DCC6DB5-9A58-4E73-B575-9670B2532B68%40me.com.
