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.
-
Prikaži ovu nit
-
There should be better ways of providing test output possible than dumping the contents into a terminal. I mean; lists work great when working in a terminal. But if you have a DOM available there should be ways to better share this information, and improve UX in the process.
1 reply 0 proslijeđenih tweetova 2 korisnika označavaju da im se sviđaPrikaži ovu nit -
Jetbrains provides something similar; though it doesn't feel like much attention has been paid to UX: https://www.jetbrains.com/help/rider/Reference_Windows_Unit_Tests.html … But yeah; it'd be interesting to see attempts at improving this. Wish testing in VS Code was entirely frictionless.
1 reply 0 proslijeđenih tweetova 1 korisnik označava da mu se sviđaPrikaži ovu nit -
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
0 proslijeđenih tweetova 0 korisnika označava da im se sviđaPrikaži ovu nit
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)
Č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.