Want: test integration for @code that resembles Heroku's TAP integration UI. VS Code already performs tight integration for linters/compiler warnings. Might as well lean in and provide the same for test runs as well.
Ohh, looking at jetbrains a bit more: the test coverage window is really cool! https://www.jetbrains.com/help/rider/Unit_Tests_Coverage_window.html … If the language server protocol had a way to provide coverage info to the IDE, that would make for a really good view. Very curious which other things jetbrains provide :O
-
-
Okay, taking a step back: if I could have it my way I'd make it so tools would help me figure out what to tackle next. What I feel is always missing is *overview*. For code that's: missing tests, docs, todos, open issues, PRs, deps.
Prikaži ovu nit -
In browsers it's: a11y, load timings, caniuse metrics, test coverage, CSS utilization, fps, db usage, cache headers, img compressions, and all the lighthouse stuff. *something* should be possible there to automate answering the q: "What can I improve?"
Prikaži ovu nit -
It feels like so many tools out there exist doing a singular task, with varying degrees of success. But so few programming tools consider a complete workflow. It feels there's so much room for improvement.
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
-
-
I think you could get Test failure as diagnostic messages with the LSP, that just require the maintainer to run tests and stuff. (Which could also be painful for longer running tests)
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.