lud

lud

Hello,

I do TDD a lot and so my code, notably my test code, is very often incorrect compared to the current implementation (since the purpose is to then change that implementation, obviously).

The problem is that whenever I run mix test [...], test failures are printed and then the test warnings are printed. When using AI to write more tests it’s a giant waterfall of type warnings. This is bad because when focusing on tests I just have to scroll a lot after each test execution, and that is very often.

Is there a way to enforce test failures being the last thing printed? The "Finished in XX seconds, N failures, N skipped etc. block is still last.

Also I’m not really sure why the current behaviour exists. Warnings supposed to be emitted during compilation (alhough .exs file) and test failures after test execution, so warnings should be before failures (for a same file at least, which is good enough for me).

Erlang/OTP 29 [erts-17.0.2] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [jit:ns]

Interactive Elixir (1.20.1) - press Ctrl+C to exit (type h() ENTER for help)

Edit: after a bit of exploration with Claude, it seems this is because my test is async: true and tests are executed whenever a file is compiled whereas warnings are printed when there is no more file in the compilation queue (the “require phase”).

Is there a way to change that?

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
webofbits
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself. My main conc...
#ai
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews